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

# Adot

Push audiences to the Adot DSP to run display and video campaigns.

The Adot connector pushes your audiences to the Adot Demand Side Platform, so you can run media campaigns - display, video and the rest.

<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, Hashed emails, Mobile IDs</td></tr><tr><td><strong>Authentication</strong></td><td>Adot API authorisation token, shared with your account manager</td></tr></tbody></table>

## Description

### What you can do with this connector

* Run Adot media campaigns against an audience built in mediarithmics.

### Which identifiers are sent

* **Cookies**
* **Hashed emails**
* **Mobile IDs**

## Connector setup

### Prerequisites

* An **API authorisation token**, provided by your Adot account manager. Transfer it to your mediarithmics account manager **securely**.

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

### Authentication

Once your mediarithmics account manager has the token, they complete the configuration. You then only fill in the feed itself.

### Setup steps

{% stepper %}
{% step %}
**Get the API authorisation token from your Adot account manager and pass it securely to mediarithmics.**
{% endstep %}

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

<table data-search="false"><thead><tr><th width="260">Field</th><th></th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>Identifies the feed within the platform.</td></tr><tr><td><strong>Identifying resources</strong></td><td>The identifier types to send to Adot.</td></tr></tbody></table>
{% 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

#### Where does the API authorisation token come from?

Your Adot account manager, not mediarithmics. Pass it on securely.

## Partner documentation

`TODO` - Adot publishes no public product documentation. Ask your mediarithmics account manager for the partner-side setup guide.


---

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