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

# Index Exchange

Distribute first-party audience segments to Index Exchange for deal creation and audience targeting.

The Index Exchange connector distributes your first-party audience segments to Index Exchange. Once synchronised, they become available to publishers and Marketplace Partners for deal creation and audience targeting.

<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/ssp-and-ad-servers.md">SSP &#x26; ad servers</a></td></tr><tr><td><strong>Identifiers sent</strong></td><td>Mobile advertising IDs (MAID), Universal IDs (UTIQ MartechPass mobile, ID5 decrypted), IP addresses</td></tr><tr><td><strong>Authentication</strong></td><td>SFTP with SSH key credentials, on an account provisioned by Index Exchange</td></tr></tbody></table>

{% hint style="info" %}
Setting up this connection involves work on the mediarithmics side. Contact your account manager to get the SFTP connection to Index Exchange opened.
{% endhint %}

## Description

### What is Index Exchange?

Index Exchange is a global advertising marketplace that lets media owners and buyers transact programmatically with transparency and efficiency.

Through its Audience capabilities, Index Exchange allows data providers and partners to:

* Share audience segments for activation in private marketplaces and deals.
* Let publishers and buyers target specific audiences across inventory.
* Use external data to enhance campaign performance.
* Operate within a privacy-conscious and scalable programmatic ecosystem.

### What you can do with this connector

* Make a mediarithmics segment available for deal creation inside the Index Exchange ecosystem.
* Let publishers and Marketplace Partners target that audience across their inventory.

### Which identifiers are sent

* **Mobile advertising IDs** (MAID)
* **Universal IDs**
  * UTIQ MartechPass mobile
  * ID5, decrypted
* **IP addresses**

## Connector setup

### Prerequisites

* An **Index Exchange account**.
* An **advertiser account ID** and an **owner account ID**, both provided by Index Exchange.
* Access to an **SFTP account** provisioned by Index Exchange.
* Access to the mediarithmics platform, with permission to create and manage feeds.

### Authentication

Authentication runs over SFTP, using SSH key credentials. Index Exchange provisions the SFTP account and issues the credentials; they are configured on the mediarithmics side when the connection is opened.

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

* **Allow a short delay before data flows.** After the segment is created, roughly ten minutes are needed for the taxonomy file to be fully ingested before user data is sent.

## FAQ

#### Do I need a specific Index Exchange account?

Yes. You need an Index Exchange account, with an advertiser account ID and an owner account ID provided by Index Exchange.

#### How is authentication handled?

Over SFTP, with SSH key credentials. They are configured when the connection is set up.

#### Is there a delay before data starts flowing?

Yes. Expect around ten minutes after the segment is created, so the taxonomy file is fully ingested before user data is sent.

## Partner documentation

Index Exchange documents its own platform at [https://kb.indexexchange.com/](https://kb.indexexchange.com/Home.htm). Use it for anything that happens on the partner side of this connector: account setup, the fields the partner expects, and its own limits.

## 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>SSP &#x26; ad servers</strong></td><td>What an SSP needs from your CDP, and every mediarithmics connector that reaches one.</td><td><a href="/connectors/partner-types/ssp-and-ad-servers.md">SSP &amp; ad servers</a></td></tr><tr><td><strong>Getting started</strong></td><td>Every documented connector, by partner type and by name.</td><td><a href="/connectors/readme.md">Getting started</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/destinations/index-exchange.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.