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

# Identifiers Exporter

Export segment identifiers as incremental files to S3, GCP or SFTP, with upserts and deletes.

The Identifiers Exporter connector exports segment identifiers to a partner by sending **updates or deletes** as files, to an Amazon S3 bucket, a GCP bucket or an SFTP server.

<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>Cookies, Mobile IDs, Email identifiers, Profile data</td></tr><tr><td><strong>Authentication</strong></td><td>Destination configured by your mediarithmics account manager</td></tr></tbody></table>

## Description

### What this connector does

It writes files carrying the identifiers of the users in a segment to a destination you own, and keeps writing them as the segment changes. Compare it with [Segment Exporter](/connectors/destinations/segment-exporter.md), which pushes only **full** segment files, and only to SFTP.

### What you can do with this connector

* Deliver an audience to a partner that has no dedicated connector.
* Send incremental changes rather than a full list each time, including exits.
* Choose the file path, name, header, size and upload frequency.

### Which identifiers are sent

* **Cookies**
* **Mobile IDs**
* **Email identifiers**
* **Profile data**

{% hint style="warning" %}
**One identifying resource and one compartment ID per feed.** If you select more than one of either, the feed sends no identifiers at all. To export several identifiers, create several feeds.
{% endhint %}

The identifying resources available:

<table data-search="false"><thead><tr><th width="300">Resource</th><th></th></tr></thead><tbody><tr><td><code>USER_ACCOUNT</code></td><td>One compartment allowed.</td></tr><tr><td><code>USER_EMAIL</code></td><td></td></tr><tr><td><code>USER_PROFILE</code></td><td>One compartment allowed. Requires a custom field selection.</td></tr><tr><td><code>USER_DEVICE_TECHNICAL_ID</code></td><td>One registry allowed. Covers <code>MUM_ID</code>, <code>NETWORK_DEVICE_ID</code>, <code>CUSTOM_DEVICE_ID</code>, <code>MOBILE_ADVERTISING_ID</code> and <code>TV_ADVERTISING_ID</code>.</td></tr></tbody></table>

## Connector setup

### Prerequisites

Give your mediarithmics account manager the delivery specification:

* The **targeted file path**. It must start and end with a `/`.
* The **expected file name**, for example `Segmentname_extractiondate(YYMMDDHHmmss)`.
* The **expected header**.
* The **expected maximum file size**, if relevant.
* Whether the file needs to be **compressed**.
* The **minimum and maximum uploads per day** - for example, a file every two hours.

### Authentication

The destination - cloud hosting provider or SFTP - is set up by the mediarithmics project team, who return a **File destination token**. That token is what the feed references; credentials are never entered on the feed.

### Setup steps

{% stepper %}
{% step %}
**Send the delivery specification to your account manager.**

They set up the destination and return the file destination token.
{% endstep %}

{% step %}
**Select the Identifiers Exporter 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>A name you choose.</td></tr><tr><td><strong>File destination token</strong></td><td>The technical name provided by the mediarithmics project team. Points at the destination cloud provider or SFTP.</td></tr><tr><td><strong>Share both Upsert and Delete</strong></td><td>Off, only upserts are sent and there is no operation column. On, an <code>UPSERT</code> / <code>DELETE</code> column is added.</td></tr><tr><td><strong>Add Segment Name column</strong></td><td>Writes the segment name, or the formatted segment name, into the file.</td></tr><tr><td><strong>Add Segment Id column</strong></td><td>Writes the segment ID into the file.</td></tr><tr><td><strong>Add Operation timestamp column</strong></td><td>Writes the operation timestamp, in milliseconds.</td></tr><tr><td><strong>Formatted Segment Name</strong></td><td>The segment name used in the file, and in the file name through macros.</td></tr></tbody></table>
{% endstep %}

{% step %}
**Fill in the resource-specific fields.**

* **Third-party cookie selection** - **mandatory when `MUM_ID` is the identifying resource.** Choose the mediarithmics option to send `vector_ids` / `mum_ids`, or another option to send partner cookies coming from cookie sync with mediarithmics.
* **User Profile custom field selection** - **mandatory when `USER_PROFILE` is the identifying resource.** Give the path to the identifier on the UserProfile, for example `crm_data.hash_email`. A String or Number field is written as is; an Object or Array field is written as stringified JSON.
  {% endstep %}
  {% endstepper %}

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

{% hint style="info" %}
**Sending frequency follows segment calculation.** If uploads are scheduled more often than the segment is computed, some files will be empty.
{% endhint %}

## FAQ

#### What does the exported timestamp represent?

The moment the user **entered** the segment for an `UPSERT`, and the moment they were **removed** from it for a `DELETE`.

#### Why is my feed sending nothing?

Check that exactly one identifying resource and one compartment ID are selected. More than one of either, and the feed sends no identifiers.

#### Should I use Identifiers Exporter or Segment Exporter?

Identifiers Exporter sends incremental upserts and deletes, to S3, GCP or SFTP. [Segment Exporter](/connectors/destinations/segment-exporter.md) sends the full segment list, to SFTP only.

## 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>Segment Exporter</strong></td><td>Full-list export over SFTP.</td><td><a href="/connectors/destinations/segment-exporter.md">Segment Exporter</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/identifiers-exporter.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.