> 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.md).

# Criteo

The two Criteo audience feeds, and which identifiers each one carries.

Both Criteo connectors set up retargeting campaigns from audiences already built in mediarithmics. The difference is what they can match on.

## Which connector to use

<table data-search="false"><thead><tr><th width="300">Connector</th><th></th></tr></thead><tbody><tr><td><a href="/connectors/destinations/criteo/direct.md"><strong>Direct</strong></a></td><td>Sends cookies, mobile IDs and emails - including emails held in the user profile. Requires an authorisation link approved with admin rights on your Criteo account.</td></tr><tr><td><a href="/connectors/destinations/criteo/s2s.md"><strong>S2S</strong></a></td><td>Sends cookies only. Set up with your <code>criteo_partner_id</code> alone.</td></tr></tbody></table>

Pick **Direct** if you need to reconcile on anything other than cookies. **S2S** is the lighter setup when a cookie match is enough.

## What each connector sends

<table data-search="false"><thead><tr><th width="220">Connector</th><th width="150">Type</th><th></th></tr></thead><tbody><tr><td><a href="/connectors/destinations/criteo/direct.md">Direct</a></td><td>Server-side</td><td>Cookies, Mobile IDs, Email identifiers, Emails from the Profile object</td></tr><tr><td><a href="/connectors/destinations/criteo/s2s.md">S2S</a></td><td>Server-side</td><td>Cookies</td></tr></tbody></table>

Both require **cookie matching activated on your organisation**. Contact your account manager to confirm.

## 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.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.