> 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/report.md).

# Report

Export pass-level wallet events for campaign analysis, CRM enrichment, and external reporting.

The **Report** page exports pass-level event data, including installs, updates, removals, scans, and notifications, filtered by date range and pass attributes. It is the right view when the underlying records matter more than the totals.

Use this page to analyse campaign performance in detail, enrich CRM records with wallet activity, or feed wallet data into external reporting tools. For aggregated trends and KPI summaries, use [Analytics dashboards](/guides-monitoring/monitor/analytics-dashboards.md).

<details>

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

* A marketing team exports install events after a campaign send to compare channel performance by `Medium` or `Tag`.
* An operations team exports uninstall events to identify customers who no longer keep the pass in their wallet.
* A BI team exports scan events to study redemption patterns by location, store, or time window.

</details>

## What data can be exported

The **Report** page exports one row per event. This makes it useful for detailed analysis, reconciliation, and downstream processing.

The following event types are available for export:

* **Pass:Created** — when a pass record was created
* **Pass:Installed** — when a pass was added to Apple Wallet or Google Wallet, including installation source details such as **Medium**, **Tag**, **URL**, and **Host**
* **Pass:Uninstalled** — when a pass was removed from all wallets
* **Pass:Updated** — when pass data changed
* **Pass:UpdateSent** — when a push update was delivered to a device
* **Pass:Scanned** — when a pass barcode was scanned
* **Pass:NotificationSent** — when a push notification was sent

Each export focuses on event history rather than summary counts. That makes it possible to trace what happened, when it happened, and which pass was affected.

For the meaning and limits of each tracked event, see [What The Wallet Crew tracks](/guides-monitoring/monitor/what-the-wallet-crew-tracks.md).

## How to export

The export flow is designed for quick filtering and repeatable reporting. Start with the time period, then narrow the scope to the events and pass records that matter.

{% stepper %}
{% step %}

### Select a date range

Choose the period to analyse. The selected range controls which events are included in the file.
{% endstep %}

{% step %}

### Choose the event types

Select the event types to include in the export. This keeps the file focused on the activity needed for the task.
{% endstep %}

{% step %}

### Apply filters

Filter by template or by pass metadata field value. This helps isolate a campaign, a pass family, a region, a store group, or any other segment tracked in pass data.
{% endstep %}

{% step %}

### Export the file

Click **Export** to download the current selection as a CSV file. The file can then be opened in spreadsheet tools or loaded into CRM and BI workflows.
{% endstep %}
{% endstepper %}

## Using exported data

Exports are most useful when a team needs to work at record level. They support operational follow-up, campaign review, and external analysis without relying on aggregated dashboards alone.

### CRM sync

Export install events and match them on a stable pass identifier. This makes it possible to enrich contact records with wallet opt-in or installation status.

### Campaign attribution

Filter install events by **Medium** or **Tag** to compare which channels drove the most installs for a campaign. This helps connect wallet adoption back to the source that generated it.

### Churn detection

Export uninstall events to identify customers who removed their pass. This can support churn analysis, win-back actions, or journey adjustments.

### Scan analytics

Export scan events to analyse redemption patterns by location or time of day. This is useful when the goal is to understand not just adoption, but real pass usage.

## When to use Report vs Analytics dashboards

**Report** is the detailed view. It exports the individual rows behind wallet activity.

**Analytics dashboards** are the summary view. They show trends, totals, and KPI changes for faster monitoring. Use [Analytics dashboards](/guides-monitoring/monitor/analytics-dashboards.md) when the goal is to review programme performance at a glance.


---

# 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/report.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.