Criteo Events API
Criteo's server-side endpoint works like their pixel, from the server: the account (partner id) and mapping key travel in the event body, along with the visit's URL, IP and user agent.
Data delivered
Data delivered
- Free-form event names with real timestamps
- Page URL, IP and user agent from the visit
- Event id for deduplication
What it is for
What you can do with it
- Feed Criteo retargeting with server events
- Send the purchase event without a tag on the site
Why integrate
The business reason, not just the tech
Retargeting on server events
Criteo runs on fresh intent signals. The S2S path delivers visits and purchases without a site tag — including sales that close outside the browser.
Simple on purpose
Criteo's S2S endpoint authenticates via account and mapping key in the body — no token to rotate, no OAuth to break.
How to connect
Step by step
- Step 1
Ask Criteo for the partner id and caller id of your integration.
- Step 2
Create the destination with both identifiers.
- Step 3
Create a Delivery with the events that matter.
Frequently asked questions
Where does the access token go?
There isn't one — Criteo's S2S endpoint authenticates via the account and mapping key in the body, like their pixel. That's why creation asks for no secret.
Other integrations
Meta Conversions API
Destination
Server-side conversions to Meta, with identity already resolved and no dependency on the browser.
View integration
TikTok Events API
Destination
Server-side conversions to TikTok Ads, with hashed identity and per-event deduplication.
View integration
Snapchat Conversions API
Destination
Server-side conversions to Snapchat with the same 11 identity fields as the Meta family.
View integrationStart measuring what actually becomes revenue
Create a free account, connect your first source and see your first lead timeline today. No card required.