# Data Structure and Types ### 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). *** ### Overall Structure * **analytics/**\ This is the main folder within the bucket. All data related to analytics is organised under this folder.
### 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](https://help.openloyalty.io/technical-guide/data-exports/data-structure-and-types/achievements "mention")\ [achievement-usage](https://help.openloyalty.io/technical-guide/data-exports/data-structure-and-types/achievement-usage "mention")
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](https://help.openloyalty.io/technical-guide/data-exports/data-structure-and-types/campaigns "mention")\ [campaign-execution](https://help.openloyalty.io/technical-guide/data-exports/data-structure-and-types/campaign-execution "mention")\ [campaign-calculated-effect-results](https://help.openloyalty.io/technical-guide/data-exports/data-structure-and-types/campaign-calculated-effect-results "mention")
3. **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](https://help.openloyalty.io/technical-guide/data-exports/data-structure-and-types/campaign-visibility "mention")
4. **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](https://help.openloyalty.io/technical-guide/data-exports/data-structure-and-types/custom-events "mention")
5. **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](https://help.openloyalty.io/technical-guide/data-exports/data-structure-and-types/members "mention")
6. **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](https://help.openloyalty.io/technical-guide/data-exports/data-structure-and-types/member-tier-changes "mention")
7. **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](https://help.openloyalty.io/technical-guide/data-exports/data-structure-and-types/unit-transfers "mention")
8. **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](https://help.openloyalty.io/technical-guide/data-exports/data-structure-and-types/rewards "mention")\ [rewards-redemption](https://help.openloyalty.io/technical-guide/data-exports/data-structure-and-types/rewards-redemption "mention")
9. **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](https://help.openloyalty.io/technical-guide/data-exports/data-structure-and-types/tenants "mention")
10. **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](https://help.openloyalty.io/technical-guide/data-exports/data-structure-and-types/tiers "mention")
11. **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](https://help.openloyalty.io/technical-guide/data-exports/data-structure-and-types/transactions "mention")
12. **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](https://help.openloyalty.io/technical-guide/data-exports/data-structure-and-types/wallet-balance "mention") --- # Agent Instructions: 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: ``` GET https://help.openloyalty.io/technical-guide/data-exports/data-structure-and-types.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.