> 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/setup-and-monitor/collect-and-manage-your-data/import-data-in-batch/data-loader/load-segments.md).

# Load segments

Bind the users in a CSV file to an existing segment.

## Your goal

Put the users listed in a CSV file into a segment you have already created - a list of hashed emails, account IDs, or device identifiers.

## Expected outcome

The users the file identifies are bound to the target segment, with the lifetime you chose.

## Prerequisites

* **At least one segment of type `USER_LIST`** to bind the identifiers to. Without one, the segment document type is unavailable.
* A CSV file meeting the [file requirements](/setup-and-monitor/collect-and-manage-your-data/import-data-in-batch/data-loader.md#file-requirements).
* The compartment or registry the identifier belongs to.

## Configure the import

{% tabs %}
{% tab title="Identifier" %}

* Select the **CSV property** to use as the identifier.
* Choose the **identifier type**: `USER_ACCOUNT`, `USER_EMAIL`, or `USER_DEVICE_TECHNICAL_ID` - and specify the related **compartment** for an account, or **registry** for a device technical ID.
* Optionally select a **hashing** method to apply to the input. Only one hashing method per field is allowed.

{% hint style="info" %}
If a user is not found for a row, **a new user is created**. On a segment load this is worth thinking about: a list of identifiers you do not otherwise collect will mint UserPoints that contain nothing but a segment membership.
{% endhint %}
{% endtab %}

{% tab title="Segment" %}

* Select the **target segment** the mapped identifiers are bound to.
* Optionally update the **lifetime** value. It defaults to the lifetime configured on the target segment.
  {% endtab %}
  {% endtabs %}

## Example file

A single column is enough:

```csv
Email_sha256
ce5bfa8406dd062b059a4b841bf36de186977fe515dc5a704a58e973cab1a5d5
9980f7e8331dce3bfa2e3b3ab6b69dcb960658bcb400801cece7873afeb5a905
2a33ce360e63c2a9f2e921bc7455a1f7dad42f0fdf654a7def5f3c8a1d934954
```

## How reuse works here

For segments, the document import is named after the **segment**, not the file: `Data Loader - segment-user-list - <SEGMENT_ID>`. Every load into the same segment therefore appears as a new execution of the same import - which makes the execution history of a segment easy to read.

## Verify

* The transformation report shows no errors before upload.
* The execution succeeds with the expected success count.
* The segment's user count increases by roughly the number of rows - allowing for users already in it.
* Members leave the segment when the lifetime expires.

## 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>Data loader</strong></td><td>The upload flow and file requirements.</td><td><a href="/setup-and-monitor/collect-and-manage-your-data/import-data-in-batch/data-loader.md">Data loader</a></td></tr><tr><td><strong>Import segments</strong></td><td>The same import through the API, with expiration options.</td><td><a href="/setup-and-monitor/collect-and-manage-your-data/import-data-in-batch/import-segments.md">Import segments</a></td></tr><tr><td><strong>Load profiles</strong></td><td>Loading properties rather than membership.</td><td><a href="/setup-and-monitor/collect-and-manage-your-data/import-data-in-batch/data-loader/load-profiles.md">Load profiles</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/setup-and-monitor/collect-and-manage-your-data/import-data-in-batch/data-loader/load-segments.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.