> 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/what-the-wallet-crew-tracks.md).

# What The Wallet Crew tracks

Understand which Apple Wallet and Google Wallet events The Wallet Crew tracks, how pass installs are counted, and where Apple and Google set limits.

The Wallet Crew tracks pass activity through events generated at each meaningful moment in the pass lifecycle. This page explains what is tracked, how installation counting works, and what cannot be tracked, along with the Apple and Google platform rules behind those limits.

## What is tracked

The Wallet Crew records the lifecycle events that wallet platforms expose and that the pass flow can reliably generate. Some events describe the pass itself, while others describe what happened on a wallet or device.

### Pass creation

A pass record is created in The Wallet Crew when a pass is issued. This can happen through the API, after account creation, when a download page creates the pass for a visitor who has none (`passCreation.flow`), or through a connector.

A created pass exists in the platform even if no one has added it to a wallet yet. Creation shows issuance. It does not confirm adoption.

### Pass installation

The platform tracks when a pass is added to a wallet. Installation counting works differently on Apple Wallet and Google Wallet because each provider defines installation in its own way.

* **Apple Wallet** tracks each device individually. Adding the same pass to an iPhone and an Apple Watch counts as two installations. Moving to a new phone also creates a new installation.
* **Google Wallet** tracks installation per Google account. Multiple Android devices connected to the same account count as one installation.

Two counters exist for each pass:

* **Active installations** (`registrationInformation.activeRegistrationCount`) — decreases when the pass is removed from a wallet
* **Total installations** (`registrationInformation.totalRegistrationCount`) — cumulative and never decreases

These counters serve different purposes. Active installations show how many valid wallet presences still exist. Total installations show how many times the pass has ever been installed. For example, a pass that is installed, removed and installed again has a total of 1, then 1, then 2, and an active count of 1, then 0, then 1.

### Installation source

When a customer taps an **Add to Wallet** button, The Wallet Crew captures the source context of that action. This helps connect wallet adoption back to the campaign or page that triggered it.

* **Medium** — the distribution channel (shown as **Channel** in the dashboards), such as email, e-commerce, or store
* **Tag** — custom campaign or segment tags
* **URL** — the exact page where the button was displayed
* **Host** — the domain of that page

Source data is not available when a pass is installed through device transfer, phone sharing, or other system-level mechanisms. In those cases, the wallet platform completes the install without sending the original acquisition context back.

### Pass removal

The Wallet Crew tracks when a pass is removed from a wallet. Each removal decreases the active installation count. A `Pass:Uninstalled` event is recorded when the pass leaves its last device on Apple Wallet or on Google Wallet, and its `registrationInformation.activeRegistrationCount` tells whether the pass is still installed anywhere.

When the active installation count reaches zero across both wallets, the pass is fully uninstalled. This matters for churn analysis because a pass removed from one device may still remain active on another. See `Pass:Uninstalled` in the [event reference](#event-reference).

### Updates sent

Each push update delivered to a device is recorded. This makes it possible to review update activity over time and understand how often pass content is being refreshed.

### Scans

Each barcode scan is recorded, including the scanned data and scan type. This makes scan history useful for redemption and operational verification.

### Push notifications sent

Each push notification sent to a device is recorded, including its content and the wallet provider. This confirms that the notification was sent through the platform.

### Link clicks

Taps on tracked links inside a pass are recorded with the link position, the wallet, the language and the destination. See [Measure link clicks in passes](https://docs.thewalletcrew.io/guides-monitoring/monitor/measure-link-clicks.md).

## Event reference

Each event is recorded with the pass it belongs to. The History tab of a pass lists them (see [Pass details](https://docs.thewalletcrew.io/guides-monitoring/monitor/pass-details.md#history)), and webhooks and the Insights API deliver them.

| Event                                                                              | What it means                                                                                                                                                                                                                           |
| ---------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Pass:Created`                                                                     | The pass was created.                                                                                                                                                                                                                   |
| `Pass:Updated`                                                                     | The pass was updated.                                                                                                                                                                                                                   |
| `Pass:Installed`                                                                   | The pass was added to a wallet.                                                                                                                                                                                                         |
| `Pass:Uninstalled`                                                                 | The pass was removed from its last device on one wallet (Apple Wallet or Google Wallet). It can still be installed on the other wallet: `registrationInformation.activeRegistrationCount` is `0` only when no wallet holds it any more. |
| `Pass:UpdateSent`                                                                  | An update of the pass was sent to Apple or Google for a device.                                                                                                                                                                         |
| `Pass:NotificationSent`                                                            | A notification was sent to an installed pass.                                                                                                                                                                                           |
| `Pass:Scanned`                                                                     | The pass was scanned.                                                                                                                                                                                                                   |
| `Pass:LinkOpened`                                                                  | The holder tapped a tracked link of the pass.                                                                                                                                                                                           |
| `Pass:IdentifiersChanged`                                                          | An update added, changed or removed an identifier.                                                                                                                                                                                      |
| `Pass:MetadataChanged`                                                             | The value of at least one metadata key changed.                                                                                                                                                                                         |
| `Pass:PassTypeChanged`                                                             | An update moved the pass to another template.                                                                                                                                                                                           |
| `Pass:ThemeChanged`                                                                | An update moved the pass to another theme, or removed its theme.                                                                                                                                                                        |
| `Pass:StampApplied`, `Pass:GoalReached`, `Pass:StampsReset`                        | Stamp card movements.                                                                                                                                                                                                                   |
| `Benefit:Created`, `Benefit:Updated`, `Benefit:Deleted`, `Benefit:MovementApplied` | Benefits granted to the pass, changed, removed or used.                                                                                                                                                                                 |

## What cannot be tracked

{% hint style="warning" %}
These are privacy decisions made by Apple and Google to protect customers, not limitations of The Wallet Crew. Every wallet platform faces the same constraints.
{% endhint %}

Some signals seem natural to expect, but the wallet providers do not expose them. When the platform does not receive the data, it cannot report it later.

| What might be expected      | Why it is not available                                                                                                          |
| --------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| Pass opens or views         | Apple and Google do not report whether a customer viewed a pass. There is no equivalent of an email open rate for wallet passes. |
| Push notification tap rates | Delivery can be confirmed. Whether the customer tapped the notification is not reported by either platform.                      |
| Geo-trigger activations     | Location triggers fire on the device. The device does not report back to the issuer when this happens.                           |
| Per-device count on Google  | Google tracks installation per account. Three Android devices on one account still count as one installation.                    |

## Pass state

Pass state (used, expired) is set by the template: see [Pass state model](https://docs.thewalletcrew.io/developers-guides/integration-guides/wallet/pass-lifecycle.md#pass-state-model).

## Using this data

Tracked wallet events are useful across marketing, operations, and CRM workflows. They help teams act on real lifecycle signals rather than assumptions.

* Trigger a CRM update when a pass is first installed to confirm wallet opt-in
* Identify customers whose pass is no longer installed (`activeRegistrationCount` is `0`) as a churn signal
* Attribute installs back to source channel with **Medium** and **Tag**
* Use scan events to confirm redemption at point of sale
* Compare which links inside the pass are tapped, and follow that traffic through to the destination site

For downstream use, see [Insights API](https://docs.thewalletcrew.io/developers-guides/integration-guides/insights-api.md) for programmatic queries and [Send wallet events to your tools](https://docs.thewalletcrew.io/guides-monitoring/monitor/send-wallet-events-to-your-tools.md) for real-time delivery.


---

# 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/what-the-wallet-crew-tracks.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.
