|
| 1 | +--- |
| 2 | +title: Criteo Audiences (Actions) Destination |
| 3 | +hidden: true |
| 4 | +hide-personas-partial: true |
| 5 | +hide-boilerplate: false |
| 6 | +hide-dossier: true |
| 7 | +id: |
| 8 | +--- |
| 9 | +{% include content/plan-grid.md name="actions" %} |
| 10 | + |
| 11 | +Criteo Audiences (Actions) enables advertisers to send Segment Persona Audiences to Criteo using Criteo's Audience API. |
| 12 | + |
| 13 | +By using Segment's Persona Audiences with Criteo, you can increase traffic and drive conversions with hyper-relevant ads that promote product discovery. |
| 14 | + |
| 15 | +## Benefits of Criteo Audiences (Actions) |
| 16 | + |
| 17 | +Benefits of the Critero Audiences (Actions) destination include: |
| 18 | +- **Improved email matching**: This integration creates a direct connection between Segment and Criteo for a higher match rate of email identifiers. |
| 19 | + |
| 20 | + |
| 21 | +- **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. |
| 22 | + |
| 23 | +- **Criteo Audience**: You don't need a Criteo audience ID as the audience gets created on the fly using the Personas audience name. This enables the names of audience segments to be consistent across Segment and Criteo. |
| 24 | + |
| 25 | +- **Batching events and support for large audiences**: This destination supports batching which enables Criteo to receive large audiences without discrepancies. |
| 26 | + |
| 27 | +- **Near real time audience updates**: Actions destination helps Criteo receive real-time events and add or remove users from Criteo audiences appropriately. |
| 28 | + |
| 29 | +## Getting Started |
| 30 | + |
| 31 | +### Prerequisites: |
| 32 | + |
| 33 | +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](https://developers.criteo.com/marketing-solutions/docs/onboarding-checklist){:target="_blank"}. |
| 34 | + |
| 35 | +You will also need your Criteo Advertiser ID. Please reach out to your Criteo Account Strategist to get this ID. |
| 36 | + |
| 37 | +### To Add the Criteo Audiences Destination: |
| 38 | + |
| 39 | +1. From your Segment workspace, go to **Connections > Catalog** and click **Destinations**. |
| 40 | + |
| 41 | +2. Search for **Criteo Audiences** in the Destinations Catalog and select the destination. |
| 42 | + |
| 43 | +3. Click **Configure Criteo Audiences**. |
| 44 | + |
| 45 | +4. Choose your **Personas** space for the Source as this destination only supports sending Personas Audiences to Criteo. |
| 46 | + |
| 47 | +On the **Settings** tab, name your destination. For example, Criteo audiences – <audience name>. |
| 48 | + |
| 49 | +6. Enter your Criteo Advertiser ID, API client ID and client secret. |
| 50 | + |
| 51 | +7. Click **Save Changes**. |
| 52 | + |
| 53 | +8. In the **Mappings** tab, click **New Mapping** and select **Add Users to Audience**. Don't change any defaults. |
| 54 | + |
| 55 | +9. Under the **Configure actions fields**, set **Enable Batching** to *Yes* and click **Save**. |
| 56 | + |
| 57 | +7. Repeat steps 8 and 9 for **Remove Users from Audience**. |
| 58 | + |
| 59 | +8. **Enable** both mappings. |
| 60 | + |
| 61 | +9. Go to the **Settings** tab and **Enable** the destination. |
| 62 | + |
| 63 | +10. Go to your **Personas** space and click the **Audiences** tab. Select the source audience that you want to send to your Criteo Audiences destination. |
| 64 | + |
| 65 | +11. 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**. |
| 66 | + |
| 67 | +Your Criteo destination is now ready to receive audiences, and your Persona audiences now reflect in your Criteo Advertiser dashboard. Please note that it takes approximately 12-24 hours for the number of identifiers to populate in Criteo's Management Center. |
| 68 | + |
| 69 | +> warning "" |
| 70 | +> **NOTE**: Currently, you can only connect **ONE** personas audience to a single instance of Criteo Audience destination. If you have multiple audiences, repeat the above process to create a new Criteo audience destination and connect the audience to new destination each time. |
| 71 | +
|
| 72 | +{% include components/actions-fields.html %} |
| 73 | + |
| 74 | +## Legacy Destination |
| 75 | + |
| 76 | +Please discontinue use of the legacy Criteo destination. Follow the steps above to define your Segment Persona Audiences to be sent to Criteo. |
0 commit comments