Criteo integration: identity-resolved conversions, sent server-side

Send resolved conversions to Criteo so retargeting stops re-serving people who already bought, and starts optimizing on the ones who did.

Request a demo Start free trial

Role: Destination
Category: Ad platforms
Pre-built connectors: 12 sources
Plans: All plans

What Upstack sends

Every conversion reaches Criteo with the identifiers it matches on. Captured on the server, resolved to a person, then sent.

In: from Shopify1 of 12 sources

order_idShopify order and checkout token
email / phonecustomer contact from checkout
customer_idShopify customer record, if they have one
line_itemsproducts, variants and quantities
total / subtotal / discountorder economics

Storefront events from the Upstack Pixel, orders directly from Shopify.

Resolved before it is sent

IdentityMatched against a 750M+ device graph, so a phone browse and a desktop checkout resolve to one customer.
customer_typeNew or returning, resolved before send.
DeduplicationBrowser and server copies of the same purchase collapse on event ID, so nothing is counted twice.
Bot and fraud filteringAutomated traffic never reaches the model, because what you keep out of the training set matters as much as what goes in.

Out: to CriteoOn every event

hashed emailmatch the buyer for suppression and matching
criteo_click_idcredit the click
event_iddedupe against the OneTag
value / currencyvalue-based bidding
product idssuppress the exact items already bought

Retargeting that knows who converted.

See the set-up reference See all 12 sources How resolution works

About Criteo

Upstack sends the conversion server-side, resolved to a person, so suppression happens against the customer rather than the browser.

Someone who browsed on a phone and bought on a laptop is recognized as having bought. That is exactly the case a cookie-based signal gets wrong.

What Criteo is

Criteo is best known for retargeting: reaching people who have already visited and bringing them back.

Retargeting has one obvious failure mode, and it is expensive: paying to reach someone who already bought.

How Criteo works

Criteo builds audiences from on-site behavior reported by its tag, then serves against them. When a purchase is not reported back cleanly, the buyer stays in the retargeting pool and keeps being served.

What you can do with it

Three jobs this connector does inside Criteo.

Send complete conversions

Conversions reach Criteo through its server-side API with restored click IDs and hashed identifiers attached, so more of what you send is matched on arrival, and the conversions you never saw stop being invisible.

Optimize on the customer you want

Map any order attribute to the conversion Criteo receives (profit rather than revenue, new customers rather than repeat buyers, high-value orders rather than every checkout), so the platform learns from the buyers worth acquiring.

Stop paying to reach buyers

Purchases are resolved across devices before they are sent, so a customer who converted elsewhere is suppressed rather than re-served.

Pre-built connectors

12 sources connect to Criteo. Whichever of these you run, Criteo is one switch away.

See all connectors

Documentation

Set-up reference.

Set-up, event schema and field mapping for Criteo as a destination.

FAQ

Criteo integration questions.

What does Upstack send to Criteo?

Send resolved conversions to Criteo so retargeting stops re-serving people who already bought, and starts optimizing on the ones who did.

How do I check that events are reaching Criteo?

Open Criteo Management Center › Assets › Events. The event log shows server-side arrivals and the identifiers they carried.

Which plans include the Criteo integration?

All plans. Upstack has three plans that scale with your order volume, and the same integrations are on every plan.

Which sources can send events to Criteo?

12 sources: Shopify, WooCommerce, BigCommerce, Checkout Champ, Recharge, Custom stack, Funnelish, Lasso Commerce, Phoenix Technologies, Skio, Loop Subscriptions and Stripe. Each one has its own pre-built connector.

Will Upstack slow down my store?

Upstack’s own pixel loads asynchronously and fails silently, so it doesn’t hold up your pages. What each destination adds depends on its Tracking Method. The default, Browser + Server, loads that platform’s own tag on your store, in place of the copy you would otherwise install yourself, and also sends the same events from Upstack’s servers. Choose Server for any destination that offers it and its tag never loads, while its events still arrive from Upstack’s servers.

Similar integrations

Other Ad platforms integrations.

See all integrations

Get Criteo tracking right.

A 15-minute walkthrough tailored to your stack and channels.

Request a demo Start free trial