This is a common question from customers, especially since most providers don't give a clear answer.
Mobile wallet passes live within the Apple Wallet and Google Wallet ecosystems. These platforms unlock powerful features like push notifications and geolocation, but they also come with privacy rules that limit what data is shared. These aren't limitations from Badge, they're enforced by Apple and Google to protect user privacy.
That said, Badge gives you access to more pass-specific data and user insights than ever before. From detailed pass lifecycle statuses to engagement data and campaign performance, you're gaining real visibility into how users are interacting with your passes.
Below is a breakdown of the types of data available when using passes through Badge.
Pass
Statuses
Track the full lifecycle of each pass:
Created (Issued, pass is created but not yet activated), including creation date
Activated (installed with push notifications enabled), including platform: Google or Apple
Deactivated (push notifications disabled and/or pass uninstalled)
Invited (user receives email from Badge's Pass Download Link email tool)
Link Engagement
Track user interactions with links associated with the pass:
Back of pass link clicks. Tracking parameters are automatically added, so you can view Badge as the source in analytics tools like Google Analytics.
Value Added Opportunities clicks (Value Added Opportunities are clickable cards within the wallet experience)
For your CRM
Pass Download Link, which is unique per user and used by the end user to install their pass. This can be added to your UI or email and SMS communications.
Campaigns
When you create campaigns in the Workspace UI, you can track:
Status: Scheduled, Running (including number of push notifications sent and pass updates completed), Complete, and Cancelled
If you send push notifications through the notificationBatchCreate API endpoint,
Statuses per each notification can be retrieved with this endpoint.
Conversion, Redemption, and Revenue Tracking
Mobile wallet passes don't change what you care about measuring, they just change the channel. Badge supports conversion goals, which let you connect your own transaction, redemption, or check-in data back to Badge so you can measure the real-world impact of your campaigns.
Once set up, you can track conversions and associated revenue directly in the Badge dashboard alongside your campaign performance, without needing to manually stitch data together.
Common examples include transactions and order value, redemptions, and check-ins. To learn how to set this up, see Setting Up Conversion Goals in Badge.
Additional Data Available Through Pass Scanning
When QR codes or barcodes are scanned by your hardware and processed by your software, you can track the following within your own internal systems:
Member identification
Event check-in
Transaction metadata
Scan location
What We Cannot Track
Because passes operate within Apple and Google's ecosystems, there are a few things that are intentionally not reported back to Badge or any third party:
Pass opens: Apple and Google do not share whether a user opened or viewed their pass in wallet. This is by design to protect user privacy.
Geo-trigger activity: Badge allows you to attach geofences to passes, which can trigger a notification when a user enters a defined area. However, this action happens natively on the device. Apple and Google do not report back which users triggered a geofence or when, so this data is not available in Badge.
Push notification open rates: Whether a user tapped on a push notification is not shared by Apple or Google. You can see how many notifications were sent and delivered, but not opened.
These are platform-level constraints that apply universally, not just to Badge.
If you need help accessing or interpreting any of this data, our team is here to help. Let your Customer Success Manager know, or use the chat bubble in the bottom right corner of any page on the Badge platform.