Criteo retargeting,
powered by server-side events.
Criteo built its business on dynamic retargeting — showing shoppers the exact products they browsed, in real time, across the open web. But Criteo's engine depends on complete product view and purchase signals, and the browser-side OneTag is losing ground to ad blockers, ITP, and vanishing cookies. When events go missing, product recommendations go wrong.
Ingest Labs delivers your catalog events to the Criteo Events API server-side — every product view, cart update, and transaction, enriched with first-party identity and gated by consent. Your retargeting gets the complete signal it was designed to run on.
Why Criteo + Ingest Labs
Criteo's dynamic retargeting is only as good as the product signals flowing into it. When a shopper views a product on Safari and the event is blocked by ITP, Criteo can't add that product to the retargeting pool. When a purchase event is swallowed by an ad blocker, Criteo keeps bidding on a user who already converted. The result: wasted spend and poor ROAS.
The Criteo Events API was built to solve this — a server-to-server channel that accepts product view, basket, and transaction events with full catalog detail. But wiring up a reliable server-side pipeline, mapping product schemas, resolving identity, and enforcing consent isn't a one-afternoon project.
Ingest Labs makes it one. We capture events at the source, map them to Criteo's expected schema — including product arrays with SKU, price, and quantity — enrich them with hashed email and other first-party identifiers, and deliver them to Criteo in real time. Your dynamic ads show the right products because Criteo sees every signal.
Integration resources
Setup guide for the Criteo Events API destination, including product catalog event mapping and identity enrichment.
Contact for setup guide
Criteo Management Center — where campaigns, audiences, and product catalogs are managed and optimized.
Visit CriteoCriteo's official Events API documentation — event types, product schema, and server-side integration guide.
Criteo Events API docsKey benefits
Complete product signals for Criteo's retargeting engine — captured server-side and enriched with first-party identity.
- Recover product view and purchase events lost to ad blockers and browser tracking prevention
- Deliver full catalog detail — SKU, price, quantity — with every server-side event
- Enrich events with first-party identity for higher Criteo user match rates
- Stop bidding on already-converted users by ensuring every transaction reaches Criteo
- Enforce GDPR, CCPA, and consent policies server-side before events are transmitted
- Zero client-side performance impact — no additional JavaScript on the shopper's device
Frequently Asked Questions
What is the Criteo Events API?
The Criteo Events API is a server-to-server endpoint that accepts conversion and engagement events directly from your backend — bypassing browser limitations like ad blockers, ITP, and cookie restrictions. It powers Criteo's dynamic retargeting, prospecting, and commerce media campaigns with higher-fidelity data.
How does server-side tracking improve Criteo retargeting?
Browser-based Criteo tags miss 30–40% of product view and purchase events due to ad blockers and tracking prevention. Server-side delivery ensures every event reaches Criteo with complete product catalog data — SKUs, prices, quantities — so dynamic ads show the right products to the right users.
Will this work with my existing Criteo OneTag?
Yes. You can run Ingest Labs server-side delivery alongside your existing OneTag. Events are deduplicated so Criteo won't double-count conversions. Most customers keep the OneTag for initial page load signals and let Ingest Labs handle the high-value conversion events server-side.
What events can I send to Criteo server-side?
All standard Criteo events — viewItem, viewList, viewBasket, trackTransaction, and custom events. Ingest Labs maps your event schema to Criteo's expected format automatically, including product arrays with id, price, and quantity fields.
Is this compliant with GDPR and privacy regulations?
Yes. Ingest Labs enforces consent policies server-side before any event reaches Criteo. Events from users who haven't consented to marketing are suppressed automatically, with full audit logging for compliance documentation.
How quickly can I get started?
Most Criteo integrations go live within 24 hours. Ingest Labs handles the API connection, event mapping, and identity enrichment. You provide your Criteo account credentials and confirm which events to track — we handle the rest.
Ingest Labs Criteo integration: Server-side event delivery via the Criteo Events API for dynamic retargeting and commerce media. Ensures complete product catalog signals, enriches events with first-party identity, and enforces consent compliance. Recovers conversions lost to ad blockers and browser restrictions. Live in under 24 hours.
Give Criteo the full picture — every product view, every purchase.
Server-side retargeting signals, enriched with first-party identity — live in under a day.