Passmint
TemplatesDocsPricingBlog
Log inGet started
Passmint

Apple and Google Wallet passes from one API. Built for people who ship.

Product
  • Pass Designer
  • Developers
  • Distribution
  • Analytics
  • Templates
  • Pricing
Developers
  • Documentation
  • API reference
  • Node SDK
  • Webhooks
Company
  • Changelog
  • About
  • Contact
  • Support
  • Security
  • Terms
  • Privacy
Social
  • GitHub
  • X

© 2026 Passmint. Built for indie makers.

Apple Wallet & Google Wallet, one API.

Distribution & analytics

Update delivery rate & time-to-install

Updated June 29, 2026

Two metrics tell you how well your passes are working after they're out in the world: how reliably updates reach phones, and how quickly people install. Both are useful, and both have limits worth knowing.

Update delivery rate

When you update a pass, Passmint pushes the change to installed devices and records when each update is delivered. The delivery rate is delivered against pushed.

A high rate means your updates are reaching people promptly. A rate below 100% isn't necessarily a problem:

  • A phone that's offline receives the update later, once it reconnects, so a recent push may simply not be delivered yet.
  • A pass that was removed can't receive an update at all.
  • Battery and background limits on a device can delay when Wallet fetches the new version.

Because of this, read delivery rate over a window rather than minute to minute. A freshly sent batch will show a lower rate that climbs as phones come back online.

Time to install

This measures the gap between issuing a pass and someone adding it to their wallet, reported as a typical time and a slower-end figure. It tells you whether your distribution lands in the right moment:

  • Short times mean people install almost as soon as they get the link, which is what you want.
  • Long times mean passes are sitting unopened, a sign to revisit when and how you send them.

The limits of both

Neither metric can see what it can't measure. Time to install only counts passes people actually added, so it says nothing about those never opened (look to the funnel for that). Delivery rate reflects device conditions you don't control.

Treat these as trends, not targets. A rate that holds steady or improves over weeks is a healthier signal than any single day's number.

Related articles

Understanding your distribution dashboardWhat the stat cards, sparklines, and template ranking are telling you.The install funnel explainedThe stages a pass moves through, from issued to active to removed.

On this page

  • Update delivery rate
  • Time to install
  • The limits of both