> 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/integrations-and-data-exchange/imports-exports/exports/ui-exports/members.md).

# Members

**File format:** CSV

#### Sample CSV file

{% file src="/files/8VSidc6HrRUtC8GF3Pc1" %}

**Field reference**

The export contains 36 columns, listed below in the order they appear in the file. Every member in your program is exported as a single row, regardless of whether the member is active or anonymized.

<table><thead><tr><th width="234.12109375">Field</th><th>Description</th></tr></thead><tbody><tr><td><code>memberId</code></td><td>Unique Open Loyalty identifier (UUID) of the member</td></tr><tr><td><code>tenantId</code></td><td>Identifier (UUID) of the tenant the member belongs to</td></tr><tr><td><code>active</code></td><td><code>1</code> if the member account is active, empty if inactive</td></tr><tr><td><code>channelId</code></td><td>Identifier of the channel the member was registered in, if channels are used</td></tr><tr><td><code>firstName</code></td><td>First name</td></tr><tr><td><code>lastName</code></td><td>Last name</td></tr><tr><td><code>gender</code></td><td><code>male</code>, <code>female</code>, or <code>not_disclosed</code></td></tr><tr><td><code>email</code></td><td>Member's email address</td></tr><tr><td><code>phone</code></td><td>Phone number, including country code</td></tr><tr><td><code>birthDate</code></td><td>Date of birth, in ISO 8601 format with time and offset (for example <code>1994-10-25T00:00:00+01:00</code>)</td></tr><tr><td><code>lastLevelRecalculation</code></td><td>Timestamp of the last tier recalculation for this member (for the default tier set)</td></tr><tr><td><code>address</code></td><td>Address as a JSON object with the keys <code>street</code>, <code>address1</code>, <code>address2</code>, <code>province</code>, <code>city</code>, and <code>postal</code>. Exported as <code>[]</code> when no address is stored</td></tr><tr><td><code>loyaltyCardNumber</code></td><td>Loyalty card identifier</td></tr><tr><td><code>createdAt</code></td><td>Timestamp the member record was created in Open Loyalty</td></tr><tr><td><code>updatedAt</code></td><td>Timestamp of the most recent change to the member record</td></tr><tr><td><code>levelId</code></td><td>Identifier (UUID) of the tier the member currently belongs to (for the default tier set)</td></tr><tr><td><code>manuallyAssignedLevelId</code></td><td>Identifier (UUID) of the tier assigned manually by an admin (for the default tier set). Empty when the tier was granted automatically by the program rules</td></tr><tr><td><code>agreement1</code></td><td>Marketing consent flag — <code>1</code> if granted, empty if not</td></tr><tr><td><code>agreement2</code></td><td>Marketing consent flag — <code>1</code> if granted, empty if not</td></tr><tr><td><code>agreement3</code></td><td>Marketing consent flag — <code>1</code> if granted, empty if not</td></tr><tr><td><code>company</code></td><td>Company data as a JSON object (name and tax ID). Exported as <code>[]</code> when no company data is stored</td></tr><tr><td><code>transactionsCount</code></td><td>Total number of transactions registered for the member</td></tr><tr><td><code>transactionsAmount</code></td><td>Total value of the member's transactions</td></tr><tr><td><code>transactionsAmountWithoutDeliveryCosts</code></td><td>Total transaction value with delivery costs excluded</td></tr><tr><td><code>transactionsAmountExcludedForLevel</code></td><td>Portion of the transaction value excluded from tier calculation</td></tr><tr><td><code>averageTransactionAmount</code></td><td>Average value per transaction</td></tr><tr><td><code>lastTransactionDate</code></td><td>Date of the member's most recent transaction</td></tr><tr><td><code>firstTransactionDate</code></td><td>Date of the member's first transaction</td></tr><tr><td><code>levelAchievementDate</code></td><td>Date the member reached their current tier (for the default tier set)</td></tr><tr><td><code>referrerMemberId</code></td><td>Identifier (UUID) of the member who referred this member, if any</td></tr><tr><td><code>labels</code></td><td>Labels as a JSON array of key–value pairs, for example <code>[{"key":"served","value":"yes"}]</code>. Exported as an empty value when the member has no labels</td></tr><tr><td><code>anonymized</code></td><td><code>1</code> if the member has been anonymized, empty otherwise</td></tr><tr><td><code>referralToken</code></td><td>The member's unique referral code</td></tr><tr><td><code>currency</code></td><td>Currency used for the member's transaction values</td></tr><tr><td><code>storeCode</code></td><td>Code of the store the member is assigned to</td></tr><tr><td><code>registeredAt</code></td><td>Registration timestamp. Can differ from <code>createdAt</code> when the registration date was set explicitly during an import or via the API</td></tr></tbody></table>

{% hint style="info" %}
**Reading the values**

* All timestamps are exported in ISO 8601 format with a timezone offset, for example `2024-10-04T09:15:30+02:00`.
* Boolean fields (`active`, `agreement1/2/3`, `anonymized`) use `1` for true and an empty cell for false.
* `address`, `company`, and `labels` hold structured JSON inside a single CSV cell. If you open the file in a spreadsheet editor, keep the column as text so the JSON is not reformatted.
* Empty cells mean the field is not filled in for that member — they are not removed from the file.
  {% endhint %}

{% hint style="info" %}
If you plan to re-import this file elsewhere (e.g., via Member Segments), make sure you keep a consistent identifier column — email, phone, or loyalty card number — and don't mix identifier types within the same file.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.openloyalty.io/integrations-and-data-exchange/imports-exports/exports/ui-exports/members.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.