Analytics

analytics for personalized search can be captured on certain events, but how you capture them differs by event for a searchclicks event, you must make an additional api call when you trigger the event this directs the relevant analytics data to be captured for a purchase event, certain data must be included on triggering the event analytics are then automatically captured searchclicks analytics when you trigger a searchclicks event, you must make an api call to the following endpoint searchclicks event endpoint https //engine monetate net/api/search/v1/site search/{name}/{instance}/{domain}/report click pass the searchclicktoken key value pair with the call as shown in the following example replace the sample token with your own searchclicktoken example { "searchclicktoken" "st 1 wyi1mg1njqx3nexjjbglja2vkiwinjlzczag9lcyisici1ndmyms0isicixmjcczovl2fkrvlkil0" } the possible response codes are as follows 200 success 400 bad request your request included a parameter that is unsupported 500 error an unknown error has occurred please try again or contact your account manager for more information purchase analytics purchase events are triggered by the addpurchaserows method or by including model monetate\ context\ purchase in the engine api request when using personalized search, you must include both the productid and sku parameters in the call personalized search analytics are automatically captured when you use this call you don't need to make any additional api calls furthermore, to ensure that the purchase related data, including sales generated through search, is reported and recorded correctly, you must establish some means of storing or maintaining the persistence of the value of a customer's monetateid refer to user identity persistence in requests docid 7m254upwksja xlmmy6m4 for more information