> 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/getting-started-1/dashboard/units-wallet-overview.md).

# Units Wallet Overview

The dashboard is the first page that appears when you log in to the Admin panel. The dashboard gives an overview of the members' activity in your loyalty programs.

## Units Wallet Overview

The **Units Wallet Overview** displays the history of different types of units per wallet, allowing for easy analysis.

<figure><img src="https://2658975168-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNVX03KZzmrGwJihLiEx%2Fuploads%2Fgit-blob-0647ccdff8df990d31e631acc84ed7302520dddf%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

* **Issued Units** - the total number of issued units counted at the end of the period. The metric is calculated based on unit transfers, whether they are active, used, expired, blocked, or spent. This value increases unless the units are canceled.
* **Active Units (Cumulative)\*** - the total number of active units accumulated by members at the end of a selected period (blocked units are included)
* **Pending Units (Cumulative)\*** - the total number of pending units accumulated by members at the end of a selected period
* **Spent Units** - the total number of spent units by member at the end of the selected period
* **Expired Units** - the total number of expired units at the end of the selected period
* **Redemption rate** - the rate of points that have been issued and spent (Redemption rate value = spent/issued
* **Breakage rate** - the rate of points that have been issued and expired (Breakage rate value = expired/issued

{% hint style="info" %}
**\***&#x41;ctive and pending units are always displayed as accumulated. The example below (custom range of 4 days)
{% endhint %}

<table data-full-width="false"><thead><tr><th>Description</th><th>1st day</th><th>2nd day</th><th>3rd day</th><th>4h day**</th></tr></thead><tbody><tr><td>The initial amount of units</td><td>100</td><td></td><td></td><td></td></tr><tr><td>Amount of points visible on the chart (<strong>+ units added to the wallet that day)</strong></td><td></td><td>250 <strong>(+150)</strong></td><td>320 <strong>(+70)</strong></td><td>420 <strong>(+100)</strong></td></tr><tr><td><strong>+ Total amount of added units</strong></td><td></td><td></td><td></td><td><strong>+320</strong></td></tr></tbody></table>

{% hint style="info" %}
**\*\***&#x41;mount of Units displayed on the dashboard "Active (Cumulative)"

<img src="https://2658975168-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcNVX03KZzmrGwJihLiEx%2Fuploads%2Fgit-blob-30f39a776120b6f1a53350cf245bb162d83caf3c%2FScreenshot%202024-01-22%20at%2011.53.08.png?alt=media" alt="" data-size="original">
{% 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/getting-started-1/dashboard/units-wallet-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.