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

# Achievements

Achievement configuration exported daily as a delta file.

The Achievements file contains the achievements and their basic configuration.

{% hint style="info" %}
**Delta export.** Each daily file contains the achievements that were created or updated during that day. An achievement reappears in a later file whenever it changes. Upsert on `achievementId` and keep the row with the latest `updatedAt`.
{% endhint %}

**File:** `analytics/Achievements/achievements_YYYY_MM_DD.csv`\
**Primary key:** `achievementId`

A sample file is provided below:

{% file src="/files/mlrpMJX3byhzK9HZ3JDX" %}

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

<table><thead><tr><th width="167.7578125">Column</th><th width="115.87890625">Type</th><th width="116.7890625">Empty value</th><th>Description</th></tr></thead><tbody><tr><td><code>achievementId</code></td><td><code>uuid</code></td><td>No</td><td>Unique ID of the achievement</td></tr><tr><td><code>name</code></td><td><code>string</code></td><td>No</td><td>Name of the achievement</td></tr><tr><td><code>active</code></td><td><code>boolean</code></td><td>False</td><td>Whether the achievement is active</td></tr><tr><td><code>createdAt</code></td><td><code>datetime</code></td><td>No</td><td>Date when the achievement was created</td></tr><tr><td><code>tenantId</code></td><td><code>uuid</code></td><td>No</td><td>ID of the tenant where the achievement was created</td></tr><tr><td><code>updatedAt</code></td><td><code>datetime</code></td><td>No</td><td>Date when the achievement was last updated</td></tr></tbody></table>

{% hint style="warning" %}
Deleted achievements are not flagged in this file. A deleted achievement stops appearing in later files.
{% 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 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/achievements.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.