> 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/data-sharing-and-export.md).

# Data sharing & export

Delivering an audience as a file, a browser signal, or a segment in another mediarithmics datamart.

Not every destination is a platform with an API. Sometimes the right answer is a **file on a bucket**, a **signal in the browser** any partner can read, or a **segment handed to another mediarithmics datamart**.

This is the type you reach for when the partner has no dedicated connector, when several partners need the same audience, or when the recipient is another entity in your own group.

## Connectors

<table data-search="false"><thead><tr><th width="300">Connector</th><th></th></tr></thead><tbody><tr><td><a href="/connectors/destinations/identifiers-exporter.md">Identifiers Exporter</a></td><td>Incremental file export - <strong>upserts and deletes</strong> - to Amazon S3, a GCP bucket or SFTP. Cookies, mobile IDs, emails, profile data.</td></tr><tr><td><a href="/connectors/destinations/segment-exporter.md">Segment Exporter</a></td><td><strong>Full-list</strong> file export, SFTP only. Same identifier range.</td></tr><tr><td><a href="/connectors/destinations/curated-audiences-sda.md">Curated Audiences (SDA)</a></td><td>Writes standardised taxonomy segment IDs to the browser, under <code>mics_sda</code>, for any bidding partner on your page to read. <strong>No personal identifier is shared.</strong></td></tr><tr><td><a href="/connectors/destinations/mediarithmics-shared-segment.md">mediarithmics Shared Segment</a></td><td>Shares an audience with <strong>another mediarithmics datamart</strong> - between group entities, or between organisations.</td></tr></tbody></table>

## Choosing between them

<table data-search="false"><thead><tr><th width="290">If you need to…</th><th></th></tr></thead><tbody><tr><td>Deliver changes as they happen, including exits</td><td><a href="/connectors/destinations/identifiers-exporter.md">Identifiers Exporter</a> - it is the only file route that carries deletes.</td></tr><tr><td>Deliver a complete list on a schedule</td><td><a href="/connectors/destinations/segment-exporter.md">Segment Exporter</a>.</td></tr><tr><td>Serve several bidding partners at once, without sharing identifiers</td><td><a href="/connectors/destinations/curated-audiences-sda.md">Curated Audiences (SDA)</a>.</td></tr><tr><td>Reach another mediarithmics instance</td><td><a href="/connectors/destinations/mediarithmics-shared-segment.md">mediarithmics Shared Segment</a>.</td></tr></tbody></table>

## What to watch

* **Identifiers Exporter takes exactly one identifying resource and one compartment per feed.** Select more than one of either and the feed sends nothing at all. Create one feed per identifier.
* **Shared Segment does not delete.** A user leaving the segment on the origin datamart is not removed on the destination, and only one identifier can be sent per feed.
* **File delivery follows segment calculation.** Uploads scheduled more often than the segment is computed produce empty files.

## Related types

Several partners with no connector of their own are served through the Identifiers Exporter - Hawk and RTB House among them. See [Connectors on request](/connectors/connectors-on-request.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/data-sharing-and-export.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.