> 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.md).

# Data Structure and Types

Learn more how data is organized in AWS S3 Bucket

### Key Points

* **Export frequency:** Data is exported once per day to provide consistent and timely access.
* **Delta exports:** Each export contains only the changes (delta) from the previous calendar day.
* **Single report per environment:** One report set is generated **per environment**, regardless of the number of tenants. Each report includes a unique identifier (`tenantId`), which you can use to build pipelines and split the data by tenant if needed.
* **File naming convention:**
  * **Daily reports:** `filename_YYYY_MM_DD.csv` - where `YYYY_MM_DD` is the date the report covers.
  * **One-off reports (on request):** `filename_all_until_YYYY_MM_DD.csv` - using the same naming format as daily reports.
* **Data mapping by IDs:** Each file uses identifiers to link data across reports. For example, the **members file** contains full details for each `memberId`, while other reports reference only the `memberId` (without personal details).

***

### Column types

The tables in this section use the following CSV value types.

<table><thead><tr><th width="132.16796875">Type</th><th>Format</th></tr></thead><tbody><tr><td><code>uuid</code></td><td>A UUID identifier, for example <code>9a3c6f2e-…</code></td></tr><tr><td><code>string</code></td><td>Text value</td></tr><tr><td><code>integer</code></td><td>Whole number</td></tr><tr><td><code>decimal</code></td><td>Decimal number without a thousands separator</td></tr><tr><td><code>datetime</code></td><td>ISO 8601 timestamp with a UTC offset, unless noted otherwise</td></tr><tr><td><code>boolean</code></td><td><code>1</code> for true; an empty cell for false</td></tr><tr><td><code>enum</code></td><td>One value from the values documented for that column</td></tr><tr><td><code>json object</code></td><td>A JSON object in one CSV cell</td></tr><tr><td><code>json array</code></td><td>A JSON array in one CSV cell</td></tr></tbody></table>

An empty cell means no value, unless the column notes a different meaning.

***

### Overall Structure

* **analytics/**\
  This is the main folder within the bucket. All data related to analytics is organised under this folder.

<figure><img src="https://123136216-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgIv2CyIIYf7vRfuhMKQ6%2Fuploads%2Fgit-blob-0e4f890b68073a59ff47990574da886359c0a1bc%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

### Subfolders under `analytics/`

1. **Achievements/**\
   Contains CSV data files related to achievements. These might include records of user milestones or progress indicators, as well as the overall configuration of the achievements.\
   \
   You can find out more about the file structure stored in this folder in these articles:\
   [Achievements](/technical-guide/data-exports/data-structure-and-types/achievements.md)\
   [Achievement Usage](/technical-guide/data-exports/data-structure-and-types/achievement-usage.md)<br>
2. **Campaigns/**\
   Contains CSV data files related to campaigns, such as configuration files or performance metrics.\
   \
   You can find out more about the file structure stored in this folder in these articles:\
   [Campaigns](/technical-guide/data-exports/data-structure-and-types/campaigns.md)\
   [Campaign Execution](/technical-guide/data-exports/data-structure-and-types/campaign-execution.md)\
   [Campaign Calculated Effect Results](/technical-guide/data-exports/data-structure-and-types/campaign-calculated-effect-results.md)<br>
3. **Challenges/**\
   Contains member progress for each challenge.\
   \
   You can find out more about the file structure stored in this folder in this article:\
   [Challenge Member Progress](/technical-guide/data-exports/data-structure-and-types/challenge-member-progress.md)<br>
4. **CampaignsVisibility/**\
   Contains CSV data files related to campaigns, such as configuration files or performance metrics.\
   \
   You can find out more about the file structure stored in this folder in these articles:\
   [Campaign Visibility](/technical-guide/data-exports/data-structure-and-types/campaign-visibility.md)<br>
5. **CustomEvent/**\
   Contains CSV data files related to all the custom events registered in the system.\
   \
   You can find out more about the file structure stored in this folder in this article:\
   [Custom Events](/technical-guide/data-exports/data-structure-and-types/custom-events.md)<br>
6. **Members/**\
   Contains CSV data files related to all the members registered in the system, and the updates on their profiles.\
   \
   You can find out more about the file structure stored in this folder in this article:\
   [Members](/technical-guide/data-exports/data-structure-and-types/members.md)<br>
7. **MembersSegments/**\
   Contains CSV data files for members and their segment memberships.\
   \
   You can find out more about the file structure stored in this folder in this article:\
   [Members Segments](/technical-guide/data-exports/data-structure-and-types/members-segments.md)<br>
8. **MemberTierChanges/**\
   Contains CSV data files related to the tier changes (downgrades and upgrades) of members registered in the system at the end of each day.\
   \
   You can find out more about the file structure stored in this folder in this article:\
   [Member Tier Changes](/technical-guide/data-exports/data-structure-and-types/member-tier-changes.md)<br>
9. **Points/**\
   Contains CSV data files related to units accumulated by users, as well as used and expired transfers.\
   \
   You can find out more about the file structure stored in this folder in this article:\
   [Unit Transfers](/technical-guide/data-exports/data-structure-and-types/unit-transfers.md)<br>
10. **Reconciliation/**\
    Shows how exported files connect and how to reconcile balances and counts.\
    \
    You can find out more about reconciliation in this article:\
    [Reconciliation](/technical-guide/data-exports/reconciliation.md)<br>
11. **Rewards/**\
    Contains CSV data files related to available rewards and redemption histories.\
    \
    You can find out more about the file structure stored in this folder in these articles:\
    [Rewards](/technical-guide/data-exports/data-structure-and-types/rewards.md)\
    [Rewards Redemption](/technical-guide/data-exports/data-structure-and-types/rewards-redemption.md)<br>
12. **Segments/**\
    Contains CSV data files related to segment definitions and statistics.\
    \
    You can find out more about the file structure stored in this folder in this article:\
    [Segments](/technical-guide/data-exports/data-structure-and-types/segments.md)<br>
13. **Tenant/**\
    Contains CSV data files related to all the tenants (storeCodes) created in the system.\
    \
    You can find out more about the file structure stored in this folder in this article:\
    [Tenants](/technical-guide/data-exports/data-structure-and-types/tenants.md)<br>
14. **Tiers/**\
    Contains CSV data files related to different tier levels (e.g., Bronze, Silver, Gold) and the rules or requirements for each tier.\
    \
    You can find out more about the file structure stored in this folder in this article:\
    [Tiers](/technical-guide/data-exports/data-structure-and-types/tiers.md)<br>
15. **Transactions/**\
    Contains CSV data files related to all the transactions registered in the system.\
    \
    You can find out more about the file structure stored in this folder in this article:\
    [Transactions](/technical-guide/data-exports/data-structure-and-types/transactions.md)<br>
16. **WalletBalance/**\
    Contains CSV data files with a daily update of the current member wallets balance at the end of each day.\
    \
    You can find out more about the file structure stored in this folder in this article:\
    [Wallet Balance](/technical-guide/data-exports/data-structure-and-types/wallet-balance.md)


---

# 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.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.