How often should you send notifications?
On this page
Three or four a month is enough for most small businesses, with offers no more than once a week and some weeks nothing at all. Send a notification only when a member can use what it says, or when it changes their plans. You are allowed far more, up to three to each card every 24 hours. Members will put up with much less.
The daily limit
Each card takes three notifications in any 24 hours. A fourth is held back and is not sent later.
Google's documentation for businesses that issue cards into Google Wallet says: "You may send a maximum of 3 messages that trigger a push notification in a 24 hour period."
Every card issued through native.cards has the same limit, on Apple Wallet and on Google Wallet: three notifications in any 24 hours. A fourth is held back. It is not sent later, and the Notifications page counts it under Held back.
Three a day would be about ninety a month, which no shop intends. The limit matters on an ordinary busy day. A member who joined last week, has a reward waiting and agreed to offers is in every audience you can choose. If your welcome, your reward reminder and your Saturday offer all go out one morning, that member has had three. The notice you write at noon to say the outlet is closing early will not reach them. Keep scheduled notifications on different days, and leave room for the one you did not plan.
Cost will not hold you back either: Zero notification fees. The restraint has to come from you.
Why people switch off
Asked in a US survey about apps, people said they switch off senders who notify too often.
% of adults asked, when an app sends too often
- Change its settings
- 42%
- Turn its notifications off entirely
- 39%
- Delete it
- 8%
The best public evidence is a survey, and it is American. In June 2021 YouGov asked 1,167 adults in the United States about notifications on their phones. Nearly half, 47%, said they get too many. When an app sends too often, 42% said they change its settings, 39% said they turn its notifications off entirely and 8% said they delete it.
Promotions were the least welcome kind. A few a week seemed appropriate to 19%, once a week to 18% and less often than that to 17%. Only 6% thought more than one a day was reasonable. For comparison, 62% were content to get personal messages several times a day.
That is what Americans told a pollster about apps in 2021. It does not measure what Malaysians do with a Wallet Card. What carries over is the pattern. A message from a brand gets far less patience than one from a person, and the usual answer to too many is to switch the sender off.
Airship sells the software that apps use to send notifications, so its figures are a vendor's, and they are about apps. Its 2026 benchmark covers more than 3 billion app users, and its own consumer survey gives the top reason people opt out as messages sent "too frequently".
We found no sound evidence on which kinds of notification a shop's own members value, or on the best hour or day to send. Advice that names ten o'clock on a Tuesday is one company's data about its own customers, or a guess. The rest of this Article is judgement, and is offered as that.
Two off switches
A member can turn off offers, which you can see, or silence your card in their Wallet, which you cannot.
The first you can see. In their membership on your Business page, under Your choices here, a member can turn off Offers on my Wallet Card. Offers stop. A notice that a reward is ready, or that you are closed on Monday, still reaches them. On your side the Agreed to offers figure falls by one.
The second is in their Wallet, where a member can turn notifications off for your card. After that nothing from you alerts them, including the notice that a free drink is waiting. You are not told. Delivered on the Notifications page means, in its own words, "Google accepted the notification, or Apple accepted the iPhone card update that carries it", so a card that has been silenced still counts.
An unwanted notification can therefore cost more than being ignored. It may be the last one that member's phone shows from you, and your figures will look the same the next morning.
Two tests, four kinds
Send what a member can use or what changes their plans, and offers no more than once a week.
notifications to one member in a month
- Two offers, news and a reminder
- four
- What the limit would have allowed
- about ninety
A notification is worth sending if it passes one of two tests.
The member can use it. A reward that is already theirs. A benefit that comes with membership and may have been forgotten. An offer, if they agreed to offers, that says what it is, when it applies and how to get it.
It changes their plans. You are closed for the public holiday. Hours are shorter during Ramadan. The outlet has shifted two doors down.
A greeting with nothing attached passes neither test. Nor does last week's offer sent again, or news about you that changes nothing for them: an anniversary matters to a member only if something comes with it.
The composer's What is it about? has four answers. Five notifications worth sending to your members works through an example of each kind.
| What is it about? | What belongs under it | How often |
|---|---|---|
| Something they can use | A reward or benefit the member already holds | Every two to four weeks, to members holding one at the time |
| About their membership | A welcome, or a change to their own membership | A welcome in a member's first 30 days. You send it, and on repeat the same member gets it more than once. After that, only when something changes |
| News about your business | "Opening hours, a closure, a new outlet." | When it happens |
| An offer or promotion | A deal or a price, sent to bring in a sale | At most one a week; for most small businesses, one or two a month |
Only an offer needs the member's agreement: the composer says it "Only reaches members who agreed to offers." The other three reach every card holder in the audience you choose.
Once a week is the most often we would send offers. In the survey above, a few a week suited fewer than one person in five. Add it up for one member: two offers, one piece of news and one reward reminder make four notifications in a month. The limit would have allowed about ninety.
There are three audiences and no others: Everyone, New members ("Joined in the last 30 days.") and Members with a reward waiting. You cannot send to regulars only, or only to people who have stopped coming. So anything sent to Everyone has to read well to your most loyal customer and to your most distant one.
Who it really reaches
An offer reaches only card holders who agreed to offers. Do not file it as news to reach the rest.
An example with made-up numbers. A bakery has 600 members. Of those, 520 have its card in a Wallet. Of the 520, 310 agreed to offers and 45 hold a reward they have not used.
| The bakery sends | It can reach |
|---|---|
| News that it is closed on Monday, to Everyone | 520 |
| A weekend offer, to Everyone | 310 |
| A reminder, to Members with a reward waiting | 45 |
The offer reaches just over half of the 600 members. The composer shows the same sum for your own program before you send: how many members match, how many have your card and, for an offer, how many agreed to offers. If your program was set up without marketing wording, members were never asked, and an offer reaches no one.
It is tempting to file the offer as news so that it reaches all 520. Do not. The other 210 did not agree to offers. A member who declined offers and gets one anyway has every reason to turn off notifications for your card in their Wallet. New wording is also checked by native.cards before it goes out.
Complete without a link
No web address is allowed, so the headline and message must say everything, including what to do next.
Neither the Headline nor the Message may contain a web address, so a notification has to be complete in itself. The headline takes up to 80 characters and is, as the composer puts it, "The line they see first, on the lock screen." Write it so that a member who reads nothing else knows whether it concerns them. The message takes up to 500 characters. It should say what to do next, which is usually to show the card at the counter.
Tapping it opens sets where a tap leads: Your business page, One reward or benefit, Their recent activity or Nothing. Keep it on the card for sets how long it stays on the card: 1, 3, 7, 14 or 30 days. Match that to how long the words stay true. An offer for Saturday should not be sitting in a Wallet on Wednesday.
The wording check happens once for each wording. Approved wording can be chosen again and "can go out without waiting for a person to review it", so a reminder you send every month waits only the first time. Check the day and the date before you submit. Once the Wallets accept a notification it cannot be recalled, and a correction is one more notification to the same members.
On timing there is only common sense: send when the member could act on it. A kopitiam's breakfast set is no use at three in the afternoon, and nothing is welcome at midnight.
Do this next
Plan a month on one page, then read what came back
List every notification you mean to send in the next four weeks. Beside each, write who gets it, which of the two tests it passes and how many days it stays true. Cross out any that passes neither. If more than one offer a week is left, cut again. Then open Notifications, read Have your card and Agreed to offers, and write beside each line the number it can really reach.
A week after each one goes out, read Came in, 7 days. It shows the members who visited within seven days of receiving the notification, beside the same members' visits the week before. A payday week or a school holiday moves it too, so compare several before trusting one (How to test whether your program makes a difference explains why). And watch Agreed to offers from month to month. If it falls after a run of offers, members are turning your offers off. Those are the ones you can see.
Sources 3
- YouGov, “How consumers feel about push notifications in 2021” (survey of 1,167 adults in the United States, 3 June 2021) yougov.com
- Airship, “Mobile App Push Notification Benchmarks for 2026” (a vendor's figures about apps; read 10 October 2026) airship.com
- Google Wallet developer documentation, “Trigger Push Notifications” (read 10 October 2026) developers.google.com
Written by native.cards, . Found a mistake? The publishing policy says how to tell us.