Criteo Events API
Server-side event delivery to Criteo's Events API (S2S v0) for reliable retargeting, bypassing browser limitations and providing consistent user matching for ad optimization.
Criteo Events API is a server destination in the walkerOS flow:
Sends events server-side to Criteo using raw HTTP (no SDK). Authentication is in-payload (`account` = Partner ID, `id.mapping_key` = Caller ID). Emails are hashed into MD5, SHA-256, and SHA-256(MD5) before sending.
Installation
- Integrated
- Bundled
Configuration
This destination uses the standard destination config wrapper (consent, data, env, id, ...). For the shared fields see destination configuration. Package-specific fields live under config.settings and are listed below.
Settings
| Property | Type | Description | More |
|---|---|---|---|
partnerId | string | Criteo Partner ID (numeric string, provided by Criteo) | |
callerId | string | Caller ID for user mapping (provided by Criteo) | |
siteType | 'd' | 'm' | 't' | Site type: d (desktop), m (mobile web), t (tablet) | |
country | string | ISO 3166-1 alpha-2 country code | |
language | string | 2-letter language code | |
url | string | Custom Events API endpoint (default https://widget.criteo.com/m/event?version=s2s_v0) | |
user_data | Record<string, string> | Mapping for identity fields |
Mapping
Per-event rules under config.mapping. For the standard rule fields (consent, condition, data, batch, name, policy) see mapping.
| Property | Type | Description | More |
|---|
Examples
add to cart
page view
purchase
view item
Event mapping
Criteo uses its own standard event names. Set the Criteo event name via each rule's name field.
| walkerOS Event | Criteo Event Name |
|---|---|
page view | viewHome / viewPage |
product view | viewItem |
product list | viewList |
product add | addToCart |
cart view | viewBasket |
checkout start | beginCheckout |
checkout payment | addPaymentInfo |
order complete | trackTransaction |
user login | login |
User identity
Criteo matches users via three signals. Wire them through user_data in settings:
| Field | Description |
|---|---|
mapped_user_id | Criteo GUM ID |
email | Raw email. Hashed into MD5, SHA-256 and SHA-256(MD5) |
retailer_visitor_id | Stable retailer visitor identifier |
Email hashing
Raw emails are lowercased and trimmed, then hashed into all three formats Criteo expects:
md5: MD5 hex digestsha256: SHA-256 hex digestsha256_md5: SHA-256 hex of the MD5 hex string
Pre-hashed values (detected by hex length: 32 chars for MD5, 64 for SHA-256) are passed through without re-hashing.
Deduplication
Criteo Events API supports deduplication with Criteo OneTag by sharing a deduplication_page_view_id across channels. Wire it via data.map.deduplication_page_view_id in the event mapping.