If your click or conversion events are valid in the Events Debugger but don’t appear to be reflected in Analytics, the most common cause is that the events aren’t being sent with a queryID and therefore cannot be linked back to the search they originated.
Algolia uses the queryID to associate the event with the search that it was triggered from. To generate a queryID, the original search request should be sent with clickAnalytics:true. That queryID then needs to be included when you send the related click or conversion event.
Events can be sent without a queryID when it isn’t related to a search or browse request. However, events without a queryID aren’t considered for most Algolia features including Analytics.
To investigate this:
Open the Events Debugger in your Algolia dashboard.
Click on a click or conversion event
Check whether the event includes a
queryIDConfirm that the
queryIDmatches the one returned by the corresponding search request. A mismatchedqueryIDcan also prevent the event from being consumed by downstream features.
For a deeper dive, check out: