Home
Connectors
Shopify - Criteo

Send every Shopify event to Criteo, server-side

Q: How do I check that Shopify events are reaching Criteo?

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

Q: Will a purchase be counted twice?

No. Browser and server copies of the same purchase collapse on event ID, so nothing is counted twice.

Q: Do I need a developer to connect Shopify to Criteo?

No. Shopify connects as an app install with no theme edits, and most brands are live in under 20 minutes. Headless storefronts add the Upstack Pixel script instead of the theme app extension.

Each event is resolved to a person against a 750M+ device graph before it reaches Criteo, with restored click IDs, deduplicated conversions and delivery you can audit.

Request a demo Start free trial

4.6 out of 5 from 36 reviews on the Shopify App Store

US device IDs in the graph: 750M+
Match rate on events: 90%+
Identity window, per customer: Lifetime
Most brands are live: <20 min

How it flows

How a Shopify event reaches Criteo. Captured on the server, resolved to a person, then sent.

01 Capture

Captured from Shopify

One Upstack app setup that captures Shopify storefront and checkout events with the Upstack Pixel, records every order directly from Shopify, and forwards both to every tool you spend on.

See the Shopify integration

ShopifyWhat it sends

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

02 Understand

Resolved to one person before it leaves

Every Shopify event is matched against a 750M+ device graph, so a phone browse and a desktop checkout resolve to one customer rather than two strangers.

How resolution works

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.

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.

03 Activate

Delivered to Criteo

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

See the Criteo integration

CriteoWhat it receives

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

The catch

Shopify brands almost always have a pixel already firing.

Sending server events alongside it without a shared event ID is how a single purchase becomes two conversions and your reported ROAS quietly doubles. Upstack records one Purchase per Shopify order ID, so the pixel's copy and Shopify's own copy of an order count once.

Where to check in CriteoDelivery you can audit

Criteo Management Center Assets Events

The event log shows server-side arrivals and the identifiers they carried.

What changes

What changes when Shopify feeds Criteo. Two gains on the Criteo side, two on the Shopify side.

Criteo

Server-side delivery

Events reach Criteo through its server API rather than the browser, so ad blockers and ITP don’t cost you conversions.

Criteo

Identity-resolved events

Events sent to Criteo carry the resolved customer whenever Upstack can identify one, matched against a 750M+ device graph.

Shopify

Orders recorded from Shopify itself

Purchases also reach Upstack directly from Shopify, about 10 minutes after the order, so an order still counts when an ad blocker stopped the pixel or the shopper closed the page.

Shopify

Recognize returning customers

Shopify customer IDs, emails and phones are matched against the graph, so repeat buyers are identified across devices.

Setup

Live in under 20 minutes.

App install, no theme edits and no developer.

Upstack dashboardExample

Shopify Data source Connected

Criteo Destination Healthy

Read the full Criteo setup guide

01

Connect Shopify

In the Upstack dashboard, open System, then Data Sources, and click Connect Shopify. Approve the install in your Shopify Admin: Upstack reads products, orders and customers, and writes only its own pixel.
02

Add the Criteo destination

Under Destinations, add Criteo. Every resolved Shopify event is then forwarded to it.
03

Check delivery to Criteo

Every conversion is inspectable from the moment it fires to the moment the platform confirms it.

FAQ

Questions about Shopify and Criteo.

How do I check that Shopify events are reaching Criteo?

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

Will a purchase be counted twice?

No. Browser and server copies of the same purchase collapse on event ID, so nothing is counted twice.

Do I need a developer to connect Shopify to Criteo?

No. Shopify connects as an app install with no theme edits, and most brands are live in under 20 minutes. Headless storefronts add the Upstack Pixel script instead of the theme app extension.