Skip to main content
The Algolia Insights API accepts three types of events: click, conversion, and view events. By sending events, you can enable one or more Algolia features. For an overview of how events, queryID, and userToken work together, see Click and conversion events. To choose an implementation path, see Choose how to send events.

​
Events by features

The following table lists events and where they’re used.
SearchRecommendAdvanced PersonalizationClassic Personalization
clickedObjectIDsAfterSearch
convertedObjectIDsAfterSearch
addedToCartObjectIDsAfterSearch
purchasedObjectIDsAfterSearch
clickedObjectIDs
convertedObjectIDs
addedToCartObjectIDs
purchasedObjectIDs
viewedObjectIDs
clickedFilters
convertedFilters
viewedFilters
The Search column refers to NeuralSearch, Dynamic Re-Ranking, Query Categorization, Analytics, and A/B testing.
To learn more about the properties of each event, see the Insights API reference.

​
Minimum number of events

In general, the features that require events work better with more events. Some features need a minimum number of events to be active.

​
Events requirements for NeuralSearch

  • Minimum 1,000 click OR 100 conversion events within 30 days.
NeuralSearch uses these events:

​
Events requirements for Recommend—Frequently Bought Together

  • Minimum 1,000 conversion events with 2 or more products within 30 days
  • Maximum 3,000,000 conversion events within 30 days
If there aren’t enough events within 30 days, the collection period extends to 90 days. Frequently Bought Together uses these events:
  • Minimum 10,000 events within 30 days
  • Maximum 3,000,000 events within 30 days
If there aren’t enough events within 30 days, the collection period extends to 90 days. Related Products uses these events:

​
Events requirements for Recommend—Related Content

  • Minimum 10 events on items with content-based attributes within 30 days
  • Maximum 1,500,000 events within 30 days
If there aren’t enough events within 30 days, the collection period extends to 90 days. Related Content uses the same events as the Related Products model.
  • Minimum 500 conversion events within 30 days
  • Maximum 3,000,000 conversion events.
Trending Items and Trending Facet Values use these events:

​
Events requirements for Dynamic Re-Ranking

  • Minimum 20 click events OR 2 conversion events within 30 days
with fewer events won’t be re-ranked. Dynamic Re-Ranking uses these events: To prevent a manipulation of your ranking, Dynamic Re-Ranking only considers 1 event per user (userToken) per search query per record (objectID).

​
Events requirements for Query Categorization

Query Categorization needs a minimum number of events to train the model for predicting categories. It always uses events from the last 90 days. Query Categorization uses these events:

​
Events requirements for Personalization

Classic Personalization and Advanced Personalization can use any of the above events. The requirements for Advanced Personalization are detailed in Requirements and limits.

​
Events on category pages

You can build category pages with Algolia by sending an empty search query and an applied filter. Because category pages are just a different form of search requests, you’ll use the same events for category pages and search results. However, ensure you can differentiate between search and category page events by segmenting your analytics data. Use the events debugger and consistent event names to see which segment corresponds to which event. Some events come in two variants: with and without a query ID. Events with a query ID have AfterSearch in their name. Most Algolia features use events with query IDs, for example, to calculate the conversion rate of your search.
Events without a query ID are not considered for most Algolia features. For more information about the types of events accepted by each feature, refer to the Events by features table.
Use methods with AfterSearch in their name when a click or conversion happens after an Algolia search or browse request. These methods require a queryID, which Algolia returns when you set clickAnalytics to true.
Click and conversion events with a queryID are time-sensitive. They must occur within one hour of the corresponding search request.

​
Events unrelated to Algolia requests

Use methods without AfterSearch when an interaction isn’t tied to a previous Algolia search or browse request. Common examples include homepage modules, recommendation emails, and conversions that happen long after the original search. For details on capturing, passing, and inferring queryID, see Keep track of query IDs.
Last modified on April 7, 2026