Message Wallet pass holders

Once a user adds your pass, Pushwoosh registers it as a platform subscription (Apple Wallet or Google Wallet) tied to that User ID.

You can reach holders in several ways: send a pass update, send a one-time push, automate messages from a Customer Journey, or notify holders of a specific pass via API.

Send a pass update

Editing a pass and saving pushes the new version to every device that added it, without a separate message. The way you alert holders about the change differs by platform.

Apple Wallet

Set a Change message on any field you want holders alerted about; iOS shows it as a lock-screen message. Fields without a change message update silently.

1. In Campaigns → Wallet Passes → Apple Wallet, find the pass and click Edit in the actions menu.
2. Change the fields you need, and add a change message to any field you want holders to be alerted about.
3. Click Save.

Google Wallet

For loyalty, event ticket, and flight passes, enable Notify about changed fields to have Google send an Android notification alongside the sync. Other pass types sync silently.

1. In Campaigns → Wallet Passes → Google Wallet, find the pass and click Edit in the actions menu.
2. Change the fields you need.
3. Make sure Notify about changed fields is enabled.
4. Click Save changes.

Event and flight passes

• Google generates the notification text; you can’t customize it like an Apple Wallet change message.
• For event and flight passes, the notification only fires if fewer than 3 hours remain until the start time.
• Google allows at most 3 notifications per pass per 24 hours. If the limit is reached, the pass updates silently.

Send a one-time push to pass holders

Send a standalone push to one pass holder or to a wider audience. It appears as a lock-screen message on an Apple Wallet pass, or a notification on a Google Wallet pass.

1. Open the one-time push composer. Either click Send message in Campaigns → Wallet Passes → Apple Wallet or Google Wallet, or go to Campaigns → One-Time Messages and click Send message → One-time push.

2. On the Content step, write the message or select a preset.

3. On the Audience step, set who receives the message. The default depends on where you opened the composer:

   • From Send message on a pass: Send to specific users is selected, and Recipients (User IDs) already lists that pass holder’s User ID. Send as is to reach that one holder, or change the audience:
     • Add more User IDs in Recipients (User IDs)
     • Switch to Send to segment
     • Choose Send to all subscribers
   • From One-Time Messages: Set the audience as in a regular one-time push: Send to specific users, Send to segment, or Send to all subscribers.

4. Under Target platforms, select Apple Wallet, Google Wallet, or both.
5. Send or schedule the message.

注意

When you target a segment, delivery goes to users in that segment who have the matching platform registered, not to everyone who saved a specific pass.

Automate messages from a Customer Journey

Send messages automatically based on events or segments.

Trigger-based entry journey

Developer assistance needed

Sending custom events requires your developer team to integrate the postEvent API call into your backend or CRM. Share this section with them.

1. Create a Customer Journey and add a Trigger-based entry.
2. Select the event that should start the Journey. Create a custom event in the Control Panel first if you haven’t already, for example RewardAvailable.
3. Add and configure a push element. Enable Send by User ID so the push reaches every device tied to the user, including the saved pass.
4. Finish configuring and activate the Journey.

When the entry event fires, Pushwoosh sends the push to every device tied to the user. Pass holders receive it as a lock-screen message on Apple Wallet, or a notification on Google Wallet. Users without a wallet pass receive it on their other devices.

Pass content

The push does not change any pass fields. To update pass content alongside the message, for example a points balance, update the pass separately:

• Apple Wallet: via Edit in All passes, or through the Apple PassKit API.
• Google Wallet: via Edit in All passes, or through the Google Wallet API.

Example: Notify a user that a reward is available

POST https://api.pushwoosh.com/json/1.3/postEvent

{
  "request": {
    "application": "XXXXX-XXXXX",
    "userId": "u12345",
    "event": "RewardAvailable",
    "attributes": {
      "reward": "Free coffee",
      "expires": "2026-07-01"
    }
  }
}

The event name must match an event created in your Control Panel.

Other ways to build the journey

The trigger-based flow above is one option. Depending on what should start the journey, choose a different entry element:

• Audience-based entry: start the journey for a whole segment instead of a single event. Run it once, on a schedule, or periodically (for example, every week to everyone holding an active pass), with new users entering as they join the segment.
• API-based entry: start the journey from a business event that happens outside the app, such as a flight delay or gate change. Your external system calls the entry element’s request template and passes a filter to target the right users, for example everyone who has a tag flightNumber = SU1234 set when the pass was issued. A good fit for boarding passes and event tickets.

Notify holders of a specific pass via API

To message everyone who saved one specific pass, call Update a pass. It updates the pass and notifies devices. On Google Wallet, set notifyMessage to send a custom notification alongside the update; without it, the pass syncs silently.

• Apple Wallet:
  Update a pass
• Google Wallet:
  Update a pass