Criteo Audiences Destination

Benefits of the Criteo Audiences (Actions) destination include:

• Improved email matching: This integration creates a direct connection between Segment and Criteo for a higher match rate of email identifiers.
• Fewer settings: Unlike Criteo's Filter destination, this destination doesn't require any copy and paste code. You only need your Advertiser ID and Criteo API credentials.
• Criteo Audience: You don't need a Criteo audience ID as the audience gets created on the fly using the Engage audience name. This enables the names of audience segments to be consistent across Segment and Criteo.
• Batching events and support for large audiences: This destination supports batching which enables Criteo to receive large audiences without discrepancies.
• Near real time audience updates: Actions destination helps Criteo receive real-time events and add or remove users from Criteo audiences appropriately.

Before connecting to the Criteo Audiences (Actions) destination, you must create a Criteo API Marketing Solutions app to generate your app credentials (client ID and secret) as per the guidelines in Criteo's Developer's Portal.

You will also need your Criteo Advertiser ID. Please reach out to your Criteo Account Strategist to get this ID.

1. From your Segment workspace, go to Connections > Catalog and click Destinations.
2. Search for Criteo Audiences in the Destinations Catalog and select the destination.
3. Click Configure Criteo Audiences.
4. Select the space in Engage to use as the Source as this destination only supports sending Engage Audiences to Criteo.
5. On the Settings tab, name your destination. For example, Criteo audiences – <audience name>.
6. Enter your Criteo Advertiser ID, API client ID and client secret.
7. Click Save Changes.
8. In the Mappings tab, click New Mapping and select Add Users to Audience. To hash emails before you send them to Criteo, select yes in the Hash Emails dropdown. By default, emails are not hashed before you send them to Criteo; however, Criteo will hash the emails before storing them in our system. DO NOT change any other default settings.
9. Under the Configure actions fields, set Enable Batching to Yes and click Save.
10. Repeat steps 8 and 9 for Remove Users from Audience.
11. Enable both mappings.
12. Go to the Settings tab and Enable the destination.
13. Select your space, and navigate to Engage > Audiences. Select the source audience that you want to send to your Criteo Audiences destination.
14. Click Add Destinations and select the Criteo Audience destination you created. In the settings that appear on the right-hand side, toggle the Send Track option on and disable Send Identify. Click Save.

Your Criteo destination is now ready to receive audiences, and your Persona audiences now reflect in your Criteo Advertiser dashboard. Be aware, it takes 12-24 hours for the number of identifiers to populate in Criteo's Management Center.

Build your own Mappings. Combine supported triggers with the following Criteo Audiences-supported actions:

• Remove users from Audience
• Add users to Audience

Remove users from Criteo audience by connecting to Criteo API

Remove users from Audience is a Cloud action. The default Trigger is type = "track" and event = "Audience Exited"

Add users from Criteo audience by connecting to Criteo API

Add users to Audience is a Cloud action. The default Trigger is type = "track" and event = "Audience Entered"

Please discontinue use of the legacy Criteo destination. Follow the steps above to define your Segment Persona Audiences to be sent to Criteo.