Delivery reports

Reading a notification's report - how many were targeted, delivered and failed, the Apple and Google split, the per-recipient list, and what resending actually does.

Updated 7/26/2026

Every notification has a report. Open it from the Notifications list.

The numbers at the top

Targeted - how many passes matched your audience when the campaign ran.

Delivered - how many were successfully sent to at least one wallet.

Failed - how many couldn't be delivered.

Delivery rate - delivered as a percentage of targeted, with a bar.

Why delivered is usually lower than targeted

This is the number that surprises people, and it's almost always benign.

The most common reason is that a pass was never installed. If a pass is sitting at issued, there's no device holding it, so there's nothing to deliver to. It counts as targeted but not delivered.

The others: the pass was removed by its holder, or the device is unreachable and hasn't picked the message up.

This gap is expected rather than a fault, and it's the clearest measure of how well your install links are landing. See Choosing an audience.

The Apple and Google split

The report shows how many went to each wallet. Useful for two things: knowing which platform your customers are actually on, and spotting a problem confined to one of them.

A lopsided split is normal and reflects your customer base. A split that suddenly changes shape is worth looking at.

Live progress

While a campaign is sending, the report updates itself. Large audiences are delivered in the background in batches, so the numbers climb rather than appearing all at once.

You can navigate away and come back - nothing depends on you keeping the page open.

The recipient list

Below the summary is a row per pass: which pass, whether Apple and Google each succeeded, and any error.

Every row links to its pass, so you can go straight from a failure to the pass that produced it.

Very large campaigns show the first 250 recipients rather than every one.

Errors

If anything failed, the first few errors are called out above the list. They're usually one of:

  • The pass isn't installed on any device.
  • The device is no longer reachable - typically because the pass was removed.

A handful of these in any campaign is normal and needs no action. A large proportion failing, especially all at once, is worth investigating.

Resending

Finished campaigns offer Resend. It runs the same message again against the audience as it stands now.

Resend is not a retry of the failures. It sends to everyone who currently matches the audience - including everyone who already received it the first time. They'll get the message twice.

If your goal is to reach people who've been added since, that's exactly right. If you're trying to fix a partial failure, resending is usually the wrong tool.

Resending clears the previous report and starts a fresh one, so you lose the old numbers.

Cancelling

A campaign still in scheduled can be cancelled from its report page. Once sending has begun it can't be stopped. See Scheduling notifications.

What the report doesn't tell you

It shows delivery, not attention. There's no open rate and no read receipt - a wallet notification has no equivalent, because there's nothing to click and no pixel to load.

Judge notifications by what happens next - redemptions, bookings, visits - rather than by anything on this page. Delivery is the floor, not the outcome.

Watch your pass removal numbers alongside your campaigns. A rise in removals after a send is the clearest signal you're messaging too often or not usefully enough - and it's a signal no delivery report will give you directly.

Where to go next

More in Notifications