> 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-types/list-import-segment.md).

# File import segment

The segment type filled from outside the platform, by file import.

## What it is

A **List segment** holds an explicit list of users rather than a query. When that list comes from outside the platform - a CRM extract, a partner file - the segment appears in the segments list with the type `File import`.

This is the type to use when the audience is decided elsewhere and mediarithmics only has to hold it.

## What is specific to this type

* **It is always persisted.** Membership is stored by definition; there is nothing to compute.
* **Default lifetime applies.** Set it on the segment and each user leaves the segment that long after entering it. A per-user `expiration_ts` provided in the upload takes precedence over the segment's default lifetime.
* **Consent is checked on entry.** For a List segment, user choices are verified *before* a user is added, rather than folded into a query. See [Enforce compliance on your audience](/audience-and-activation/build-your-audiences/enforce-compliance-on-your-audience.md).

See [Segment properties](/audience-and-activation/build-your-audiences/segment-reference.md#segment-properties) for the full field list.

## Following an import

A List segment carries an **Import status** tab, which is not shown on any other type. It lists every import made into the segment:

| Column                     | What it tells you                                   |
| -------------------------- | --------------------------------------------------- |
| **Submission date**        | When the import was submitted.                      |
| **Status**                 | Whether the import succeeded (`SUCCEEDED`).         |
| **User Segments Treated**  | How many users were processed in the original file. |
| **User Segments imported** | How many users were actually imported.              |

{% hint style="info" %}
The gap between *treated* and *imported* is the useful number: it is the part of your file the platform could not attach to a user. A consistent gap usually points at the identifier you are matching on rather than at the import itself.
{% 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>Import your audience from an external source</strong></td><td>Create the segment, then load the file.</td><td><a href="/audience-and-activation/build-your-audiences/import-your-audience-from-your-information-system.md">Import your audience from an external source</a></td></tr><tr><td><strong>Automation segment</strong></td><td>The same list type, filled by a scenario instead of a file.</td><td><a href="/audience-and-activation/build-your-audiences/segment-reference/segment-types/list-automation-segment.md">Automation segment</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-types/list-import-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.