> 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/audience-and-activation/build-your-audiences/segment-reference/segment-capabilities/export-segment-identifiers.md).

# Export segment identifiers

Export the identifiers attached to a segment as a CSV, with or without technical prefixes.

## What it does

An export takes the identifiers attached to the users of a segment and produces a downloadable CSV. It is the manual counterpart to a [feed](/audience-and-activation/activate-your-audiences/set-up-a-destination/feed.md): same identifiers, no partner, no schedule.

Query exports and destination files are a different mechanism, documented in the **Setup & Monitor** section, under *Export your data*.

## Exporting

{% stepper %}
{% step %}

### Start the export

On the segment page, select the **Export** tab and click **New Export**.
{% endstep %}

{% step %}

### Choose the identifier types

You can export several types at once. Available types:

* Device ID
* User accounts
* Email hash
  {% endstep %}

{% step %}

### Decide on technical prefixes

Optionally, include the technical prefix in the exported values.

{% hint style="info" %}
With prefixes on, the value `123456789` is exported as `mum:123456789`. Turn them on when the consuming system needs to know which namespace an identifier belongs to; leave them off when it expects a bare value.
{% endhint %}
{% endstep %}

{% step %}

### Submit and wait

The export's status progresses from `PENDING`, to `RUNNING`, and finally to either `SUCCEEDED` or `FAILED`.
{% endstep %}

{% step %}

### Collect the result

Download the CSV, or read the figures on screen.
{% endstep %}
{% endstepper %}

## Reading the result

| Field                                     | What it tells you                                                        |
| ----------------------------------------- | ------------------------------------------------------------------------ |
| **Submission date**                       | When the export was requested.                                           |
| **Status**                                | Whether the export succeeded (`SUCCEEDED`).                              |
| **Progress**                              | How far it has got.                                                      |
| **Start date**                            | When the export was requested.                                           |
| **End date**                              | When the export finished.                                                |
| **User Identifier type**                  | Which identifier types were exported.                                    |
| **UserPoint in segment**                  | How many users the segment holds.                                        |
| **Exported UserPoint (with identifiers)** | How many of them carried at least one identifier of the requested types. |
| **Exported identifiers**                  | How many identifier values came out.                                     |

{% hint style="info" %}
The three last rows are the same reasoning as [identifier coverage](/audience-and-activation/activate-your-audiences/track-a-feed-stats-and-troubleshoot.md#the-three-numbers-that-matter) on a feed: a large segment producing few exported users means the identifier you asked for is thin on the ground, not that the export failed.
{% endhint %}

## 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>Send your first-party data to a destination</strong></td><td>The automated route to a partner platform.</td><td><a href="/audience-and-activation/activate-your-audiences/send-your-audience-to-a-destination/send-your-first-party-data-to-a-destination.md">Send your first-party data to a destination</a></td></tr><tr><td><strong>Segment capabilities</strong></td><td>The other actions available on a segment.</td><td><a href="/audience-and-activation/build-your-audiences/segment-reference/segment-capabilities.md">Segment capabilities</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/audience-and-activation/build-your-audiences/segment-reference/segment-capabilities/export-segment-identifiers.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.