> 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

Understand Apple Wallet and Google Wallet pass, enrolment and link performance in the Analytics dashboards of The Wallet Crew admin console.

The Wallet Crew includes three dashboards in the **Analytics** section of the admin console: **Wallets**, **Enrollments** and **Links**, plus **Benefits** in beta. Each dashboard covers a different stage of the wallet program lifecycle.

All dashboards include a date range picker that controls every tile, chart and table. It defaults to **Last 30 days**. The **Wallets** dashboard also supports filtering and Excel export (see [Export data](https://docs.thewalletcrew.io/guides-monitoring/monitor/report.md)).

The dashboards are built on the Insights API. To query the same events with custom filters, groupings or BI tools, see the [Insights API](https://docs.thewalletcrew.io/developers-guides/integration-guides/insights-api.md).

## Wallets

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

The **Wallets** dashboard gives a live overview of a wallet program. It tracks issuance, adoption, removals, engagement, 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.

<figure><img src="https://4037142687-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEsokFUBfsbM9mlwavmMB%2Fuploads%2Fgit-blob-d1d9383e4aaf9f6e1711cda3a799ef22a5a2b09c%2Fanalytics-wallets-dashboard.png?alt=media" alt="Wallets dashboard with the Passes created, Passes added and Passes removed tiles, the Passes added over time chart, the Pass distribution chart and the Channel breakdown table"><figcaption></figcaption></figure>

### KPIs

The KPI tiles separate issuance, adoption, churn and engagement. Each tile compares results with the previous equivalent period (see [Understanding the change indicator](https://docs.thewalletcrew.io/guides-monitoring/monitor/kpi-definitions.md#understanding-the-change-indicator)). Three tiles are shown by default: **Passes created**, **Passes added** and **Passes removed**, defined in [KPI definitions](https://docs.thewalletcrew.io/guides-monitoring/monitor/kpi-definitions.md). Each tile can show another metric instead.

* **Passes updated** — Pass update events during the period.
* **Notifications sent** — Push notifications sent to pass holders during the period.
* **Links opened** — Taps on tracked links inside a pass during the period. This measures engagement with the pass itself.

Compare **Passes created** and **Passes added** to understand [activation rate](https://docs.thewalletcrew.io/guides-monitoring/monitor/kpi-definitions.md#activation-rate).

### Charts

**Passes added over time** shows daily installation volume. Use it to identify changes after sends, launches, or in-store campaigns. The same chart can be switched to updates, notifications sent, or links opened, so engagement can be read on the same timeline as adoption.

**Pass distribution** splits installations between Apple Wallet and Google Wallet. It can also show **Removals by Wallet** and **Taps by Wallet**. The wallet mix helps plan wallet-specific actions: for example, Google Wallet shows at most three notifications per pass every 24 hours (see [Push notifications](https://docs.thewalletcrew.io/guides-animation/engage-and-animate/automatisation/push-notifications.md)).

### Source breakdown

The breakdown table compares the channels and pass dimensions that drive wallet saves. Its group-by selector defaults to **Channel** (`source.medium`).

#### Grouping options

Source groupings include:

* **Channel** — Distribution channels, such as `email-crm`, `ecomm`, or `trigger-crm`. `Not specified` means the pass was installed without a tracked source, such as device transfer or sharing.
* **Tag** — Campaign or segment tags attached to the installation source, set when the distribution link is generated.
* **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.

The same selector offers a **Link opened** group, which switches the table to the links customers tapped inside their pass rather than the sources that drove installs.

#### Table columns

Source groupings show the source value and **Added passes**. Metadata groupings show the metadata value, **Created passes**, **Added passes**, and [**Activation rate**](https://docs.thewalletcrew.io/guides-monitoring/monitor/kpi-definitions.md#activation-rate).

The **Link opened** group shows **Opened links** against the target URL, the device, the origin — where in the pass the link was placed — the source ID that tells apart several links sharing one origin, the pass template (column **Pass type**), and the language the customer read. [Measure link clicks in passes](https://docs.thewalletcrew.io/guides-monitoring/monitor/measure-link-clicks.md) explains what each dimension means and how the same clicks reach connectors and exports.

#### Filters and export

Use **Add filter** to focus on a template or metadata value. **Export** downloads the rows of the table, as shown, as an Excel file. See [Export data](https://docs.thewalletcrew.io/guides-monitoring/monitor/report.md).

## Enrollments

**Location:** **Analytics → Enrollments**

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

<figure><img src="https://4037142687-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEsokFUBfsbM9mlwavmMB%2Fuploads%2Fgit-blob-960026395c093c2260daec45db87572e65f72470%2Fanalytics-enrollments-dashboard.png?alt=media" alt="Enrollments dashboard with the Customers created or updated, Customers created and Customers updated tiles, the Customer enrollment chart and the Breakdown by period table"><figcaption></figcaption></figure>

### KPIs

* **Customers created or updated** — Total profile create-or-update operations (`Customer:Upserted` events).
* **Customers created** — Net-new customer profiles created.
* **Customers updated** — Updates to existing customer profiles.

### Chart

**Customer enrollment** 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.

<figure><img src="https://4037142687-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEsokFUBfsbM9mlwavmMB%2Fuploads%2Fgit-blob-3e8dff2c2f790671b98bad56cc52aaedb3148f57%2Fanalytics-links-dashboard.png?alt=media" alt="Links dashboard with the QR codes scanned tile, the QR codes scanned over time chart and the Scans per link table"><figcaption></figcaption></figure>

{% hint style="info" %}
This dashboard measures the links and QR codes used to hand out passes. Clicks on links **inside** a wallet pass are a separate measurement, reported on the **Wallets** dashboard and covered in [Measure link clicks in passes](https://docs.thewalletcrew.io/guides-monitoring/monitor/measure-link-clicks.md).
{% endhint %}

### 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 **Scans per link** table shows which individual links or QR codes drove the most scans. It includes the following columns:

* **Key** — The ID of the link, as in **Enrollments → Links & QR codes**.
* **Count** — The total number of scans.

## Benefits

**Location:** **Analytics → Benefits**

{% hint style="info" %}
**Benefits** is a beta feature. The menu entry shows when **Beta features** is turned on in the profile menu of the admin console.
{% endhint %}

The **Benefits** dashboard tracks how benefits are used. Filter it by **Tag**, **Benefit template**, **Type** or **Channel** (Console, Pass Scanner, Connector, Unattributed).

* **Used** — Uses taken in the selected period. Give backs are not counted.
* **Engaged passes** — Unique passes that used a benefit in the selected period.
* **New benefits** — Benefits granted to passes in the selected period.
* **Deleted benefits** — Benefits removed in the selected period.

It also shows a **Used over time** chart, the **Top benefit templates**, and a **Benefit template performance** table with the columns **Benefit template**, **Granted**, **Used**, **Rate** and **Last use**.

<figure><img src="https://4037142687-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEsokFUBfsbM9mlwavmMB%2Fuploads%2Fgit-blob-0c9e6f9d9155bd63544a87a0a6d381b984627528%2Fanalytics-benefits-dashboard.png?alt=media" alt="Benefits dashboard with Used, Engaged passes and Top benefit templates"><figcaption></figcaption></figure>


---

# 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.thewalletcrew.io/guides-monitoring/monitor/analytics-dashboards.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.
