> 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/partner-types/ssp-and-ad-servers.md).

# SSP & ad servers

What SSPs, ad servers and curation platforms do with your first-party data, and which connectors reach them.

Where a [DSP](/connectors/partner-types/dsp.md) spends money, these platforms **earn** it. An **ad server** decides which creative to serve in a given slot; a **supply-side platform** sells your inventory to advertisers across exchanges; a **curation platform** packages audience segments into deals that buyers can transact against.

The CDP's role here is the mirror image of the DSP case: instead of telling a buyer who to chase, you enrich **your own inventory** with what you know about the visitor, so it commands a better price.

## What these connectors have in common

* **Your data stays attached to your inventory.** These connectors make an audience available for targeting or packaging inside a platform you already monetise through.
* **They mostly match on cookies and mobile IDs**, with some accepting network IDs such as ID5.
* **Several require the partner to register mediarithmics** - as a Data Provider, a Segment Provider, or through granted rights on your seat. That step happens on the partner's side, not ours, and it is the usual cause of a connector that silently delivers nothing.

## Connectors

<table data-search="false"><thead><tr><th width="330">Connector</th><th></th></tr></thead><tbody><tr><td><a href="/connectors/destinations/equativ.md">Equativ</a></td><td>SSP and ad server, plus Equativ Buyer Connect for curation. Cookies, MAIDs, account IDs, ID5, IP addresses.</td></tr><tr><td><a href="/connectors/destinations/freewheel.md">FreeWheel</a> - <a href="/connectors/destinations/freewheel/audience-manager.md">Audience Manager</a>, <a href="/connectors/destinations/freewheel/external-feed.md">External Feed</a>, <a href="/connectors/destinations/freewheel/file-sharing.md">File Sharing</a>, <a href="/connectors/destinations/freewheel/pixel.md">Pixel</a></td><td>Four connectors, each reaching a different FreeWheel product.</td></tr><tr><td><a href="/connectors/destinations/google/ad-manager-audience-api.md">Google Ad Manager - Audience API</a></td><td>Reaches Ad Exchange, Ad Manager and both DV360 tiers. Cookies, mobile IDs, TV IDs.</td></tr><tr><td><a href="/connectors/destinations/google/ad-manager-batch-upload.md">Google Ad Manager - Batch Upload</a></td><td>The only route carrying PPIDs.</td></tr><tr><td><a href="/connectors/destinations/index-exchange.md">Index Exchange</a></td><td>Marketplace for publishers and Marketplace Partners. MAIDs, UTIQ MartechPass, ID5, IP addresses.</td></tr><tr><td><a href="/connectors/destinations/magnite-ex-rubicon.md">Magnite (ex Rubicon)</a></td><td>Ad exchange. Cookies.</td></tr><tr><td><a href="/connectors/destinations/pubmatic.md">Pubmatic</a></td><td>SSP. Mobile IDs, ID5 IDs.</td></tr></tbody></table>

## Curation

Curation platforms let you package audience segments into deals buyers transact against, rather than targeting campaigns directly. **Equativ Buyer Connect** is served by the [Equativ](/connectors/destinations/equativ.md) connector - it is one of the two products that connector feeds. **Xandr curation** is available through your account manager; see [Connectors on request](/connectors/connectors-on-request.md).

## Related types

For selling audience data as a third-party segment rather than enriching your own inventory, see [The Trade Desk](/connectors/destinations/the-trade-desk.md), which supports both first-party and third-party activation, under [DSP](/connectors/partner-types/dsp.md).


---

# 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/partner-types/ssp-and-ad-servers.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.