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

# Shared

Synchronise an audience to the mediarithmics member on Xandr and share it to your destination member.

The Xandr Shared connector synchronises an audience to the **mediarithmics member** on Xandr, then shares it to your destination member. It needs no setup, and it trades functionality for that.

<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>None - only your Xandr member ID is needed</td></tr></tbody></table>

## Description

### What you can do with this connector

* Push an audience to Xandr without any onboarding on the Xandr side.
* Share a specific segment with a third party by creating a **separate feed instance** carrying that third party's Xandr `member_id`.

{% hint style="warning" %}
**Limited functionality.** Segments created through this connector **cannot be shared with third parties** from your own account, and **no CPM information** is available. If you need either, use [Xandr - Direct](/connectors/destinations/xandr/direct.md).
{% endhint %}

### 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

* Your **`member_id`** - your Xandr client ID. That is all this feed type requires.

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

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

Xandr's ingestion SLA, active-user definition and invalid-user behaviour apply here too - see [Good to know on Xandr - Direct](/connectors/destinations/xandr/direct.md#good-to-know).

{% 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

#### How do I share a segment with a third party through this connector?

Create a **specific feed instance** using the third party's Xandr `member_id`. You cannot share an existing shared segment onward from your own account.

#### Why can I not see CPM information?

Shared feeds do not carry it. Use [Xandr - Direct](/connectors/destinations/xandr/direct.md) if you need CPM.

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