> 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/challenge-member-progress.md).

# Challenge Member Progress

Each member's progress towards each challenge, exported daily as a delta file.

The Challenge Member Progress file contains each member's progress towards each challenge. It is the challenge equivalent of [Achievement Usage](/technical-guide/data-exports/data-structure-and-types/achievement-usage.md).

{% hint style="info" %}
**Delta export.** Each daily file contains the member–challenge progress entries whose progress changed during that day. An entry reappears whenever the member makes further progress. Upsert on `campaignId` + `customerId` and keep the row with the latest `updatedAt`.
{% endhint %}

{% hint style="warning" %}
This report is **not** available by default. To enable it for your environment, contact the Open Loyalty support team.
{% endhint %}

**File:** `analytics/Challenges/challenges_member_progress_YYYY_MM_DD.csv`\
**Primary key:** `campaignId` + `customerId`

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

<table><thead><tr><th width="219.80859375">Column</th><th width="124.546875">Type</th><th width="117.54296875">Empty value</th><th>Description</th></tr></thead><tbody><tr><td><code>campaignId</code></td><td><code>uuid</code></td><td>No</td><td>ID of the challenge</td></tr><tr><td><code>campaignName</code></td><td><code>string</code></td><td>No</td><td>Name of the challenge</td></tr><tr><td><code>campaignDescription</code></td><td><code>string</code></td><td>Yes</td><td>Description of the challenge</td></tr><tr><td><code>customerId</code></td><td><code>uuid</code></td><td>No</td><td>ID of the member</td></tr><tr><td><code>limitReached</code></td><td><code>boolean</code></td><td>False</td><td>Whether the member reached the completion limit</td></tr><tr><td><code>completedCount</code></td><td><code>integer</code></td><td>No</td><td>Number of completed challenges</td></tr><tr><td><code>memberProgressRules</code></td><td><code>json array</code></td><td>No</td><td>Progress on each challenge rule</td></tr><tr><td><code>createdAt</code></td><td><code>datetime</code></td><td>No</td><td>Date when the progress entry was created</td></tr><tr><td><code>completedAt</code></td><td><code>datetime</code></td><td>Yes</td><td>Date when the member last completed the challenge</td></tr><tr><td><code>tenantId</code></td><td><code>uuid</code></td><td>No</td><td>ID of the tenant where the challenge was created</td></tr><tr><td><code>updatedAt</code></td><td><code>datetime</code></td><td>No</td><td>Date of the most recent progress update</td></tr></tbody></table>

{% hint style="warning" %}
`limitReached`, `completedCount`, and `memberProgressRules` are calculated **when the file is produced**, not at the end of the day the file covers.
{% endhint %}

{% hint style="info" %}
Achievements that were migrated to challenges can appear both here and in the Achievement Usage 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 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/challenge-member-progress.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.