Trends · A practical loyalty guide

Boomerangme Push Delivery: Installation and Device Limits to Check

A sent message is not necessarily displayed. Installation status, wallet settings, browser support and device limits affect delivery.

Independent affiliate journal. We may earn a commission if you subscribe through our links. How we research and fund the guides.

Original editorial checklist illustration for Boomerangme Push Delivery: Installation and Device Limits to Check.

Editorial illustration: Boomerangme Partner Journal / original editorial illustration. Image credits.

Quick answer

Boomerangme’s troubleshooting page says only installed cards can receive pushes and lists wallet settings, automatic updates and browser support as common blockers. It also documents a Google limit of three push notifications displayed per day.

Distinguish sent, eligible and displayed

A campaign can be sent from the dashboard while a customer is not eligible because the card is not installed. Even an installed card can have notifications or automatic updates disabled. A delivery report should not be interpreted as proof that a person saw the message.

The official troubleshooting page separates Apple Wallet, Google Wallet and Android PWA conditions. This October 23, 2026 product watch records the current guidance; it does not claim those platform limits began on this date.

Test the device combinations you advertise

Use staff devices with Apple Wallet, Google Wallet and the PWA route you actually offer. Turn notification settings off and on, check card status, and observe what the user can control. The documentation recommends Chrome where browser notifications are involved because support is not universal.

Do not tell customers that installing a card guarantees every alert. Explain how to check settings and provide an important-message alternative for operational notices that must reach them. Marketing push is not a substitute for an order, safety or appointment channel.

Respect frequency before the platform enforces it

The documented Google display limit makes message competition visible, but the better reason to cap frequency is customer usefulness. Coordinate automated birthday, feedback and visit reminders so several workflows do not fire on the same day.

Track sends, eligible installed cards, known failures and downstream actions separately. A click or visit after a message is evidence of action, not proof that every recipient read it.

A practical pilot

Create test profiles for not-installed, installed with notifications on, notifications off, automatic updates off and PWA in supported and unsupported browsers. Send one harmless test, record the result and update the help script for staff.

Use a staff test account first. Save the transaction or booking reference, the rule applied, the resulting customer balance and the person who made any correction. Review edge cases before inviting the public. A loyalty card is the customer-facing record of an offer; it does not replace the booking, payment, inventory or accounting system that proves what happened.

Boomerangme documents digital stamp cards and reward cards. You can explore Boomerangme to compare those mechanics with this workflow. This independent journal does not imply a native integration with the businesses or systems cited here. Verify the current settings in your own account and keep the primary operational record in the system that owns it.

What to record and review

For “Boomerangme Push Delivery: Installation and Device Limits to Check,” keep a compact decision log beside the operating system that proves the transaction. Record the customer-facing rule version, qualifying reference, date, location or channel, value added or removed, staff user and exception reason. Do not copy sensitive operational notes into a public-facing wallet pass. Review a small sample weekly during the pilot: one ordinary earning event, one redemption, one correction and one case that did not qualify. Compare the saved record with what the customer can see. This is especially important for the trends workflow described here, because a card balance alone cannot explain a booking state, refund, product exclusion or staff override. If the same exception appears twice, improve the written rule or checkout process instead of relying on memory.

Quick questions

Does “sent” mean the customer saw the push?

No. Installation status, device settings, browser support and platform behavior can prevent display.

How many Google push notifications are displayed per day?

Boomerangme’s current troubleshooting page documents a limit of three displayed notifications per day. Recheck current guidance.

Should push replace appointment reminders?

Use the channel appropriate to the operational need and consent. Marketing wallet pushes may not reach every customer.

Sources & further reading

  1. Why aren’t my customers receiving push messages?Primary troubleshooting documentation checked October 23, 2026.
  2. Push automationPrimary documentation for automatic push events; checked October 23, 2026.
  3. Apple Wallet overviewApple primary overview for wallet passes and updates; checked October 23, 2026.

Sources reviewed .

Numerical examples are illustrative unless a cited source states otherwise.

Put the ideas into practice

Your next loyal customer could already be in your business.

Explore Boomerangme’s digital wallet cards and engagement tools. See the current features, plans, and sign-up options on the official website.

Explore Boomerang Me