> For the complete documentation index, see [llms.txt](https://docs.mediarithmics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mediarithmics.io/connectors/destinations/criteo/direct.md).

# Direct

Set up Criteo retargeting from mediarithmics audiences, using cookies, mobile IDs or emails.

The Criteo Audience Feed lets you set up retargeting campaigns with Criteo, using audiences already built in mediarithmics.

<table data-search="false"><thead><tr><th width="220">Connection</th><th></th></tr></thead><tbody><tr><td><strong>Type</strong></td><td>Server-side</td></tr><tr><td><strong>Category</strong></td><td><a href="/connectors/partner-types/dsp.md">DSP</a></td></tr><tr><td><strong>Identifiers sent</strong></td><td>Cookies, Mobile IDs, Email identifiers, Emails from the Profile object</td></tr><tr><td><strong>Authentication</strong></td><td>Authorisation link, approved with admin rights on your Criteo account</td></tr></tbody></table>

## Description

### What you can do with this connector

* Retarget on Criteo with an audience computed in the CDP.
* Reconcile on cookies, mobile IDs or emails - including emails held in the user profile.

### Which identifiers are sent

* **Cookies**
* **Mobile IDs**
* **Email identifiers**
* **Emails** contained in the Profile object

Criteo is reached by several connectors and they behave differently - [the comparison is on the Criteo page](/connectors/destinations/criteo.md).

## Connector setup

### Prerequisites

* Your **advertiser\_id**, for CRM synchronisation, given to your account manager.
* **Admin rights** on your Criteo account.

{% hint style="warning" %}
Cookie matching must be activated on your organisation. Contact your account manager to confirm.
{% endhint %}

### Authentication

Once you have supplied the advertiser ID, mediarithmics generates a link and sends it back to you. Clicking it - with admin rights on your Criteo account - authorises mediarithmics to push information to Criteo on your behalf.

### Setup steps

{% stepper %}
{% step %}
**Send your advertiser\_id to your account manager.**
{% endstep %}

{% step %}
**Open the authorisation link mediarithmics returns, signed in with Criteo admin rights.**
{% endstep %}

{% step %}
**Select the Criteo connector and fill in its configuration.**

<table data-search="false"><thead><tr><th width="280">Field</th><th></th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>Identifies the feed on the platform.</td></tr><tr><td><strong>Credential name</strong></td><td>Provided by your mediarithmics account manager.</td></tr><tr><td><strong>Identifier to send</strong></td><td>The identifier to send to Criteo.</td></tr></tbody></table>
{% endstep %}

{% step %}
**To send emails, fill in the advanced fields.**

<table data-search="false"><thead><tr><th width="280">Field</th><th></th></tr></thead><tbody><tr><td><strong>Fields to use</strong></td><td>Emails from the user identifiers, emails stored in the profile, or both.</td></tr><tr><td><strong>Compartment Ids to use</strong></td><td>The compartments the emails are stored in. Several can be given, comma-separated.</td></tr></tbody></table>

{% hint style="warning" %}
Sending emails to Criteo **requires** the advanced fields - the source of the emails has to be selected explicitly.
{% endhint %}
{% endstep %}
{% endstepper %}

Creating and activating the feed on a segment is covered in the **Audience & Activation** section, under *Activate your audiences › Send your first-party data to a destination*.

## Good to know

{% hint style="warning" %}
Following CNIL guidance on cookies and trackers, make sure that:

1. the partner is correctly named when you collect user consent for targeting purposes, or the equivalent;
2. the partner is named in your cookie policy - these partners may drop a cookie on your users' browsers from your websites.
   {% endhint %}

## FAQ

#### My emails are not reaching Criteo. What did I miss?

The advanced fields. **Fields to use** and **Compartment Ids to use** must be filled in for emails to be sent.

#### Should I use Direct or S2S?

Direct if you need emails or mobile IDs. [S2S](/connectors/destinations/criteo/s2s.md) only carries cookies.

## Partner documentation

Criteo documents its own platform at <https://help.criteo.com/kb/en>. Use it for anything that happens on the partner side of this connector: account setup, the fields the partner expects, and its own limits.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mediarithmics.io/connectors/destinations/criteo/direct.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.