Reach the people who will care most about you, whether they’re just discovering you, or have engaged with you before.
Supported syncing
| Sync Type | Description | Supported Sync Modes | API Reference |
|---|---|---|---|
| Audiences | Create audiences and update contact list membership | Add, Remove | Audiences reference |
Connect to Criteo
Go to the Destinations overview page and click the Add destination button. Select Criteo and click Continue. You can then authenticate Hightouch to Criteo using OAuth.
Click Log in to Criteo, log in with your Criteo account, and click Approve. Once successful, you will be redirected back to Hightouch to enter a descriptive name for your destination and complete setup.
Sync configuration
Once you've set up your Criteo destination and have a model to pull data from, you can set up your sync configuration to begin syncing data. Go to the Syncs overview page and click the Add sync button to begin. Then, select the relevant model and the Criteo destination you want to sync to.
Whether you're syncing events or audiences, begin your configuration by selecting the advertiser ownign the audience you want to sync to.
Syncing audiences
Syncing to Criteo's Audience API lets you manage your contact lists by creating, deleting, and updating audience data used for advertising campaigns.
Select an existing audience or create a new one
You can create a new audience or use an existing one. When creating a new audience, you can optionally enter a name; otherwise, Hightouch defaults to the name of the associated model. To use an existing audience, select the desired audience from the dropdown.
User identifiers
To identify which users to add or update in an audience, select model columns and the corresponding Criteo fields. You can match on any of the following Criteo 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
Matched users count
Hightouch retrieves the audience metadata from Criteo in real-time. The matched number displayed in Hightouch should reflect what you see in Criteo. Note that the matched numbers are approximated to maintain privacy thresholds. Hightouch takes the matched count to calculate a match rate for your sync, where applicable. The calculation breakdown:
matched_user_count / # of rows queried in the latest sync runThe match rate is
not
calculated when:- syncing to an existing segment because the total number of records to ever be uploaded to the segment is unknown
- removed users from your model is not removed in Criteo because the matched user count would be inflated in the calculation
Common causes for low match rates:
- Your audience model is too small. Most ad platforms do not display the matched number unless there's at least one thousand matched users to maintain privacy thresholds.
- The upload is still processing. We recommend waiting at least
72 hours
from the first sync run for numbers to settle. - Your data isn’t cleaned or hashed properly. Hightouch does most of the cleaning and hashing for you, but it’s still good to make sure that the data is as clean as possible. Note that Hightouch can not clean your data if you opt to hash it yourself, so ensure you follow the data cleaning requirements for Criteo.
Common errors
To date, our customers haven't experienced any errors while using this destination. If you run into any issues, please don't hesitate to . 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.