> 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/the-trade-desk.md).

# The Trade Desk

Share audiences with The Trade Desk, as first-party data on your seat or as third-party data on its marketplace.

The Trade Desk connector shares your audiences with The Trade Desk.

<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>Mobile IDs, Third-party cookies</td></tr><tr><td><strong>Authentication</strong></td><td>Advertiser ID and secret key shared with your account manager</td></tr></tbody></table>

## Description

### What you can do with this connector

* Target a mediarithmics audience on the seat you share the segment with, as **first-party** data.
* Publish it to The Trade Desk's **third-party data marketplace**.

{% hint style="info" %}
Setting up the TTD marketplace requires a **custom integration**. Ask your account manager.
{% endhint %}

### Which identifiers are sent

* **Mobile IDs**
* **Third-party cookies**

## Connector setup

### Prerequisites

Give your account manager:

* your **AdvertiserId**;
* your **Secret Key**.

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

### Setup steps

{% stepper %}
{% step %}
**Send your AdvertiserId and Secret Key to your account manager.**

They return the **Credential Name**.
{% endstep %}

{% step %}
**Select The Trade Desk connector and fill in its configuration.**

<table data-search="false"><thead><tr><th width="300">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>Credential Name</strong></td><td>Provided by your mediarithmics account manager.</td></tr><tr><td><strong>Segment Name</strong></td><td>The name shown in The Trade Desk. Defaults to the mediarithmics segment name.</td></tr><tr><td><strong>Time to leave</strong></td><td>The lifespan of the data in The Trade Desk, <strong>in minutes</strong>. Defaults to 365 days - <code>525600</code>.</td></tr><tr><td><strong>Data Center</strong></td><td>The data centre closest to the users you are sharing.</td></tr><tr><td><strong>Data activation type</strong></td><td><code>FIRST_PARTY</code> or <code>THIRD_PARTY</code>.</td></tr><tr><td><strong>Identifying resources</strong></td><td>The data to send to TTD.</td></tr></tbody></table>

{% hint style="warning" %}
To activate `THIRD_PARTY` segments you must first design the **taxonomy and rate settings** for each segment on the destination platform. The Trade Desk documents the [integration process](https://partner.thetradedesk.com/v3/portal/data/doc/DataThirdPartyIntegrationAudience#process) and [taxonomy design](https://partner.thetradedesk.com/v3/portal/data/doc/DataTaxonomyDesign).
{% 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

#### Time to leave is in minutes, not days?

Minutes. The default `525600` is 365 days.

#### My third-party segment is not activating.

The taxonomy and rate settings have to be designed on The Trade Desk side **before** activation. See TTD's integration process documentation.

## Partner documentation

The Trade Desk documents its own platform at <https://partner.thetradedesk.com/>. 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/the-trade-desk.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.