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

# Teads

Share first-party audiences with Teads, to retarget or exclude them in Teads campaigns.

The Teads connector shares your first-party audiences directly with Teads, so advertisers can retarget or exclude their own audiences in campaigns running on the Teads platform.

<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>Teads third-party cookies, Mobile IDs (IDFA / AAID)</td></tr><tr><td><strong>Authentication</strong></td><td>Teads advertiser ID, plus cookie sync activated by your account manager</td></tr></tbody></table>

## Description

### How it works

The connector uses two mechanisms together:

* **Server-side file transfer** - it generates and uploads flat files, Taxonomy and User Membership, to a secure S3 bucket.
* **Cookie synchronisation** - it syncs mediarithmics and Teads cookies so users match accurately.

### What you can do with this connector

* Retarget your own first-party audiences on Teads.
* Exclude them from a Teads campaign.

### Which identifiers are sent

* **Teads third-party cookies** - requires cookie sync
* **Mobile IDs** - IDFA / AAID

## Connector setup

### Prerequisites

**1. Consent management (TCF).** The cookie synchronisation only works where consent is managed through the IAB TCF framework.

* Teads is registered as **Vendor 132**.
* mediarithmics is registered as **Vendor 184**.

**2. Cookie synchronisation.** The sync is triggered only on websites carrying a TCF-compliant CMP. mediarithmics triggers it from your website to match the right audiences. Make sure the Teads vendor ID is listed and authorised in your CMP.

{% hint style="info" %}
Contact your mediarithmics account manager to activate the cookie sync on the mediarithmics side.
{% endhint %}

* Your **Teads advertiser ID** - your Teads account identifier. It is a required property on the feed.

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

**Users expire rather than being deleted.** Teads does not currently support explicit delete instructions for users in a segment, so the connector applies a maximum **TTL of 30 days** to every user sent.

* A user still in the segment has their TTL refreshed by regular updates.
* A user who leaves the segment, or withdraws consent, stops being sent and is removed from the Teads audience **after 30 days**.

**Upload frequency.** Files are uploaded when they reach **100 MB**, or at least **once per hour**, whichever comes first.

## FAQ

#### How are user deletions handled?

Through the 30-day TTL described above, not through an explicit delete. Plan for that delay when excluding users.

#### Can I use this connector for CTV or Panorama IDs?

Not at this stage. Teads supports them, but this connector currently carries Teads cookies and mobile IDs (IDFA / AAID) only. Other IDs may follow.

#### Does this connector support the Teads Data Marketplace?

No. The scope is an advertiser retargeting or excluding their own first-party audiences. Marketplace synchronisation, including CPMs, is not supported.

## Partner documentation

Teads documents its own platform at <https://help.teads.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/teads.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.