Analytics Tracking

overview reporting user interaction with klevu is crucial to allow the machine learning algorithms to accurately rank items analytics should be considered a required component of implementation analytics should be considered a required component of implementation there are three key aspects of analytic reporting searches the primary source of learning, and is where we ascertain the most meaningful and useful customer interactions clicks a machine learning data point measuring engagement purchases are a critical data point for attributing conversion these learnings are applied to all three of our core products search, category merchandising and recommendations including all enabled banners and facets in most of the analytic calls, the shopper's ip address is used by the machine learning to attribute a single shopper's searches and clicks into conversions please note if the klevu shopperip parameter is left empty, klevu will attempt to retrieve the ip value from the header of the request itself as best practice, when possible, you should identify the ip value prior to the analytics call and consider it as a required required parameter analytics url the endpoint urls are based on your assigned analytics url you can find this value within your klevu merchant center dashboard klevu merchant center > store settings > analytics url you will see this represented in the documentation as placeholder {{ analytics url }} request headers when proxying analytics calls to our system, ensure that all common request headers, including the original user agent , are passed through correctly this is crucial for accurate reporting, as our system relies on standard headers to derive important information such as this is crucial for accurate reporting, as our system relies on standard headers to derive important information such as device type we don’t provide specific guidelines for individual header values, as browsers and http clients send predefined values however, it’s important to handle these headers correctly for more details on common request headers, refer to mozilla developer network's glossary on request headers