Skip to main content

Wallet Analytics

Wallet Analytics is the aggregate report for your Wallet Passes: how many passes you issued, how many recipients actually added them to their phone, how many were scanned or redeemed, and how well they retain - broken down by source, platform, or template.

Navigate to Analytics → Wallet Analytics from the sidebar.

What is being counted​

The report is built from the wallet lifecycle events Joryio records automatically:

StageEventWhen it fires
Issuedpass.issuedA pass was provisioned for a contact
Downloadedpass.downloadedThe install link was opened and the pass file was served
Installedpass.installedThe pass was added to a device's wallet
Scannedpass.scannedThe pass barcode was scanned or redeemed

The funnel unit is a distinct pass, not an event: a pass that is scanned five times still counts once toward "scanned". Bot traffic is filtered out.

The install signal differs by platform: for Apple Wallet it comes from the device registering the pass with the wallet web service; for Google Wallet it comes from Google's save/delete callback.

Filters​

Two controls at the top of the page shape everything below:

  • Date range - defaults to the last 30 days. Dates are interpreted in your workspace timezone.
  • Breakdown - the dimension for the breakdown table:
    • Source - where the pass was issued from: a campaign, a journey node, or manual issuance. Passes issued without attribution are grouped into a placeholder bucket.
    • Platform - Apple vs. Google.
    • Template - the pass template, shown by name and linked to its editor.

Stat cards​

Five headline tiles summarize the selected period:

  • Passes Issued - distinct passes provisioned.
  • Download Rate - downloaded / issued, with the absolute downloaded count beneath.
  • Installation Rate - installed / issued, with the absolute installed count beneath.
  • Scan / Redemption Rate - scanned / issued, with the absolute scanned count beneath.
  • Retention (scan after install) - scanned / installed: of the passes that made it onto a device, how many were actually used at the point of scan.

The Adoption Funnel​

The funnel chart shows the pass journey as three ordered stages:

Issued → Downloaded → Scanned

Each stage shows its pass count, its conversion rate against the issued cohort, and the drop-off versus the previous stage.

Installed is deliberately reported alongside the funnel (in the stat cards and the breakdown table) rather than as a chart stage: install tracking coverage differs between Apple and Google, so gating the cross-platform funnel on it would distort the picture. Use the Installation Rate tile and the per-group install columns for the install story, and switch the breakdown to Platform to compare Apple and Google directly.

If there was no wallet pass activity in the selected period, the chart shows an empty state instead of zeros.

The breakdown table​

Below the funnel, a table splits the same numbers by your chosen breakdown dimension. Columns:

ColumnMeaning
Source / Platform / TemplateThe breakdown value
IssuedDistinct passes issued in this group
DownloadedDistinct passes downloaded
InstalledDistinct passes installed
ScannedDistinct passes scanned
Install %installed / issued for the group
Scan %scanned / issued for the group
Retention %scanned / installed for the group

Rows are sorted by issued count. In the Template breakdown, each row links to that template's editor, so you can jump straight from a weak row to fixing the design.

How to use it​

  • Low Download Rate - recipients aren't tapping the Add-to-Wallet link. Look at where the link sits in your message and how it's presented; compare sources to see which campaign or journey placement performs.
  • Downloads without installs - the install page was opened but the pass didn't land in a wallet. Compare the Platform breakdown; a gap on one platform usually points at that platform's flow.
  • Low Scan % - passes are installed but not used. That's a pass-value question: the offer, barcode placement, or in-store process. Compare templates to see which designs get redeemed.
  • Retention % - the truest "did this pass earn its place" number, since it only considers passes that made it onto a device.
  • Compare sources across the whole funnel - because the source is stamped on every lifecycle event, you can tell not just which campaign or journey issued the most passes, but which one produced passes that actually get scanned.

Notes​

  • The source on a pass is stamped at issuance and carried through every lifecycle event, so the whole funnel - not just issuance - can be split by source. Events recorded before source stamping existed have no source and fall into the unattributed bucket.
  • Uniqueness is by pass serial number: a pass counts once per stage no matter how many times the underlying event repeats.
  • Other lifecycle events (pass.updated, pass.removed, pass.voided) are recorded on the contact timeline but are not part of this funnel report.
  • Viewing this page requires wallet read permission in your role.
  • Per-contact wallet history (issued passes, status, timeline) lives on the contact's Wallet tab, not here.
  • Wallet events are also available for segmentation and journey triggers - see Wallet Passes for the full event list.