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

# Rewards Redemption

The Rewards Redemption file contains information about members' reward redemptions.

{% hint style="info" %}
**Delta export.** Each daily file contains issued rewards created or updated during that day. Upsert on `issuedRewardId` and keep the row with the latest `updatedAt`.
{% endhint %}

**File:** `analytics/Rewards/issued_rewards_YYYY_MM_DD.csv`\
**Primary key:** `issuedRewardId`

A sample file is provided below:

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

**Available Data:**

<table><thead><tr><th width="197.03515625">Column</th><th width="121.76953125">Type</th><th width="114.54296875">Can be empty</th><th>Description</th></tr></thead><tbody><tr><td><code>issuedRewardId</code></td><td>uuid</td><td>No</td><td>Unique ID of the issued reward</td></tr><tr><td><code>tenantId</code></td><td>uuid</td><td>No</td><td>ID of the tenant where the reward was issued</td></tr><tr><td><code>reward</code></td><td>json object</td><td>Yes</td><td>Reward configuration at export time</td></tr><tr><td><code>name</code></td><td>string</td><td>Yes</td><td>Name of the reward</td></tr><tr><td><code>memberId</code></td><td>uuid</td><td>No</td><td>ID of the member the reward was issued to</td></tr><tr><td><code>memberData</code></td><td>json object</td><td>No</td><td>Member details</td></tr><tr><td><code>costInPoints</code></td><td>decimal</td><td>No</td><td>Units paid for the reward</td></tr><tr><td><code>token</code></td><td>string</td><td>No</td><td>Material-reward token or coupon code</td></tr><tr><td><code>redemptionDate</code></td><td>datetime</td><td>No</td><td>Date the reward was issued</td></tr><tr><td><code>rewardType</code></td><td>enum</td><td>No</td><td><code>material</code>, <code>static_coupon</code>, <code>dynamic_coupon</code>, <code>conversion_coupon</code>, or <code>fortune_wheel</code></td></tr><tr><td><code>tax</code></td><td>decimal</td><td>Yes</td><td>Tax value</td></tr><tr><td><code>taxPriceValue</code></td><td>decimal</td><td>Yes</td><td>Tax price value</td></tr><tr><td><code>price</code></td><td>decimal</td><td>Yes</td><td>Reward price</td></tr><tr><td><code>status</code></td><td>string</td><td>Yes</td><td>Current status</td></tr><tr><td><code>statusLastUpdatedAt</code></td><td>datetime</td><td>Yes</td><td>Date of the last status change</td></tr><tr><td><code>issuedCoupon</code></td><td>json object</td><td>Yes</td><td>Coupon details</td></tr><tr><td><code>actionCause</code></td><td>json object</td><td>Yes</td><td>Campaign issue trigger data</td></tr><tr><td><code>createdAt</code></td><td>datetime</td><td>No</td><td>Date created</td></tr><tr><td><code>updatedAt</code></td><td>datetime</td><td>No</td><td>Date last updated</td></tr></tbody></table>


---

# 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/rewards-redemption.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.