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

# mediarithmics Shared Segment

Share an audience with another mediarithmics datamart, between group entities or organisations.

The mediarithmics Shared Segment connector shares audiences between **datamarts** - for example between several entities of one group, or between different organisations.

<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/data-sharing-and-export.md">Data sharing &#x26; export</a></td></tr><tr><td><strong>Identifiers sent</strong></td><td>One identifier resource per feed, plus a separate matching identifier</td></tr><tr><td><strong>Authentication</strong></td><td>None - both datamarts are mediarithmics</td></tr></tbody></table>

## Description

### What this connector does

It sends the users of a segment to a **destination datamart**, creating or feeding a segment there. Two different identifiers are involved, and confusing them is the usual source of trouble:

<table data-search="false"><thead><tr><th width="260">Identifier</th><th></th></tr></thead><tbody><tr><td><strong>Identifier Matching type</strong></td><td>Used to <strong>match</strong> users between the origin and destination datamarts.</td></tr><tr><td><strong>Identifiers resources</strong></td><td>The identifier <strong>actually sent</strong> to the destination datamart.</td></tr></tbody></table>

### What happens on the destination datamart

* An identifier that **matches** an existing one is merged into the corresponding UserPoint.
* An identifier that **matches nothing** creates a new UserPoint carrying that identifier. The new UserPoint holds no activity.
* Several identifiers on the origin side that resolve to the **same** UserPoint on the destination count as **one** insertion.

{% hint style="warning" %}

* **There is no deletion on the destination datamart** when a user leaves the segment on the origin datamart.
* **Only one identifier can be sent at a time.** To send several, create several feeds.
  {% endhint %}

## Connector setup

### Prerequisites

* The **ID of the destination datamart**.
* Where the matching identifier is a UserAccount, the compartment IDs on **both** sides.

### Setup steps

{% stepper %}
{% step %}
**Select the mediarithmics Shared Segment connector and fill in its configuration.**

<table data-search="false"><thead><tr><th width="300">Field</th><th></th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>The name of the feed in the platform.</td></tr><tr><td><strong>Target Datamart id</strong></td><td>The ID of the destination datamart.</td></tr><tr><td><strong>Identifier Matching type</strong></td><td>The identifier used to match users between the two datamarts.</td></tr><tr><td><strong>Identifier Matching rule</strong></td><td>Which users to send - see below.</td></tr><tr><td><strong>Identifiers resources</strong></td><td>The identifier actually sent to the destination datamart.</td></tr><tr><td><strong>Segment Id</strong></td><td>The destination segment to feed. Leave empty and the feed creates a new segment there, then updates its own configuration with the new ID.</td></tr><tr><td><strong>Segment Name</strong></td><td>The segment's name in the destination datamart. Leave empty for the default, <code>SEGMENT_NAME-ORGANISATION_NAME/DATAMART_ID SHARED</code>.</td></tr><tr><td><strong>Source User Account Compartment ID</strong></td><td>Compartment ID on the source datamart. Required only when the matching identifier is a UserAccount; otherwise leave blank.</td></tr><tr><td><strong>Destination User Account Compartment ID</strong></td><td>Compartment ID on the destination datamart. Same condition.</td></tr></tbody></table>
{% endstep %}
{% endstepper %}

The **Identifier Matching rule** decides who is sent:

<table data-search="false"><thead><tr><th width="220">Rule</th><th></th></tr></thead><tbody><tr><td><strong>Matched users</strong></td><td>Only the selected identifier, for users matched on the destination datamart.</td></tr><tr><td><strong>Unmatched users</strong></td><td>Only the selected identifier, for users not matched on the destination datamart.</td></tr><tr><td><strong>All users</strong></td><td>Every user in the origin segment.</td></tr></tbody></table>

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*.

## FAQ

#### What happens when a user leaves the segment on the origin side?

Nothing on the destination. This connector does not delete.

#### Can I send several identifiers in one feed?

No. One identifier per feed - create one feed per identifier you want to share.

#### Do I have to create the destination segment first?

No. Leave **Segment Id** empty and the feed creates it, then records the new ID in its own configuration.

#### Why did my user count on the destination come out lower than the segment size?

Because several origin identifiers can resolve to the same destination UserPoint. Those count as one insertion.


---

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