> ## Documentation Index
> Fetch the complete documentation index at: https://vexioncards.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Delivery & history

> Where notifications go, how to read the delivery stats, and the full history of what you sent.

Every notification you send is tracked. The **History** list below the composer shows everything sent, and each one opens a detailed delivery breakdown.

## Who receives a notification

A push can only reach a customer who has **installed** the card (in a wallet or as a web card). Notifications are delivered across three channels, depending on the customer's device:

* **Apple Wallet** (iPhone).
* **Google Wallet** (Android).
* **Web card** (browser) pushes, shown as **FCM** in the **By Platform** list.

A customer who was sent a card but never added it to their wallet cannot be reached until they do.

## The history list

Each row shows:

| Column | What it means |
| - | - |
| **Message** | The text you sent (with the First Name chip shown where you personalised it). |
| **Status** | **Scheduled** (waiting for its send time), **Pending** (currently sending), **Delivered**, or **Failed**. |
| **Delivered** | How many reached customers out of the total (for example "45/49"). |
| **Sent at** | When it went out, or, for a scheduled message, when it is due. |

Two actions sit on each row: a **stats** icon (the delivery breakdown below) and a **delete** icon to remove it from history. A **refresh** button at the top reloads the list, and a just-sent message updates live as it delivers.

![The Notifications page History list: one delivered notification showing its message, a green Delivered status, a 29/32 delivered count, and how long ago it was sent, with stats and delete actions on the row.](https://mintcdn.com/vexioncards/jyoFo5IjMFdGfJql/images/notification-history.png?fit=max\&auto=format\&n=jyoFo5IjMFdGfJql\&q=85\&s=53e070b7f3a85571735ef2a5799f0c72)

Notification history

## Delivery statistics

Open a notification's **stats** to see exactly how it went out. The **Overall** row counts:

* **Total**: how many customers it targeted.
* **Delivered**: successfully reached.
* **Sent**: handed to Apple's servers (Apple Wallet only, an in-between step before Delivered).
* **Queued**: still waiting to go out.
* **Failed**: could not be delivered (for example the customer removed the card).

A colour bar visualises the split, and a **By Platform** breakdown repeats the same numbers separately for **Apple Wallet**, **Google Wallet**, and **FCM**, so you can see how each device type performed.

![The Delivery Statistics dialog: an Overall grid of Total 32, Delivered 29, Sent 0, Queued 0, Failed 3 with a colour split bar, then a By Platform breakdown for Apple Wallet (20 total, 17 delivered, 3 failed) and Google Wallet (12 total, 12 delivered).](https://mintcdn.com/vexioncards/jyoFo5IjMFdGfJql/images/notification-delivery-stats.png?fit=max\&auto=format\&n=jyoFo5IjMFdGfJql\&q=85\&s=a108f725b783571aadcb0309c30a6ef5)

Delivery statistics for one notification

> [!NOTE]
>
> A few **Failed** deliveries are normal, they are usually customers who deleted the pass from their wallet. A high failure rate on one platform is worth a closer look.

## Scheduled notifications

A [scheduled](https://vexioncards.mintlify.site/knowledge-base/sending-a-notification.md) message sits in the history with a **Scheduled** badge and its future send time until it goes out, then it delivers like any other. To cancel one before it sends, delete it from the history.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.