Integrations / Personalisation
Algolia Insights
Server-side delivery to the Algolia Insights API (/1/events). Maps Signal search, product-list, click, view, add-to-cart, and purchase events to Algolia click/view/conversion event types — with a stable first-party userToken (anonymous_id), authenticatedUserToken (user_id), queryID for after-search attribution, and objectIDs/positions/objectData for analytics, A/B testing, Dynamic Re-Ranking, and Algolia Recommend training.
Datafly Signal delivers first-party events to Algolia Insights server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Algolia Insights expects.
Why route Algolia Insights through Datafly Signal
Profiles update from the server, not the browser
Events reach Algolia Insights even when a tracker blocker or a failed page unload would have dropped a client-side call, so the profile reflects what actually happened.
Delivery is batched, rate-limited, and retried
Signal buffers to Kafka, respects the Algolia Insights rate limit, and retries on 429 or transient failure rather than dropping the event.
One consent decision governs every destination
Algolia Insights is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
What ships in the blueprint
Mapped events
add_to_cartpurchasesearchselect_itemview_itemview_item_listVertical presets
Search & Discovery. Each preset starts from a working configuration for that vertical rather than a blank field map.
Full field mappings, configuration fields, and troubleshooting are in the Algolia Insights documentation.
Frequently asked questions
Does Datafly Signal integrate with Algolia Insights?
Yes. Datafly Signal delivers first-party events to Algolia Insights server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Algolia Insights expects. The integration is included in every deployment at no additional cost.
How is server-side Algolia Insights tracking different from the Algolia Insights tag?
The Algolia Insights tag runs in the visitor's browser, so it is subject to ad blockers, tracking prevention, and page-unload races. Signal collects the event through a first-party endpoint on your own domain and delivers it to Algolia Insights from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Algolia Insights?
The blueprint ships with mappings for add_to_cart, purchase, search, select_item, view_item, view_item_list. Any event in your schema can be mapped to Algolia Insights through pipeline configuration without a code change.
Do I need to keep the Algolia Insights tag on my site?
No. Signal delivers to Algolia Insights from the server, so no client-side Algolia Insights script is required on your site.
Other personalisation integrations
Ready to move Algolia Insights server-side?
See how Datafly Signal delivers first-party events to Algolia Insights from infrastructure you control, with hashed identity and consent enforcement built in.