> 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.md).

# Push notifications

Compare Apple Wallet and Google Wallet push notifications: what triggers them, platform limits, and common use cases for brands using The Wallet Crew.

Wallet notifications help deliver timely information in a familiar channel. Apple Wallet and Google Wallet do not work the same way, so the trigger strategy matters.

<figure><img src="https://2685221786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F97ZAXMtqOjhvBBCfpmcE%2Fuploads%2Fgit-blob-a7a7d46ea05b3e0d0ce8a17b6744325ae9e2dad7%2Fpush-apple-google-notification-diagram-lumen.png?alt=media" alt="Diagram comparing push notifications in Apple Wallet vs Google Wallet"><figcaption></figcaption></figure>

<details>

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

* A loyalty member receives a points update after a purchase.
* A gift card balance is refreshed after an in-store redemption.
* A ticket holder is alerted about a gate change or schedule update.

</details>

## How to send a notification

In the admin console, a notification is one action of an [automation](/guides-animation/engage-and-animate/automatisation.md#send-a-notification): the same message can be sent once, on a date, on a repeating schedule, relative to a date on the pass, or each time an event happens on a pass. The recipe [Send a one-off notification](/guides-animation/engage-and-animate/automatisation.md#send-a-one-off-notification) lists the steps. A notification can also be sent to one pass with **Notify** on the pass page. Integrations use the API: see [Pass lifecycle](/developers-guides/integration-guides/wallet/pass-lifecycle.md).

## Apple Wallet vs Google Wallet

|                 | Apple Wallet                                                                                                        | Google Wallet                                                                                                                                 |
| --------------- | ------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| Trigger         | Only when a pass is updated: a field, QR code or location changes.                                                  | Can notify from a message, without a pass update.                                                                                             |
| Content         | The message appears on the lock screen or in Notification Center. The last message appears on the back of the pass. | Usually alerts the customer that a message was added. The customer opens the pass to read it. The message can also stay in pass details only. |
| Inside the pass | Not supported.                                                                                                      | A title, description, image and clickable link can be added.                                                                                  |

Apple also supports automatic pass presentation based on geolocation, dates, or events.

<figure><img src="https://2685221786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F97ZAXMtqOjhvBBCfpmcE%2Fuploads%2Fgit-blob-b8b48ef81b83b6eac23c9390727437f9cf941d8b%2Fpush-apple-google-notification-comparison-lumen.png?alt=media" alt="Example showing notification content differences between Apple Wallet and Google Wallet"><figcaption></figcaption></figure>

<figure><img src="https://2685221786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F97ZAXMtqOjhvBBCfpmcE%2Fuploads%2Fgit-blob-66f4d2a496d19575671b201a63eb87d1cbcbfb8f%2Fdocumentation-readme-example-google-wallet-value-added-opportunities-image-front-back.png?alt=media" alt="Example of Google Wallet value-added opportunities (image + link)"><figcaption></figcaption></figure>

## Update pass information and trigger alerts

The Wallet Crew manages Apple Wallet and Google Wallet passes through a unified API. Connected CRM, ticketing, and POS systems can update pass data in real time.

Common updates include:

* Remaining gift-card balance.
* Coupon or ticket expiry date.
* Promotional content on a pass.

A pass update synchronizes with Apple Wallet and Google Wallet. Platform rules determine whether it generates a notification.

<figure><img src="https://2685221786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F97ZAXMtqOjhvBBCfpmcE%2Fuploads%2Fgit-blob-dd8dd5ba56717d059382b4a21ca1b27312ff3ab6%2Fpush-pass-update-notification-example-lumen.png?alt=media" alt="Example of a pass update triggering a notification"><figcaption></figcaption></figure>

## Notification types

### Geolocation-based notifications

Apple Wallet uses GPS coordinates to detect when a customer enters or exits a defined area. Google Wallet notifies when the device enters a radius set by Google around one of the pass's locations. This can surface a pass near a store or venue. See [Geolocated notifications](/guides-animation/engage-and-animate/geolocated-notifications.md) for how to set it up.

<figure><img src="https://2685221786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F97ZAXMtqOjhvBBCfpmcE%2Fuploads%2Fgit-blob-7a6c6e05ce8cbef6a196654a5cf98f627059d6aa%2Fpush-location-based-notification-example-lumen.png?alt=media" alt="Example of a location-based notification near a store"><figcaption></figcaption></figure>

### Date- or calendar-based notifications

Brands can configure reminders around pass validity or an event date.

<figure><img src="https://2685221786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F97ZAXMtqOjhvBBCfpmcE%2Fuploads%2Fgit-blob-b0e894b707195d63e1874630c98a3672eddc42fb%2Fpush-scheduled-reminder-notification-example-lumen.png?alt=media" alt="Wallet notification announcing an in-store event, sent on a schedule"><figcaption></figcaption></figure>

### Event-triggered notifications

Connected CRM, POS and ticketing systems can update pass data (purchases, point accrual, cancellations); the update follows the platform rules above.

<figure><img src="https://2685221786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F97ZAXMtqOjhvBBCfpmcE%2Fuploads%2Fgit-blob-29aaaf78ecdc4c42607bb0e6fd78e8e0e02a26fb%2Fpush-event-triggered-notification-example-lumen.png?alt=media" alt="Phone lock screen showing a Wallet notification sent after a purchase, triggered by a connected system"><figcaption></figcaption></figure>

### Beacon tags

Beacon tags use Bluetooth to detect nearby devices. This capability is available only with Apple Wallet.

<figure><img src="https://2685221786-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F97ZAXMtqOjhvBBCfpmcE%2Fuploads%2Fgit-blob-9d43ba86c087832ebc52906136437a77836852ee%2Fdocumentation-readme-bluetooth-beacon-based-notification-example-apple-wallet-lumen.png?alt=media" alt="Bluetooth beacon-based notification example (Apple Wallet)"><figcaption></figcaption></figure>

## Limits

### Apple Wallet

Notifications can appear on the iPhone lock screen, in Notification Center, and on Apple Watch when enabled.

Keep messages to about 120 characters, the length the admin console editors recommend.

Apple Watch usually shows one or two lines.

### Google Wallet

Google Wallet applies the following restrictions:

* Customers must enable pass notifications.
* Message links must relate to the pass.
* A maximum of three messages can trigger a push notification within 24 hours.
* Google Wallet controls the lock-screen notification.

Google may throttle delivery when it detects spam. More information is available in [Google's considerations when sending messages](https://developers.google.com/wallet/retail/offers/use-cases/trigger-push-notifications#some-considerations-when-sending-messages-with-notifications-to-users).

## FAQ

<details>

<summary><strong>Why did a customer not receive a wallet notification?</strong></summary>

Check device settings first. Notifications may be disabled globally or for a specific pass. Then validate the platform trigger, and check the **Notifications** tab of the pass and the history of the automation: see [Check that it worked](/guides-animation/engage-and-animate/automatisation.md#check-that-it-worked).

</details>

<details>

<summary><strong>Should wallet notifications be treated as marketing?</strong></summary>

It depends on the message purpose. Service messages are usually transactional. Promotions are marketing. See [Consents & GDPR compliance](/guides-animation/engage-and-animate/automatisation/push-notifications/consents-and-gdpr-compliance.md).

</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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.thewalletcrew.io/guides-animation/engage-and-animate/automatisation/push-notifications.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.