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

# Getting started

Every platform mediarithmics connects to - browsable by partner type, or by name.

This section documents every platform mediarithmics connects to, one page per connector. Each page follows the same shape: what the partner is and what the connector does, which identifiers are sent, what you need in place before setting it up, how it authenticates, and the answers to the questions that come up most often.

There are three ways in.

<table data-view="cards" data-search="false"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Partner types</strong></td><td>Start here if you know the <em>kind</em> of platform you need - a DSP, an ESP, an SSP - but not which one.</td><td><a href="/connectors/partner-types/dsp.md">DSP</a></td></tr><tr><td><strong>Destinations</strong></td><td>Everything you send audiences <em>to</em>, listed by partner name. Start here if you already know the partner.</td><td><a href="/connectors/destinations/ab-tasty.md">AB Tasty</a></td></tr><tr><td><strong>Sources</strong></td><td>What brings data <em>into</em> mediarithmics: your cloud data warehouse.</td><td><a href="/connectors/sources/google-bigquery.md">Google BigQuery</a></td></tr></tbody></table>

{% hint style="info" %}
This section is about **specific partners**. The concepts behind them - what a feed is, what a destination is, how to create one on a segment and how to monitor it - live in the **Audience & Activation** section, under *Activate your audiences*.
{% endhint %}

## Browse by partner type

Each type page explains what that kind of platform does, what it needs from your CDP, and which connectors reach one.

<table data-search="false"><thead><tr><th width="300">Type</th><th></th></tr></thead><tbody><tr><td><a href="/connectors/partner-types/dsp.md">DSP</a></td><td>Buy media programmatically against your audiences. <strong>18 connectors.</strong></td></tr><tr><td><a href="/connectors/partner-types/ssp-and-ad-servers.md">SSP &#x26; ad servers</a></td><td>Enrich and monetise your own inventory, including curation. <strong>10 connectors.</strong></td></tr><tr><td><a href="/connectors/partner-types/social-and-retail-media.md">Social &#x26; retail media</a></td><td>Reach walled gardens by matching identifiers against their account base. <strong>9 connectors.</strong></td></tr><tr><td><a href="/connectors/partner-types/esp-and-marketing-automation.md">ESP &#x26; marketing automation</a></td><td>Email, mobile messaging and journeys, to people you can already contact. <strong>6 connectors.</strong></td></tr><tr><td><a href="/connectors/partner-types/on-site-personalisation.md">On-site personalisation</a></td><td>Adapt your own site to the segment a visitor is in, usually without sending anything anywhere. <strong>4 connectors.</strong></td></tr><tr><td><a href="/connectors/partner-types/data-sharing-and-export.md">Data sharing &#x26; export</a></td><td>Files, browser signals, and sharing with another mediarithmics datamart. <strong>4 connectors.</strong></td></tr><tr><td><a href="/connectors/partner-types/dmp-and-data-providers.md">DMP &#x26; data providers</a></td><td>Platforms whose business is redistributing audience data. <strong>1 connector.</strong></td></tr><tr><td><a href="/connectors/partner-types/data-warehouse.md">Data warehouse</a></td><td>Connect the warehouse where the rest of your data lives. <strong>2 connectors.</strong></td></tr></tbody></table>

## The distinction that matters

Partner type tells you what a platform is for. **Connection type** tells you how the connector behaves, and it is the more consequential of the two. Every connector page states it in its first table.

<table data-search="false"><thead><tr><th width="280">Type</th><th></th></tr></thead><tbody><tr><td><strong>Server-side</strong></td><td>Identifiers travel server to server. The whole audience is sent, including history, and segment exits are communicated to the partner.</td></tr><tr><td><strong>Client-side (pixel)</strong></td><td>A partner pixel fires in the visitor's browser. mediarithmics sends no identifiers.</td></tr><tr><td><strong>Client-side (local storage)</strong></td><td>Segment membership is written to the visitor's browser, where an on-site partner reads it. Nothing leaves your CDP.</td></tr></tbody></table>

{% hint style="warning" %}
Both client-side types share three consequences: volumes **ramp up** as users visit your sites rather than appearing at once, a segment **exit cannot be signalled** to the partner, and **nothing is sent** when the tag is blocked or consent is refused. Several partners offer both a server-side and a client-side connector, and running both is usually the recommendation.
{% endhint %}

## Find a partner by name

Where a partner has several connectors, the parent page compares them and tells you which to pick.

The **Identifiers sent** column is the fastest way to rule a partner in or out: a connector that cannot carry an identifier you hold will run cleanly and reach nobody. Each connector page then explains the detail - which hash, which combination, and what happens when an identifier is missing.

