> For the complete documentation index, see [llms.txt](https://docs.perkville.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perkville.com/features/reports/redemption-overview.md).

# Redemption Overview

The Redemption Overview Report provides a comprehensive view of all perks redeemed across your locations. This report helps you track the overall redemption activity.

## **Filters for the Redemption Overview Report**

Before running the report, you can apply the following filters to customize the data:

* **Start Date/End Date:** Define the date range for when the voucher was created. This filter covers the creation date of the voucher, not the date it was used.
* **Locations:** Select the locations where the voucher was redeemed.

## **Columns in the Redemption Overview Report**

* **Used:** Vouchers that have been marked as Used.
* **Unused:** Vouchers that have not yet been marked as Used.
* **Expired:** Vouchers that expired prior to being used.
* **Credited:** Rewards sent directly to a customer’s account within the POS system. Currently, this is applicable only to MindBody and Lightspeed Cloud/Retail businesses with connected redeeming rules.
* **Voided:** Vouchers with Voided status, meaning access to the voucher was removed, and points were added back to the customer's account.
* **Emailed Reward:** Rewards that were emailed to a customer by an external reward provider.
* **Perk Total:** The total `quantity` of all rewards redeemed, including voided vouchers.

{% hint style="info" %}
If a `quantity` greater than one is redeemed in a single transaction only one voucher will be generated. Because of this, "Perk Total" and other columns might not add up.
{% 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://docs.perkville.com/features/reports/redemption-overview.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.
