Criteo
Sync audience segments to Criteo for retargeting and prospecting campaigns. Upload your warehouse segments to Criteo’s audience platform.
Prerequisites
- A Criteo account with API access
- API client credentials (Client ID and Client Secret)
- Your Criteo Advertiser ID
Authentication
Criteo uses OAuth 2.0 Client Credentials grant.
- In Criteo, go to Marketing Solutions > API to create API credentials
- Enter your Client ID and Client Secret in Zeotap
Zeotap automatically obtains and refreshes access tokens using these credentials.
Configuration
| Field | Type | Required | Description |
|---|---|---|---|
| Advertiser ID | Text | Yes | Your Criteo advertiser identifier. Example: 12345 |
Target Settings
| Field | Type | Required | Description |
|---|---|---|---|
| Audience Name | Text | Yes | Name of the Criteo audience segment |
| Audience ID | Text | No | Existing audience ID to update. Leave blank to create new. |
Supported Operations
Sync Modes: Upsert, Mirror
Audience Sync Modes: Add, Remove, Mirror, Upsert
Features
- Field Mapping: No
- Schema Introspection: No
Match Keys
Criteo matches contact-list members on hashed identifiers. Map raw columns and Zeotap normalizes and hashes them at delivery, or map pre-hashed digests directly:
| Field | Type | Description |
|---|---|---|
email | string | Raw email address — lowercased, trimmed, and SHA-256 hashed before upload (Criteo’s recommended form) |
hashed_email | string | Pre-hashed SHA-256 hex digest of the lowercase, trimmed email |
hashed_email_md5 | string | Pre-hashed MD5 hex digest of the lowercase, trimmed email. Criteo accepts MD5 but recommends SHA-256 — prefer hashed_email when you have both. |
phone | string | Raw phone number — normalized to E.164 (digits with leading +) and SHA-256 hashed before upload |
hashed_phone | string | Pre-hashed SHA-256 hex digest of the E.164 phone number |
When both a raw field and its pre-hashed counterpart are mapped, the pre-hashed value wins. Values with the wrong digest shape (SHA-256 not 64-hex, MD5 not 32-hex) are never uploaded — they are dropped (falling back to the raw column if mapped) and counted in the sync run logs. See Match Keys & Identifier Hashing for the full normalization contract, precedence, and validation rules.
Troubleshooting
Client credentials invalid
Verify your Client ID and Client Secret in the Criteo Marketing Solutions API settings. Regenerate credentials if needed.
Advertiser ID not found
Ensure the Advertiser ID matches your Criteo account. Find it in the Criteo Management Center.