This page helps you choose how to send events to Algolia.
If you need an overview of events, queryID, and userToken, start with
Click and conversion events.
Start your implementation
The best way to send events to Algolia depends on where you’re sending them from.
Use this page to choose your implementation path.
Client-side versus server-side events
It’s best to send events straight from your users’ devices.
To do this, see Send events from your frontend on this page.
If you’re not collecting enough events compared to the number of visitors to your website or app,
it might be because your users use ad blockers.
In this case, consider server-side tracking.
With server-side tracking, your users’ devices send events to your servers.
Then your servers forward the events to the Insights API.
To set up server-side tracking, see Send events manually or in batches on this page.
If you’re using any of these ecommerce platforms,
you can use the Algolia integrations to send events:
If you’re using a headless ecommerce platform,
see Send click and conversion events from your frontend.
Send click and conversion events from your frontend
If you’re using Algolia’s UI libraries,
you can use their Insights integrations to send events:
For domain-specific guidance, see:
To send events from pages that aren’t search pages,
such as a shopping cart, use the search-insights library for web apps.
For native Android and iOS apps, use the InstantSearch event guides listed above.
If you’re not using Algolia’s UI libraries,
use the search-insights library to send click and conversion events.
These platforms can send events to the Algolia Insights API:
Send events manually or in batches
Use these resources if you need to send events manually,
forward them through your own servers,
or upload recent events from another system.
For more information, see:
Upload events from external analytics
You can speed up data collection by uploading events from the last four days.
To upload historical events, you can use:
For Algolia Recommend,
you can upload a CSV file
with events from the last 90 days.
If an event needs a queryID,
its timestamp must be within an hour of the related search or browse request.
The queryID can’t be from a search event older than four days.
For more information, see Event types.
See also
Last modified on September 28, 2026
