> 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: triggers, limits, and common use cases with 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. *Apple Wallet notifications require a pass update. Google Wallet can notify from a message.*
Real-world examples
* 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.
## How push notifications work
### Apple Wallet
Apple Wallet notifications are triggered only when a pass is updated. A field, QR code, or location can change. Notifications appear on the lock screen or in Notification Center. The last message appears on the back of the pass.
Apple also supports automatic pass presentation based on geolocation, dates, or events.
### Google Wallet
Google Wallet can send notifications without a pass update. The notification alerts the customer that a message was added to the pass.
Google Wallet can show the message in pass details only. It can also display the message and generate a notification.
## 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.
## Notification types
### Geolocation-based notifications
Apple Wallet uses GPS coordinates to detect when a customer enters or exits a defined area. Google Wallet relies on location information associated with the Google account. This can surface a pass near a store or venue.
### Date- or calendar-based notifications
Brands can configure reminders around pass validity or an event date.
### Event-triggered notifications
The Wallet Crew can react to events from CRM, POS, and ticketing systems. Purchases, point accrual, or cancellations can update a pass and trigger a notification.
### Beacon tags
Beacon tags use Bluetooth to detect nearby devices. This capability is available only with Apple Wallet.
## Limits
### Apple Wallet
Notifications can appear on the iPhone lock screen, in Notification Center, and on Apple Watch when enabled.
As of iOS 18, up to three lines are displayed. Keep messages below 140 characters to reduce truncation. 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).
## Key differences
### Notification triggering
Apple Wallet requires a pass update. Google Wallet can notify from a message, independently of a pass update.
### Notification content
Apple Wallet can display message content on the lock screen. Google Wallet usually alerts customers that a message was added. Customers then open the pass to read it.
### Value-added opportunities
Google Wallet can add a title, description, image, and clickable link inside the pass. Apple Wallet does not support this interaction model.
## The Wallet Crew unified API
The Wallet Crew centralizes pass updates for both platforms. This creates consistent business logic while respecting each wallet's delivery rules.
## FAQ
Can notification text be customized on Google Wallet?
Not in the same way as Apple Wallet. Google Wallet usually alerts customers that a message was added. They then open the pass to read the content.
Why did a customer not receive a wallet notification?
Check device settings first. Notifications may be disabled globally or for a specific pass. Then validate the platform trigger.
What are the Google Wallet sending limits?
Google Wallet limits push-triggering messages to three per 24-hour period for each pass.
Should wallet notifications be treated as marketing?
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).
---
# 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.md?ask=&goal=
```
`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.