<table data-search="false"><thead><tr><th width="250">Partner</th><th width="210">Type</th><th>Identifiers sent</th></tr></thead><tbody><tr><td><a href="/connectors/destinations/ab-tasty.md">AB Tasty</a></td><td>On-site personalisation</td><td>None - segment names only, kept in the browser</td></tr><tr><td><a href="/connectors/destinations/active-agent.md">Active Agent</a></td><td>DSP</td><td>Cookies</td></tr><tr><td><a href="/connectors/destinations/adform.md">AdForm</a></td><td>DSP</td><td>Mobile IDs, third-party cookies (AdForm cookies)</td></tr><tr><td><a href="/connectors/destinations/adot.md">Adot</a></td><td>DSP</td><td>Cookies, Hashed emails, Mobile IDs</td></tr><tr><td><a href="/connectors/destinations/adswizz.md">AdsWizz</a></td><td>DSP</td><td>AdsWizz Listener IDs (third-party cookies), Mobile IDs (IDFA / AAID), IP addresses (IPv4 and IPv6)</td></tr><tr><td><a href="/connectors/destinations/airship.md">Airship</a></td><td>ESP &#x26; marketing automation</td><td>Emails, Channels, Named User, Open Channel</td></tr><tr><td><a href="/connectors/destinations/amazon-ads.md">Amazon Ads</a> - 2 connectors + consent</td><td>DSP</td><td>Emails, profile data, mobile IDs, cookies</td></tr><tr><td><a href="/connectors/destinations/batch.md">Batch CEP</a></td><td>ESP &#x26; marketing automation</td><td>Mobile IDs, User account IDs, Device IDs</td></tr><tr><td><a href="/connectors/destinations/beeswax.md">Beeswax</a></td><td>DSP</td><td>Cookies, Mobile IDs, Email identifiers, User account IDs</td></tr><tr><td><a href="/connectors/destinations/braze.md">Braze</a></td><td>ESP &#x26; marketing automation</td><td>User account IDs</td></tr><tr><td><a href="/connectors/destinations/brevo-ex-sendinblue.md">Brevo (ex SendInBlue)</a></td><td>ESP &#x26; marketing automation</td><td>Unencrypted emails, Profile information</td></tr><tr><td><a href="/connectors/destinations/browser-local-storage.md">Browser Local Storage</a></td><td>On-site personalisation</td><td>None - segment names only, kept in the browser</td></tr><tr><td><a href="/connectors/destinations/criteo.md">Criteo</a> - 2 connectors</td><td>DSP</td><td>Cookies, mobile IDs, email identifiers</td></tr><tr><td><a href="/connectors/destinations/curated-audiences-sda.md">Curated Audiences (SDA)</a></td><td>Data sharing &#x26; export</td><td>None - taxonomy segment IDs only, kept in the browser</td></tr><tr><td><a href="/connectors/destinations/emarsys.md">Emarsys</a></td><td>ESP &#x26; marketing automation</td><td>Unencrypted emails, User accounts (Emarsys user IDs)</td></tr><tr><td><a href="/connectors/destinations/equativ.md">Equativ</a></td><td>SSP &#x26; ad servers</td><td>Cookies, MAIDs, Account IDs, ID5 IDs, IP addresses</td></tr><tr><td><a href="/connectors/destinations/freewheel.md">FreeWheel</a> - 4 connectors</td><td>SSP &#x26; ad servers</td><td>Cookies, mobile IDs, TV IDs, user account IDs, IP addresses; none for the pixel</td></tr><tr><td><a href="/connectors/destinations/google.md">Google</a> - 5 connectors + consent</td><td>DSP, SSP &#x26; ad servers</td><td>Cookies, mobile and TV advertising IDs, hashed emails, phone numbers, PPIDs, user account IDs, profile data; none for the pixel</td></tr><tr><td><a href="/connectors/sources/google-bigquery.md">Google BigQuery</a></td><td>Data warehouse - <strong>Source</strong></td><td>Whatever your BigQuery datasets expose to the service account</td></tr><tr><td><a href="/connectors/destinations/identifiers-exporter.md">Identifiers Exporter</a></td><td>Data sharing &#x26; export</td><td>Cookies, Mobile IDs, Email identifiers, Profile data</td></tr><tr><td><a href="/connectors/destinations/index-exchange.md">Index Exchange</a></td><td>SSP &#x26; ad servers</td><td>Mobile advertising IDs (MAID), Universal IDs (UTIQ MartechPass mobile, ID5 decrypted), IP addresses</td></tr><tr><td><a href="/connectors/destinations/kameleoon.md">Kameleoon</a> - 2 connectors</td><td>On-site personalisation</td><td>mediarithmics <code>vector_id</code> server-side; none client-side</td></tr><tr><td><a href="/connectors/destinations/linkedin.md">LinkedIn</a></td><td>Social &#x26; retail media</td><td>Email identifiers, Mobile IDs (AAID only), Profile data</td></tr><tr><td><a href="/connectors/destinations/lotame.md">Lotame</a></td><td>DMP &#x26; data providers</td><td>Lotame IDs, Android GAID, Apple IDFA</td></tr><tr><td><a href="/connectors/destinations/magnite-ex-rubicon.md">Magnite (ex Rubicon)</a></td><td>SSP &#x26; ad servers</td><td>Cookies</td></tr><tr><td><a href="/connectors/destinations/mediarithmics-shared-segment.md">mediarithmics Shared Segment</a></td><td>Data sharing &#x26; export</td><td>One identifier resource per feed, plus a separate matching identifier</td></tr><tr><td><a href="/connectors/destinations/meta.md">Meta</a> - 2 connectors</td><td>Social &#x26; retail media</td><td>Email identifiers, mobile IDs, profile data; none for the pixel</td></tr><tr><td><a href="/connectors/destinations/microsoft-advertising.md">Microsoft Advertising</a></td><td>DSP</td><td>Email identifiers (SHA-256) only</td></tr><tr><td><a href="/connectors/destinations/pinterest.md">Pinterest</a></td><td>Social &#x26; retail media</td><td>Email hash (SHA-256), Mobile IDs, Phone number hashes</td></tr><tr><td><a href="/connectors/destinations/pubmatic.md">Pubmatic</a></td><td>SSP &#x26; ad servers</td><td>Mobile IDs, ID5 IDs</td></tr><tr><td><a href="/connectors/destinations/salesforce-marketing-cloud.md">SalesForce Marketing Cloud</a></td><td>ESP &#x26; marketing automation</td><td>Profile data only</td></tr><tr><td><a href="/connectors/destinations/segment-exporter.md">Segment Exporter</a></td><td>Data sharing &#x26; export</td><td>Cookies, Mobile IDs, Email identifiers, Profile data</td></tr><tr><td><a href="/connectors/destinations/snapchat.md">Snapchat</a> - 2 connectors</td><td>Social &#x26; retail media</td><td>Hashed emails, phone numbers, mobile IDs; none for the pixel</td></tr><tr><td><a href="/connectors/sources/snowflake.md">Snowflake</a></td><td>Data warehouse - <strong>Source</strong></td><td>Whatever the Snowflake database exposes to the service account</td></tr><tr><td><a href="/connectors/destinations/teads.md">Teads</a></td><td>DSP</td><td>Teads third-party cookies, Mobile IDs (IDFA / AAID)</td></tr><tr><td><a href="/connectors/destinations/the-trade-desk.md">The Trade Desk</a></td><td>DSP</td><td>Mobile IDs, Third-party cookies</td></tr><tr><td><a href="/connectors/destinations/tiktok.md">TikTok</a> - 2 connectors</td><td>Social &#x26; retail media</td><td>Hashed emails, mobile IDs, phone number hashes; none for the pixel</td></tr><tr><td><a href="/connectors/destinations/twitter-x.md">Twitter / X</a></td><td>Social &#x26; retail media</td><td>Email hash (SHA-256), Mobile IDs (IDFA, AAID or both)</td></tr><tr><td><a href="/connectors/destinations/xandr.md">Xandr</a> - 2 connectors</td><td>DSP</td><td>Cookies, mobile IDs, TV IDs, First ID, UTIQ MartechPass</td></tr><tr><td><a href="/connectors/destinations/yahoo-advertising.md">Yahoo Advertising</a></td><td>DSP</td><td>Mobile IDs, Emails (SHA-256), Cookies</td></tr></tbody></table>

Sixteen more partners are supported through your account manager rather than in self-service - see [Connectors on request](/connectors/connectors-on-request.md).

## Before you set one up

Three things are worth checking on any connector, before the configuration itself:

* **Which identifiers it accepts.** This is not a platform-wide list - one partner takes hashed emails and mobile advertising IDs, another only third-party cookies, another only a CRM ID. A well-built audience sent through an identifier the destination cannot resolve produces a feed that runs cleanly and reaches nobody.
* **Whether cookie matching is activated** on your organisation. Many connectors that carry cookies depend on it, and it is not on by default.
* **What the partner requires on their side.** Almost every connector needs an account, credentials, an ID exchange or an authorisation granted in the partner's own interface - and several of those authorisations expire in minutes.

## Related pages

<table data-view="cards" data-search="false"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Google</strong></td><td>The five Google connectors, and the consent rules common to all of them.</td><td><a href="/connectors/destinations/google.md">Google</a></td></tr><tr><td><strong>Connectors on request</strong></td><td>Partners available through your account manager, and how a new connector is evaluated.</td><td><a href="/connectors/connectors-on-request.md">Connectors on request</a></td></tr></tbody></table>


---

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