> For the complete documentation index, see [llms.txt](https://help.openloyalty.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.openloyalty.io/technical-guide/data-exports/data-structure-and-types/members-segments.md).

# Members Segments

The current segment membership of every member, exported daily as a full snapshot.

The Members Segments file lists every member who belongs to at least one segment, together with the IDs of all their segments.

{% hint style="warning" %}
**Snapshot export.** This is **not** a delta file. Each file contains the **complete** segment membership at the time the file was produced, not the changes made that day. Replace the previous day's data with the new file; do not merge files together. A member who is no longer in any segment is **not** included, so they only disappear from the file; no row marks the removal.
{% endhint %}

**File:** `analytics/Segments/members_segments_YYYY_MM_DD.csv`\
**Primary key:** `memberId` + `storeId`

The date in the file name is the day before the file was produced. The content reflects segment membership at the time the file was produced, shortly after midnight, not at a precise cut-off.

**Available data** (in column order):

<table><thead><tr><th width="135.27734375">Column</th><th width="131.31640625">Type</th><th width="114.8984375">Empty value</th><th>Description</th></tr></thead><tbody><tr><td><code>memberId</code></td><td><code>uuid</code></td><td>No</td><td>ID of the member</td></tr><tr><td><code>storeId</code></td><td><code>uuid</code></td><td>No</td><td>ID of the tenant</td></tr><tr><td><code>segmentIds</code></td><td><code>json array</code></td><td>No</td><td>IDs of the segments the member belongs to</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://help.openloyalty.io/technical-guide/data-exports/data-structure-and-types/members-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.