Reach the people who will care most about you, whether they’re just discovering you, or have engaged with you before.
Overview
This destination lets you push data from various sources to create and update membership of audiences. Create a new audience and add new members within a single sync. Subsequent syncs update audience membership. Use your audiences to leverage Criteo's targeting suite to reach active in-market shoppers ready to engage with you and become your next loyal customers.
Supported syncing
| Object Type | Description | Supported Sync Modes |
|---|---|---|
| Audiences | Create audiences and update contact list membership | Upsert |
Getting started
To use the Criteo destination in Hightouch, you need Criteo credentials to authorize the Hightouch application with OAuth.
Syncing data
Audiences
Syncing to Criteo's Audience API lets you manage your contact lists by creating, deleting, and updating audience data used for advertising campaigns.
Record matching
You can match columns in your model with users in Criteo on the following fields:
- Mobile ad identifier
- LiveRamp identity link
- Criteo GUM cookie identifier
When using the Criteo GUM cookie identifier, you must also enter your advertiser's GUM Caller ID. To get the GUM Caller ID, reach out to your Criteo account team.
Delete behavior
You can choose how to handle user records in Criteo when the corresponding rows are deleted in your source.
| Behavior | Description |
|---|---|
| Do nothing | Keep the contact in your Criteo audience |
| Remove from list | Remove the contact from your Criteo audience |
Tips and troubleshooting
Common errors
To date, our customers haven't experienced any errors while using the Criteo destination. If you run into any issues, . We're here to help.
Live debugger
Hightouch provides complete visibility into the API calls made during each of your sync runs. We recommend reading our article on debugging tips and tricks to learn more.
Sync alerts
Hightouch can alert you of sync issues via Slack, PagerDuty, SMS, or email. For details, please visit our article on alerting.