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

# Direct

Synchronise an audience directly to your own Xandr member, with the segment as your account's property.

The Xandr Direct connector synchronises an audience **directly to a Xandr member**, so you can run media campaigns - display, video and the rest - on the Xandr DSP.

<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>Cookies, Mobile IDs, TV IDs, First ID, UTIQ MartechPass</td></tr><tr><td><strong>Authentication</strong></td><td>Xandr API access, credentials shared with your account manager</td></tr></tbody></table>

## Description

### What you can do with this connector

* Push an audience to your own Xandr member and run campaigns against it.
* **Share the resulting segment with third parties** - the segment is your account's property, which is the main thing Direct gives you over Shared.

### Which identifiers are sent

* **Cookies**
* **Mobile IDs**
* **TV IDs**
* **First ID**
* **UTIQ MartechPass**

{% hint style="warning" %}
**First ID** and **UTIQ MartechPass** need a specific configuration following the [Xandr API](https://learn.microsoft.com/en-us/xandr/digital-platform-api/bss-avro-file-format#extended-idseid-or-publisher-provided-idsppid). Contact your Xandr account manager to authorise the sources **`first-id.fr`** or **`utiq-mtp.com`** on your seat, if they are not authorised already.
{% endhint %}

Xandr is reached by several connectors and they behave differently - [the comparison is on the Xandr page](/connectors/destinations/xandr.md).

## Connector setup

### Prerequisites

No whitelisting is needed on the mediarithmics side, but you need **Bidder Access to Xandr**, and your Xandr team has to set up the authentication.

**Get API access from Xandr.** To be granted it you must:

* be a current Xandr UI customer with a **current user ID and member ID** - support cannot create a new user to fulfil an API access request;
* be a **Network, Network Observer, Advertiser or Publisher** user. API access cannot be granted to Network Advertiser Manager or Network Publisher Manager users. See Xandr's [User Service](https://docs.xandr.com/bundle/xandr-api/page/user-service.html) for the user types.

Open a support ticket titled **"Request for API Access"**, and include:

* the numeric ID of the **user** that requires API access;
* the billing name and numeric ID of the **member** that user sits under.

Xandr's support team cannot grant access to clients who are not platform UI or Invest users. If that is your case, contact the Platform Integrations team for your business unit. Xandr documents the whole flow in its [API onboarding process](https://docs.xandr.com/bundle/xandr-api/page/api-onboarding-process.html).

{% hint style="warning" %}
Cookie matching must be activated on your organisation. Contact your mediarithmics account manager to confirm.
{% endhint %}

### Authentication

Once API access is granted, give your account manager:

* **`member_login`** - the credential of a Xandr user;
* **`password`** - that user's password;
* **`member_id`** - your Xandr client ID.

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

These behaviours are Xandr's, and they apply to the [Shared](/connectors/destinations/xandr/shared.md) connector too.

### Ingestion and matching

* **Ingestion delay SLA on the Xandr side: 24 hours.**
* **Active users** are all users Xandr has seen in the past 24 hours where Xandr is used as SSP.

### Invalid users

Xandr documents the causes in [Troubleshooting invalid users](https://docs.xandr.com/bundle/xandr-bidders/page/troubleshooting-invalid-users.html):

* a typo in the UID makes the user invalid;
* Xandr expires UIDs on a rolling basis, removing the users unseen for longest from its database;
* Xandr does not store the user ID server-side until it sees the user a **second** time.

{% hint style="warning" %}
Following CNIL guidance on cookies and trackers, make sure that:

1. the partner is correctly named when you collect user consent for targeting purposes, or the equivalent;
2. the partner is named in your cookie policy - these partners may drop a cookie on your users' browsers from your websites.
   {% endhint %}

## FAQ

#### Why is my match lower than the segment size?

Several Xandr behaviours reduce it: UIDs expire on a rolling basis, and Xandr only stores a user ID server-side after seeing the user a second time. Add the 24-hour ingestion SLA before comparing counts.

#### Xandr refused my API access request.

Check the user type. API access cannot be granted to Network Advertiser Manager or Network Publisher Manager users, nor to clients who are not platform UI or Invest users.

#### Can I share the segment with a third party?

Yes - that is what Direct gives you. Segments created through [Shared](/connectors/destinations/xandr/shared.md) cannot be shared onward.

## Partner documentation

Xandr documents its own platform at <https://learn.microsoft.com/en-us/xandr/>. 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/xandr/direct.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.