> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/guides-animation/engage-and-animate/automatisation/push-notifications/how-to-send-push-notifications-to-apple-and-google-wallet.md).

# How to Send Push Notifications to Apple and Google Wallet

Create and schedule Apple Wallet and Google Wallet push notifications, target pass holders, configure messages, and verify delivery.

## Send push notifications to Apple Wallet and Google Wallet

The Wallet Crew sends wallet notifications to Apple Wallet and Google Wallet pass holders. Use an automation to send a message immediately, on a schedule, after an event, or relative to a pass date.

Apple Wallet displays the configured message on the lock screen. Google Wallet controls the lock-screen notification text. It generally tells customers that a new pass message is available.

<details>

<summary><strong>Real-world examples</strong></summary>

* A ticketing platform sends gate details one hour before an event.
* A retailer reminds loyalty members that an offer expires tomorrow.
* A gift-card program confirms a balance update after redemption.

</details>

## Create a push notification automation

This automation combines timing, audience, message, and delivery speed. Configure each setting before saving the notification.

### Open the notification workflow

Open **Engagement** and select **Add a new one** in the top-right corner.

Select **Send a notification**, then select **Next**.

<figure><img src="https://2685221786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F97ZAXMtqOjhvBBCfpmcE%2Fuploads%2Ffs1F7nh5M3O8YMZxeCHF%2FCapture%20d%E2%80%99e%CC%81cran%202026-08-06%20a%CC%80%2017.30.28.png?alt=media&amp;token=b77cde39-e386-4ec9-b3b8-088e2b9306b8" alt="Engagement page showing the Add a new one button"><figcaption><p>Start a new automation from the Engagement section.</p></figcaption></figure>

<figure><img src="https://2685221786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F97ZAXMtqOjhvBBCfpmcE%2Fuploads%2FJl1D4kh93s6SEYfE1HiP%2FCapture%20d%E2%80%99e%CC%81cran%202026-08-06%20a%CC%80%2017.30.39.png?alt=media&amp;token=64df9e4e-165e-4ea6-8ad2-602544ebea8c" alt="Automation type selector with Send a notification selected"><figcaption><p>Select Send a notification to create a wallet notification automation.</p></figcaption></figure>

### Set the delivery time

Name the notification and choose its delivery time. The name identifies the automation internally.

Choose one of the following delivery options:

* **Now** sends the notification immediately after configuration is complete.
* **Scheduled** sends the notification on a selected date and time.
* **Recurrence** repeats delivery daily, weekly, or monthly.
* **Date relative** uses a **DateTime** metadata field. Set an offset before or after that date.
* **Event** runs after a selected event occurrence. Run it per pass or only after first installation. A delay can be added.

<figure><img src="https://2685221786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F97ZAXMtqOjhvBBCfpmcE%2Fuploads%2F6h5ynNF1pt46rGlChNkX%2FCapture%20d%E2%80%99e%CC%81cran%202026-08-06%20a%CC%80%2017.30.43.png?alt=media&amp;token=5640cc5e-7872-4521-9c6e-9c2d56b04480" alt="Notification delivery-time options in the automation editor"><figcaption><p>Choose immediate, scheduled, recurring, date-relative, or event-based delivery.</p></figcaption></figure>

Select **Next** after setting the name and delivery time.

### Target the audience

Filters define which installed passes receive the notification. Select **Estimate** to check the number of targeted passes before sending.

Select **Add filter** to narrow the audience by:

* **Installation status** — target installed passes, Apple Wallet passes, or Google Wallet passes.
* **Template** — target a selected pass template.
* **Metadata** or **Identifiers** — target a specific data value or identifier.

Multiple filters always use an **AND** rule. Every selected condition must match. This rule cannot be changed.

<figure><img src="https://2685221786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F97ZAXMtqOjhvBBCfpmcE%2Fuploads%2FYrkcthIJtKuKIRLE0n1u%2FCapture%20d%E2%80%99e%CC%81cran%202026-08-07%20a%CC%80%2010.29.46.png?alt=media&amp;token=82c616dc-eb7b-4830-bcd0-400e208d71d2" alt="Audience filter builder for a notification automation"><figcaption><p>Use filters to define the pass holders who receive the notification.</p></figcaption></figure>

### Write the notification message

Configure the Apple Wallet message. It appears on the lock screen when Apple Wallet sends the notification.

On Google Wallet, Google controls the notification text. The Wallet app notifies customers that a new message is available.

For multilingual passes, enable **translations**. Then select each language on the right to configure its message.

<figure><img src="https://2685221786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F97ZAXMtqOjhvBBCfpmcE%2Fuploads%2Fesbl0tYJ7UkzvU9qnPDK%2FCapture%20d%E2%80%99e%CC%81cran%202026-08-07%20a%CC%80%2011.21.07.png?alt=media&amp;token=3a0b7d07-a8a3-4780-9423-85aff95cd066" alt="Translation toggle in the notification message editor"><figcaption><p>Enable translations to configure a message for each supported pass language.</p></figcaption></figure>

<figure><img src="https://2685221786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F97ZAXMtqOjhvBBCfpmcE%2Fuploads%2FyFYMMNKd50BPi7vEBRez%2FCapture%20d%E2%80%99e%CC%81cran%202026-08-07%20a%CC%80%2014.43.26.png?alt=media&amp;token=f0d31f10-7097-4576-966f-f1c98ffa50c6" alt="Language selector in the notification message editor"><figcaption><p>Select a language to edit its localized notification message.</p></figcaption></figure>

Use the preview in the top-right corner to check the Apple Wallet and Google Wallet experience.

Notifications remain visible for seven days by default. During that period, recipients can view them on the back of the pass.

To change this duration, open **Wallet → Template → Editing → General → Advanced configuration**. Then update the notification duration.

### Configure delivery throughput

The default throughput suits most notifications. Increase it only when delivery must complete before a fixed time.

For example, set a suitable throughput before sending event access details. This helps deliver notifications before doors open.

Select **Next** to review the summary. Save the automation after confirming the audience and settings.

## Verify notification delivery

Use the pass-level notification timeline to confirm delivery and investigate reports of missing notifications. Open **Wallet → Passes → \[select a pass] → Notifications**.

The tab shows a full timeline of notifications sent to that pass, including:

* The timestamp and delivery status.
* The target platform: Apple Wallet or Google Wallet.
* The sent message and localized variants, such as `FR-FR`.

{% hint style="info" %}
Synchronization may take up to five minutes. The notification then appears in the **Notifications** tab.
{% endhint %}

## FAQ

<details>

<summary><strong>Can the same notification target Apple Wallet and Google Wallet?</strong></summary>

Yes. Installation-status filters can target Apple Wallet, Google Wallet, or both. The platforms handle lock-screen content differently.

</details>

<details>

<summary><strong>Why is the Google Wallet lock-screen text different?</strong></summary>

Google Wallet controls the notification text. It alerts customers that a new pass message is available. The message content is available in the pass.

</details>

<details>

<summary><strong>How can delivery be checked for one customer?</strong></summary>

Open the pass and select **Notifications**. The timeline shows the send time, delivery status, platform, and message content. Allow up to five minutes for synchronization.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.thewalletcrew.io/guides-animation/engage-and-animate/automatisation/push-notifications/how-to-send-push-notifications-to-apple-and-google-wallet.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.