Client Activity Tracking
Applications using Places (Search) API must enable services to log user activities such as search requests, search result choices and other interactions.
Activity Tracking aims to improve the future Search and Discovery experience for the user. This feature is based on anonymously provided data about user activities such as search requests. More specifically Places (Search) API relies on feedback from users in order to improve the statistical model it uses for building relationships between places, ranking places and providing recommendations. This data also helps HERE to debug customers' technical issues.
To this end, client applications should send certain tracking data with each request they make. The data is anonymous and the purpose is not to track individual users but to improve the results from the Places (Search) API. For detailed information for how to appropriately track client activity, see below:
X-Forwarded-For header should be provided in line with the Internet Engineering Task Force (IETF) Forwarded HTTP Extension specification.
If requests from the client application are generated on a server rather than the user's device, the server should send the client's IP address in the X-Forwarded-For header.
The User-Agent. in header should be provided to the Places (Search) API.