> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/guides-monitoring/monitor/analytics-dashboards.md).

# Analytics dashboards

The Wallet Crew includes three dashboards in the **Analytics** section of the admin console. Each dashboard covers a different stage of the wallet programme lifecycle.

All dashboards include a date range picker. It defaults to **Last 30 Days**. The **Wallets** dashboard also supports filtering and CSV export.

<details>

<summary><strong>Real-world examples</strong></summary>

* A retail brand compares wallet saves by acquisition channel after a campaign launch.
* An event organiser tracks enrolment form activity before a ticket release.
* An in-store team identifies which QR codes generate the most wallet saves.

</details>

## Wallets

**Location:** **Analytics** → **Wallets**

The **Wallets** dashboard gives a live overview of a wallet programme. It tracks issuance, adoption, removals, source performance, and wallet mix during the selected period.

Use it to assess campaign impact, spot unexpected changes, and compare results by source, template, or pass metadata.

### KPIs

The KPI tiles separate issuance, adoption, and churn. Each tile compares results with the previous equivalent period.

* **Passes Created** — Total pass records created during the period. Creation does not confirm wallet adoption.
* **Passes Installed** — Passes saved to Apple Wallet or Google Wallet during the period. This measures adoption.
* **Passes Uninstalled** — Passes removed from every device where they were installed. This measures churn.

Compare **Passes Created** and **Passes Installed** to understand [activation rate](/guides-monitoring/monitor/kpi-definitions.md). The rate is calculated as `Installed Passes ÷ Created Passes`.

{% hint style="info" %}
Passes Created ≠ Passes Installed. A created pass is not necessarily saved to a wallet.
{% endhint %}

### Charts

**Evolution of installations** shows daily installation volume. Use it to identify changes after sends, launches, or in-store campaigns.

**Pass Distribution** splits installations between Apple Wallet and Google Wallet. The wallet mix helps plan wallet-specific actions. Google Wallet limits pushes to three updates per pass every 24 hours.

### Source breakdown

The breakdown table compares the channels and pass dimensions that drive wallet saves. Its group-by selector defaults to **Medium**, which corresponds to `source.medium`.

#### Grouping options

Source groupings include:

* **Medium** — Distribution channels, such as `email-crm`, `ecomm`, or `trigger-crm`.
* **Tag** — Campaign or segment tags attached to the installation source.
* **URL** and **Host** — The exact page or domain containing the **Add to Wallet** button.

Any pass metadata field can also group results. For example, use `storeId` or `storeName` to compare stores, regions, partners, or segments.

#### Table columns

Source groupings show the source value and **Installed Passes**. Metadata groupings show the metadata value, **Created Passes**, **Installed Passes**, and [**Activation rate**](/guides-monitoring/monitor/kpi-definitions.md).

#### Filters and export

Use **Add filter** to focus on a template or metadata value. **Export** downloads the current table view as a CSV file.

### Date range

The date picker controls every tile, chart, and table on the dashboard. Percentage changes use the immediately preceding equivalent period. For example, a seven-day selection compares with the previous seven days.

## Enrolments

**Location:** **Analytics** → **Enrolments**

Enrolment metrics track customer profile activity driven by enrolment forms. Use this dashboard to monitor profile creation and updates during the selected period.

### KPIs

* **Customer Upserted** — Total profile create-or-update operations.
* **Customer Created** — Net-new customer profiles created.
* **Customer Updated** — Updates to existing customer profiles.

### Chart

**Customer enrolment over time** shows customer profile activity across the selected period.

## Links

**Location:** **Analytics** → **Links**

Links metrics track QR code and redirect link usage. Use this dashboard to measure in-store or on-site distribution performance.

### KPI

* **QR codes scanned** — Total scans during the selected period.

### Chart

**QR codes scanned over time** shows scan activity across the selected period.

### Breakdown table

The breakdown table shows which individual links or QR codes drove the most scans. It includes the following columns:

* **Key** — The link identifier.
* **Count** — The total number of scans.

## FAQ

<details>

<summary>Which date range applies to a dashboard?</summary>

The date range picker controls the full dashboard. It defaults to **Last 30 Days**. On **Wallets**, export uses the current table view.

</details>

<details>

<summary>How can Wallets focus on one pass template?</summary>

In **Analytics** → **Wallets**, select **Add filter** and narrow the dashboard to the required template.

</details>

<details>

<summary>Which dashboard measures QR code performance?</summary>

Use **Analytics** → **Links**. The dashboard shows total scans, scan activity over time, and results by link key.

</details>

<details>

<summary>Why are Passes Created often higher than Passes Installed?</summary>

Creation measures issuance. Installation measures adoption. A pass can be issued without being saved to a wallet.

</details>

<details>

<summary>Why can Passes Uninstalled stay low when removals happen?</summary>

The metric counts a pass only when every active installation is removed. A pass still installed on another device is not counted.

</details>


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.thewalletcrew.io/guides-monitoring/monitor/analytics-dashboards.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.