> 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/import-your-audience-from-your-information-system.md).

# Import your audience from an external source

Load a list of users decided elsewhere - a CRM extract, a partner file - into a segment.

## Your goal

Get an audience that was decided outside mediarithmics into the platform, so it can be activated, analysed, or used as a criterion in other segments.

## Expected outcome

A [List segment](/audience-and-activation/build-your-audiences/segment-reference/segment-types/list-import-segment.md) of type `File import`, populated from your file, with an import you can inspect line-count by line-count.

## When this is useful

When the audience is not defined by criteria the platform holds, but by a decision made in your own systems: a CRM selection, a loyalty tier, a churn list produced by your data team, an audience a partner sent you.

## Prerequisites

* The list itself, as a CSV file (ndjson also works). Each line is a command for one user: add (`UPDATE`) or remove (`DELETE`), how long they stay (`expiration_duration`, in minutes, `0` for no expiry), the segment, and one identifier. See [The segment command](https://app.gitbook.com/s/XSPACE_SETUP/collect-and-manage-your-data/import-data-in-batch/import-segments#the-segment-command), and for imports and executions, [Import data in batch](https://app.gitbook.com/s/XSPACE_SETUP/collect-and-manage-your-data/import-data-in-batch).
* One identifier per line: an account ID with its compartment ID, an email hash, or a user agent ID. Lines may mix identifier types.
* Access to the **Computing console** app.

## Steps

{% stepper %}
{% step %}

### Create the segment

In the side menu, go to **Audience > Segments** and click **New Segment**. Choose the **User List** type, fill in at least the name, and click **Save**. You are redirected to the segment page.

{% hint style="info" %}
Set the **default lifetime** here if the audience should expire. It applies to every user entering the segment - unless the upload provides `expiration_ts` for a user, which always wins. See [Segment properties](/audience-and-activation/build-your-audiences/segment-reference.md#segment-properties).
{% endhint %}
{% endstep %}

{% step %}

### Create the import

Go to the **Computing console** app, **Jobs > Import**, and click **New Import**.
{% endstep %}

{% step %}

### Configure it

Fill in:

* **Import name.** The name for your import.
* **Document type.** Choose **User Segment**.
* **Priority.** `LOW`, `MEDIUM`, or `HIGH`.

Save when done.
{% endstep %}

{% step %}

### Create an execution and upload the file

Create a new execution, then drag and drop your CSV. Ingestion can be followed from the same screen.

For best performance, keep each file to 100 MB at most, and split larger lists.
{% endstep %}

{% step %}

### Check the result on the segment

Open the segment and look at the **Import status** tab - it is only present on List segments. It shows the submission date, the status, the number of users treated, and the number actually imported.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
To bind a CSV to the segment without configuring an import, use the **Data loader** in the Computing Console: UTF-8, headers mandatory, 20 MB at most. Pick the identifier column and type, an optional hashing method, and the target segment. A user not found is created. See [Load segments](https://app.gitbook.com/s/XSPACE_SETUP/collect-and-manage-your-data/import-data-in-batch/data-loader/load-segments).
{% endhint %}

## Verification

The import is `SUCCEEDED`, and **User Segments imported** is close to **User Segments Treated**.

{% hint style="warning" %}
A large gap between treated and imported is the signal worth acting on: the platform read those lines but could not attach them to a user. That is an identifier problem - the identifier type, its formatting, or its hashing - not an import failure. Identity resolution is documented in **Setup & Monitor**, under `Resolve identities`.
{% endhint %}

## Consent on an imported audience

For a List segment, user choices are checked **before a user is added to the segment**, rather than woven into a query. If the audience will be activated, attach the processing activities first. See [Enforce compliance on your audience](/audience-and-activation/build-your-audiences/enforce-compliance-on-your-audience.md).

## 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>File import segment</strong></td><td>The type's properties, and the import status columns in full.</td><td><a href="/audience-and-activation/build-your-audiences/segment-reference/segment-types/list-import-segment.md">File import segment</a></td></tr><tr><td><strong>Import segments</strong></td><td>The segment command, field by field, and the import API.</td><td><a href="https://app.gitbook.com/s/XSPACE_SETUP/collect-and-manage-your-data/import-data-in-batch/import-segments">https://app.gitbook.com/s/XSPACE_SETUP/collect-and-manage-your-data/import-data-in-batch/import-segments</a></td></tr><tr><td><strong>Load segments</strong></td><td>Binding a CSV to a segment with the Data loader.</td><td><a href="https://app.gitbook.com/s/XSPACE_SETUP/collect-and-manage-your-data/import-data-in-batch/data-loader/load-segments">https://app.gitbook.com/s/XSPACE_SETUP/collect-and-manage-your-data/import-data-in-batch/data-loader/load-segments</a></td></tr><tr><td><strong>Send your first-party data to a destination</strong></td><td>Activating the imported audience.</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></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/import-your-audience-from-your-information-system.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.