- 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 WooCommerce event reaches Criteo. Captured on the server, resolved to a person, then sent.
01 Capture
Captured from WooCommerce
Capture WooCommerce orders and customer events server-side and forward them to every platform you buy on.
See the WooCommerce integration →
WooCommerceWhat it sends order_idWooCommerce order numberbilling_email / phonecheckout contact fieldscustomer_idWordPress user, when logged inline_itemsproducts and quantitiesorder_totalorder value after discount
02 Understand
Resolved to one person before it leaves
Every WooCommerce 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.
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 matchingcriteo_click_idcredit the clickevent_iddedupe against the OneTagvalue / currencyvalue-based biddingproduct idssuppress the exact items already bought
The catch
WooCommerce sites vary enormously in how checkout is built, and browser-side conversion tags break on custom checkouts more often than on hosted platforms.
Capturing on the server sidesteps the theme entirely.
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 WooCommerce feeds Criteo. Two gains on the Criteo side, two on the WooCommerce 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.
WooCommerce
Every event, server-side
Storefront and checkout events are captured from WooCommerce on the server, independent of the browser.
WooCommerce
One setup, every destination
Connect WooCommerce once and forward to every ad platform, email tool and warehouse you run.
Setup
Live in under 20 minutes.
Connect WooCommerce once and every destination, Criteo included, is forwarded the same resolved events.
Upstack dashboardExample
WooCommerce Data source Connected
Criteo Destination Healthy
Read the full Criteo setup guide → -
01
Connect WooCommerce
Capture WooCommerce orders and customer events server-side and forward them to every platform you buy on.
-
02
Add the Criteo destination
Under Destinations, add Criteo. Every resolved WooCommerce 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 WooCommerce and Criteo.
How do I check that WooCommerce 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.
How long does it take to connect WooCommerce to Criteo?
Most brands are live in under 20 minutes. Once WooCommerce is connected, every destination receives the same resolved events, Criteo included.