|
7 | 7 | --- |
8 | 8 | {% include content/plan-grid.md name="actions" %} |
9 | 9 |
|
10 | | -Criteo Audiences (Actions) enables advertisers to send Segment Persona Audiences seamlessly to Criteo using Criteo's Audience API. |
| 10 | +Criteo Audiences (Actions) enables advertisers to send Segment Persona Audiences to Criteo using Criteo's Audience API. |
11 | 11 |
|
12 | | -By leveraging Segment's Persona Audiences with Criteo, you have the opportunity to get traffic and drive conversions from new and existing customer as well as re-engaging existing customers with hyper-relevant ads that promote product discovery. |
| 12 | +By using Segment's Persona Audiences with Criteo, you have the opportunity to get traffic and drive conversions from new and existing customers as well as re-engaging existing customers with hyper-relevant ads that promote product discovery. |
13 | 13 |
|
14 | | -# Benefits of Criteo Audiences (Actions) |
| 14 | +## Benefits of Criteo Audiences (Actions) |
15 | 15 |
|
16 | | -This new integration creates a direct connection between Segment and Criteo for a higher match rate of email identifiers. |
| 16 | +This integration creates a direct connection between Segment and Criteo for a higher match rate of email identifiers. Other benefits include: |
17 | 17 |
|
18 | | -- **Fewer settings**: Unlike our Filter destination, this destination does not require any custom copy and paste code. All that is needed is Advertiser id and Criteo API credentials. |
| 18 | +- **Fewer settings**: Unlike Criteo's Filter destination, this destination doesn't require any custom copy and paste code. You only need the Advertiser ID and the Criteo API credentials. |
19 | 19 |
|
20 | | -- **Criteo Audience**: creation on the Fly: You do not need a Criteo audience id as the audience gets created on the fly using the Personas audience name. That way audience segment names are consistent across the two platforms Segment and Criteo. |
| 20 | +- **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 audience Segment names to be consistent across Segment and Criteo. |
21 | 21 |
|
22 | 22 | - **Batching events and support for large audiences**: This destination supports batching which enables Criteo to receive large audiences without discrepancies. |
23 | 23 |
|
24 | | -- **Near real time audience updates**: Actions destination helps Criteo receive real time events and add or remove users from Criteo audiences appropriately. |
| 24 | +- **Near real time audience updates**: Actions destination helps Criteo receive real-time events and add or remove users from Criteo audiences appropriately. |
25 | 25 |
|
26 | | -# Getting Started |
| 26 | +## Getting Started |
27 | 27 |
|
28 | 28 | ### Prerequisites: |
29 | 29 |
|
30 | | -Before connecting to 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). |
| 30 | +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). |
31 | 31 |
|
32 | 32 | You will also need your Criteo Advertiser ID. Please reach out to your Criteo Account Strategist to get this ID. |
33 | 33 |
|
34 | 34 | ### To Add the Criteo Audiences Destination: |
35 | 35 |
|
36 | | -1. From your Segment workspace, go to **Connections > Catalog** and click Destinations. |
| 36 | +1. From your Segment workspace, go to **Connections > Catalog** and click **Destinations**. |
37 | 37 |
|
38 | 38 | 2. Search for **Criteo Audiences** in the Destinations Catalog and select the destination. |
39 | 39 |
|
40 | | -3. Click **Configure Criteo Audiences** in the top-right corner of the screen. |
| 40 | +3. Click **Configure Criteo Audiences**. |
41 | 41 |
|
42 | | -4. Source should be your **Personas** space as this destination only supports sending Personas Audiences to Criteo. |
| 42 | +4. Choose your **Personas** space for the Source as this destination only supports sending Personas Audiences to Criteo. |
43 | 43 |
|
44 | | -5. On the **Settings** tab, name your destination appropriately, for example, Criteo audiences – <audience name>. Enter your Criteo Advertiser ID, API client id and client secret. Hit **Save Changes**. |
| 44 | +5. On the **Settings** tab, name your destination. For example, Criteo audiences – <audience name>. |
45 | 45 |
|
46 | | -6. In the **Mappings** tab, click **New Mapping** and select **Add Users to Audience**. Do not change any defaults. Under **Configure Actions Fields**, set **Enable Batching** to **Yes** and hit **Save**. |
| 46 | +6. Enter your Criteo Advertiser ID, API client ID and client secret. |
47 | 47 |
|
48 | | -7. Repeat the same process for **Remove Users from Audience**. |
| 48 | +7. Click **Save Changes**. |
49 | 49 |
|
50 | | -8. **Enable** both mappings. You can then **Enable** the destination from **Settings** tab. |
| 50 | +8. In the **Mappings** tab, click **New Mapping** and select **Add Users to Audience**. Don't change any defaults. |
51 | 51 |
|
52 | | -9. You can now go to your **Personas space > Audiences** tab and select the source audience that you want to send to your newly created Criteo Audiences destination. |
| 52 | +9. Under the **Configure actions fields**, set **Enable Batching** to *Yes* and click **Save**. |
53 | 53 |
|
54 | | -10. Click **Add Destinations** and select the newly created destination. On the settings that appear on the right-hand side, toggle **Send Track** option on and disable **Send Identify**. Hit **Save**. |
| 54 | +7. Repeat steps 8 and 9 for **Remove Users from Audience**. |
55 | 55 |
|
56 | | -Your Criteo destination should be ready to receive audiences! |
57 | | -Your Persona audiences will reflect in your Criteo Advertiser dasboard. Please note that it will take approximately 12-24 hours for the number of identifiers to populate in Criteo's Management Center |
| 56 | +8. **Enable** both mappings. |
| 57 | + |
| 58 | +9. Go to the **Settings** tab and **Enable** the destination. |
| 59 | + |
| 60 | +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. |
| 61 | + |
| 62 | +11. Click **Add Destinations** and select the Criteo Audience destination you created. On the settings that appear on the right-hand side, toggle the **Send Track** option on and disable **Send Identify**. Click **Save**. |
| 63 | + |
| 64 | +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. |
58 | 65 |
|
59 | 66 | > warning "" |
60 | 67 | > **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. |
61 | 68 |
|
62 | 69 | {% include components/actions-fields.html %} |
63 | 70 |
|
64 | | -# Legacy Destination |
| 71 | +## Legacy Destination |
65 | 72 |
|
66 | 73 | 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