Custom stack to Criteo
Forward every Custom stack event to Criteo server-side, resolved to a person against a 750M+ device graph — with restored click IDs, deduplicated conversions and delivery you can audit.
Connection
Connect Custom stack to Criteo with Upstack Data
Custom stack
Not on the list? Send events to Upstack from any stack over webhook or direct post, with the same schema and the same resolution.
Custom stack integration
Criteo
Send resolved conversions to Criteo so retargeting stops re-serving people who already bought, and starts optimising on the ones who did.
Criteo integrationWhat changes
What changes when Custom stack feeds Criteo.
Server-side delivery
Events reach Criteo through its server API, not the browser — so ad blockers, ITP and consent banners don’t cost you conversions.
Identity-resolved events
Every event sent to Criteo carries a resolved customer, matched against a 750M+ device graph.
Any stack, any framework
Headless, custom checkout, native app or a platform we haven’t listed — if it can make an HTTP request, it can send to Upstack.
The same event schema
Custom events are resolved, filtered and forwarded exactly like a Shopify order.
What actually moves
What Custom stack carries, and what Criteo needs.
Custom stack and Criteo describe a customer with different vocabularies. This is the mapping Upstack applies on the way through — the left column is what Custom stack can put on an event, the right is what Criteo can actually use.
Custom stack sends
- event_name
- whatever you choose to call it
- user identifiers
- any of email, phone, external ID
- value / currency
- if the event carries revenue
- custom properties
- any attribute in your own schema
Criteo receives
- hashed email
- match the buyer for suppression and matching
- criteo_click_id
- credit the click
- event_id
- dedupe against the OneTag
- value / currency
- value-based bidding
- product ids
- suppress the exact items already bought
Delivery you can audit
How you know it is working.
Ad platforms accept almost anything and tell you very little. These controls exist so you can see what was sent and what was accepted, rather than inferring it from a reporting gap.
Per-event inspection
Every conversion is inspectable from the moment it fires to the moment the platform confirms it.Deduplication
Browser and server copies of the same purchase collapse on event ID, so nothing is counted twice.Bot and fraud filtering
Automated traffic never reaches the model, because what you keep out of the training set matters as much as what goes in.
Where to check in Criteo
Criteo Management CenterAssetsEvents. The event log shows server-side arrivals and the identifiers they carried.
Related connectors
Other places Custom stack can send to.
- Custom stackMeta Conversions API
- Custom stackGoogle Ads Conversions
- Custom stackTikTok Events API
- Custom stackPinterest
- Custom stackSnapchat
- Custom stackReddit
- Custom stackMicrosoft Ads
- Custom stackX
Other sources that feed Criteo.
- ShopifyCriteo
- WooCommerceCriteo
- BigCommerceCriteo
- Checkout ChampCriteo
- RechargeCriteo
- FunnelishCriteo
- Lasso CommerceCriteo
- Phoenix TechnologiesCriteo
- SkioCriteo
- Loop SubscriptionsCriteo
- StripeCriteo
- Everything Criteo can take12 sources feed Criteo, and the setup is the same for each one.Criteo integration
- How resolution worksEvery event matched against a 750M+ device graph before it is forwarded.Upstack Signal
- What it costsThree plans that scale with your order volume. Every connector is on every plan.See pricing
Get Custom stack talking to Criteo.
A 15-minute walkthrough of this connector on your own account.