> 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/connectors-on-request.md).

# Connectors on request

Partners reachable through your account manager, and what is considered when a new connector is requested.

Not every partner mediarithmics can reach has a connector page. Some are available through your account team rather than in self-service, and some do not exist yet.

## Partners available through your account manager

These partners are supported, but their setup is handled by your account team. Contact them to find out what is possible for your organisation and what it requires.

<table data-search="false"><thead><tr><th width="300">Partner</th><th></th></tr></thead><tbody><tr><td>Adelphic</td><td><a href="/connectors/partner-types/dsp.md">DSP</a></td></tr><tr><td>Adobe Campaign Classic (ex Neolane)</td><td><a href="/connectors/partner-types/esp-and-marketing-automation.md">ESP &#x26; marketing automation</a></td></tr><tr><td>Adventori</td><td><a href="/connectors/partner-types/esp-and-marketing-automation.md">ESP &#x26; marketing automation</a></td></tr><tr><td>Easyence</td><td><a href="/connectors/partner-types/dmp-and-data-providers.md">DMP &#x26; data providers</a></td></tr><tr><td>Equativ curation</td><td><a href="/connectors/partner-types/ssp-and-ad-servers.md">SSP &#x26; ad servers</a> - curation</td></tr><tr><td>First-Id</td><td>Network ID - see <em>Setup &#x26; Monitor › User identity › Network IDs</em></td></tr><tr><td>Hawk</td><td><a href="/connectors/partner-types/dsp.md">DSP</a>, through the <a href="/connectors/destinations/identifiers-exporter.md">Identifiers Exporter</a></td></tr><tr><td>ID5</td><td>Network ID - see <em>Setup &#x26; Monitor › User identity › Network IDs</em></td></tr><tr><td>LiveRamp</td><td>Onboarder</td></tr><tr><td>MediaMath</td><td><a href="/connectors/partner-types/dsp.md">DSP</a></td></tr><tr><td>NP6</td><td><a href="/connectors/partner-types/esp-and-marketing-automation.md">ESP &#x26; marketing automation</a></td></tr><tr><td>RTB House</td><td><a href="/connectors/partner-types/dsp.md">DSP</a>, through the <a href="/connectors/destinations/identifiers-exporter.md">Identifiers Exporter</a></td></tr><tr><td>Squadata</td><td><a href="/connectors/partner-types/dsp.md">DSP</a></td></tr><tr><td>Utiq</td><td>Network ID - see <em>Setup &#x26; Monitor › User identity › Network IDs</em></td></tr><tr><td>Weborama</td><td><a href="/connectors/partner-types/dmp-and-data-providers.md">DMP &#x26; data providers</a></td></tr><tr><td>Xandr curation</td><td><a href="/connectors/partner-types/ssp-and-ad-servers.md">SSP &#x26; ad servers</a> - curation</td></tr></tbody></table>

{% hint style="info" %}
**Prebid.js** is not a connector. It is one of the tools that can consume what mediarithmics writes to the browser - see [Browser Local Storage](/connectors/destinations/browser-local-storage.md) and [Curated Audiences (SDA)](/connectors/destinations/curated-audiences-sda.md), which includes a worked Prebid.js example.
{% endhint %}

## Requesting a new partner connector

Talk to your account manager. To evaluate the request, they will want to know:

* **What are your use cases?**
* **What will your usage frequency be** - daily, weekly, one shot?
* **What type of audiences, and what volumes**, will you need to send?
* **What return do you expect?** For example the cost avoided by not refreshing CRM data by hand, or an improvement in click-through rate.
* **Which identifiers have to be sent** - the partner cookie ID, CRM IDs, SHA-256 emails? And are they already available in the mediarithmics platform?
* **Where do the legal agreements stand?** Have you contracted with the partner?
* **Do you have a contact at the partner**, preferably a technical one?

## 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>Connectors</strong></td><td>Every documented connector, by partner type and by name.</td><td><a href="/connectors/readme.md">Getting started</a></td></tr><tr><td><strong>Identifiers Exporter</strong></td><td>The route several on-request partners are served through.</td><td><a href="/connectors/destinations/identifiers-exporter.md">Identifiers Exporter</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/connectors-on-request.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.