> 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/implementation-guide/integrations-and-data-exchange/imports-exports/exports/ui-exports/dashboard.md).

# Dashboard

Export the General overview and Units Wallet overview dashboard reports to share metrics outside the Admin Panel or feed them into your own reporting tools.

**File format:** PNG, JPG, or CSV

#### Sample CSV file

{% file src="/files/8xRS4dSqijXoLSLa1HlL" %}

#### Field reference — General overview

<table><thead><tr><th width="220">Field</th><th>Description</th></tr></thead><tbody><tr><td><code>registeredMembers</code></td><td>Total number of registered members in the selected period</td></tr><tr><td><code>activeMembers</code></td><td>Number of members who were active in the selected period</td></tr><tr><td><code>revenue</code></td><td>Total revenue from transactions in the selected period</td></tr><tr><td><code>avgSpending</code></td><td>Average spend per member</td></tr><tr><td><code>transactions</code></td><td>Total number of transactions (purchases)</td></tr><tr><td><code>avgTransactionValue</code></td><td>Average value per transaction</td></tr><tr><td><code>avgNumberOfTransactions</code></td><td>Average number of transactions per member</td></tr><tr><td><code>returnTransactions</code></td><td>Total number of return transactions</td></tr><tr><td><code>totalReturns</code></td><td>Total value of returns</td></tr><tr><td><code>avgReturnValue</code></td><td>Average value per return</td></tr><tr><td><code>avgNumberOfReturnTransactions</code></td><td>Average number of returns per member</td></tr></tbody></table>

#### Field reference — Units Wallet overview

<table><thead><tr><th width="220">Field</th><th>Description</th></tr></thead><tbody><tr><td>Issued Units</td><td>Total units issued, counted at the end of the period (based on all unit transfers — active, used, expired, blocked, or spent). Only decreases if a transfer is canceled.</td></tr><tr><td>Active Units</td><td>Total active units accumulated by members at the end of the period (includes blocked units)</td></tr><tr><td>Pending Units</td><td>Total pending units accumulated by members at the end of the period</td></tr><tr><td>Spent Units</td><td>Total units spent by members at the end of the period</td></tr><tr><td>Expired Units</td><td>Total units expired at the end of the period</td></tr><tr><td>Redemption rate</td><td>Spent ÷ issued units</td></tr><tr><td>Breakage rate</td><td>Expired ÷ issued units</td></tr></tbody></table>

{% hint style="info" %}
Active and Pending Units are always shown as accumulated values, not deltas — each period's figure already includes carry-over from prior periods.
{% endhint %}

{% hint style="info" %}
Aggregation granularity depends on the selected date range: 1–30 days aggregates daily, 31–90 days weekly, 91–360 days monthly, and over 360 days annually.
{% 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 dynamically 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/implementation-guide/integrations-and-data-exchange/imports-exports/exports/ui-exports/dashboard.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 `build a script that syncs our docs to a CMS` 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.