Integrations / Personalisation
Coveo
Server-side delivery to the Coveo Usage Analytics (UA) Write API (rest/ua/v15/analytics). Routes page/content views to the /view endpoint (contentIdKey/contentIdValue for Content Recommendations) and behavioural events (search, product views, cart, purchase) to the /custom endpoint. clientId is mapped from Signal's anonymous_id for visit stitching; originLevel1 (search hub) and ISO 639-1 language come from organization config and context.
Datafly Signal delivers first-party events to Coveo server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Coveo expects.
Why route Coveo through Datafly Signal
Profiles update from the server, not the browser
Events reach Coveo even when a tracker blocker or a failed page unload would have dropped a client-side call, so the profile reflects what actually happened.
One consent decision governs every destination
Coveo 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_cartpagepurchaseremove_from_cartsearchselect_itemview_itemVertical presets
Default. 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 Coveo documentation.
Frequently asked questions
Does Datafly Signal integrate with Coveo?
Yes. Datafly Signal delivers first-party events to Coveo server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Coveo expects. The integration is included in every deployment at no additional cost.
How is server-side Coveo tracking different from the Coveo tag?
The Coveo 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 Coveo from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Coveo?
The blueprint ships with mappings for add_to_cart, page, purchase, remove_from_cart, search, select_item, view_item. Any event in your schema can be mapped to Coveo through pipeline configuration without a code change.
Do I need to keep the Coveo tag on my site?
No. Signal delivers to Coveo from the server, so no client-side Coveo script is required on your site.
Other personalisation integrations
Ready to move Coveo server-side?
See how Datafly Signal delivers first-party events to Coveo from infrastructure you control, with hashed identity and consent enforcement built in.