Why are my click and conversion events valid but features still not working?

Even if your events return a 200 status in the Events Debugger, this only means they were successfully received by Algolia. It does not guarantee they the events contains all the required data used by features such as Dynamic Re-Ranking.

If you find that features that rely on events are not working as expected, you can investigate by checking the following:

Do your click and conversion events include a queryID?

A queryID is required to link a click or conversion event to the search or browse request it originated from.

If events related to Algolia search requests are not being sent with a queryID, they won't be usuable by event dependant features.

Events that are not associated with a search or browse requests are not expected to contain a queryID.

For a full breakdown of the types of events accepted by each feature, check out the Events by features table.

How to check queryID?

1. Go to the Events Debugger in your dashboard
2. Filter events using eventType=click or eventType=conversion
3. Select an event to view its details

In the Event Details:

• Confirm whether a queryID is present
• Scroll down to see which features will use the event 

You will also see the following message in the debugger:

This event may still not be consumed by the destination if its queryID does not match any queries' queryID.

This means that even if a queryID is present, the event won’t be used unless it corresponds to a valid query.

To learn how to verify this, check out this guide article.

If you don't see the queryID in the Event Details for events that should contain one, those events won’t be used by relevant features, even though they appear valid.

Are your events passing valid objectIDs?

Your events must pass the objectID values that exist within your index.

If an event sends an invalid or non-existent objectID, it won’t be usable by Algolia features.

How to verify objectIDs

You can validate objectIDs in two ways:

1. Using the Event Debugger validator

When viewing an event, check the Event Validity section:

• If you see “Objects are valid”, the objectIDs exist in your index
• If there’s an issue, it will be flagged here

2. Manually checking the index

1. Copy the objectID from the event details

2. Search for it in your Algolia index using - if no results are returned, the objectID is invalid

Key takeaway

A 200 status only confirms the event was successfully received.

If features aren’t working as expected, focus on:

• Whether a queryID is present when required
• Whether objectIDs exist in your index (and pass validation)

These checks ensure your events are not just valid but actually usable.

If instead you’re seeing 422 errors (invalid events), refer to this guide article on on how to debug your events.