Home
Connectors
BigCommerce - Criteo

Send every BigCommerce event to Criteo, server-side

Q: How do I check that BigCommerce 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: How long does it take to connect BigCommerce to Criteo?

Most brands are live in under 20 minutes. Once BigCommerce is connected, every destination receives the same resolved events, Criteo included.

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

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 BigCommerce event reaches Criteo. Captured on the server, resolved to a person, then sent.

01 Capture

Captured from BigCommerce

Server-side capture of BigCommerce storefront and checkout events, resolved and forwarded downstream.

See the BigCommerce integration

BigCommerceWhat it sends

order_idBigCommerce order
email / phonecheckout contact
customer_idBigCommerce customer record
productscatalog items on the order
total_inc_taxorder value

02 Understand

Resolved to one person before it leaves

Every BigCommerce 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

BigCommerce's hosted checkout limits what a browser tag can see at the moment of purchase, which is exactly the moment that matters for conversion tracking.

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 BigCommerce feeds Criteo. Two gains on the Criteo side, two on the BigCommerce 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.

BigCommerce

Every event, server-side

Storefront and checkout events are captured from BigCommerce on the server, independent of the browser.

BigCommerce

One setup, every destination

Connect BigCommerce once and forward to every ad platform, email tool and warehouse you run.

Setup

Live in under 20 minutes.

Connect BigCommerce once and every destination, Criteo included, is forwarded the same resolved events.

Upstack dashboardExample

BigCommerce Data source Connected

Criteo Destination Healthy

Read the full Criteo setup guide

01

Connect BigCommerce

Server-side capture of BigCommerce storefront and checkout events, resolved and forwarded downstream.
02

Add the Criteo destination

Under Destinations, add Criteo. Every resolved BigCommerce 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.