What Push Campaigns are
A push campaign sends a notification to customers who have added your Wallet Pass. It lands on their lock screen, the same way a message from any app would, so it is a direct way to announce a sale, a points event, or a new reward.
Campaigns are one-off sends. To surface a message automatically when a customer is near a store, use Location Pushes instead (see: Location-Triggered Push Notifications).
Your Wallet Pass must be enabled before you can send campaigns. See: Wallet Pass - Overview & Setup.
Creating a campaign
In the Mage Loyalty app, go to Wallet Pass → Push Campaigns.
Click Create campaign.
Fill in the notification, audience, and schedule (covered below). The preview on the right shows how it will look on Apple and Google.
Click Save.
Notification
Field | Details |
Campaign name (internal) | A label for your own reference. Only you see it, and it is how the campaign shows in your list. |
Push header | The bold title line of the notification. Up to 35 characters. |
Push body | The main message. Up to 150 characters. |
Devices | Send to all devices, Apple only, or Android only. |
The 35 and 150 character limits exist because phones cut off notification text that runs longer. Staying inside them means your full message shows on the lock screen rather than being trimmed with an ellipsis. Keep the header short and punchy, and put the detail in the body.
Audience
Choose who receives the campaign:
All pass holders - everyone who has added your pass.
VIP tier - only pass holders in the tier you pick.
Shopify customer segment - pass holders in a Shopify segment. Enter the segment ID, and optionally a name for your own reference.
Schedule
Set the campaign to send at a specific date and time, or save it as a draft to finish later. Scheduled times use your store's timezone, shown beneath the time picker. A scheduled campaign sends automatically when its time arrives, so there is nothing more to do.
How it appears on Apple and Google
Both platforms show your header and body as a lock-screen notification. There is one difference worth knowing on Google:
Google Wallet limits passes to 3 notifications per pass in any 24 hour period. If you send more than that to the same Android pass holder within a day, the extra notifications are not delivered. Apple has no such cap. This is a Google rule, not a Mage setting, so plan your Android sends with it in mind.
Separately, Mage protects your customers from being over-messaged. Across all your wallet pass notifications (manual campaigns and automated pushes combined), we send at most 3 to any one customer in a rolling 24 hours, and never more than one per hour. This applies to both Apple and Google, on top of Google's own per-pass limit above.
After you send
Your campaign list shows each campaign's status, audience, devices, and schedule. Open a campaign to see how many notifications were sent and any sales attributed to it.
While a campaign is still a draft or scheduled, you can cancel it from the list. Once it has sent, it cannot be recalled, so double-check the preview before the send time.
Common mistakes to avoid
Writing a header or body that reads well in the editor but is longer than the limit allows. The character counter under each field tells you where you stand. If it is full, assume some phones will trim the text.
Sending several campaigns to the same Android audience in one day. Because of Google's 3-per-day limit, later sends may silently not arrive for Android pass holders.
Still need help? Reach out to the Mage Loyalty team through our live chat support.