Push Notifications Strategy for Apps and Websites

By Grocito14 October 2026

A good push notifications strategy sends the right message, to the right person, at a moment when it is useful, and nothing more. Ask for permission after the user has seen value, separate essential alerts from promotions, segment by behaviour, respect time zones and quiet hours, give people control, and measure opt-outs as carefully as taps. Overuse is the fastest way to lose both subscribers and installs.

Key takeaways

Ask for permission at a moment of clear value, with a short explanation first, not on first launch.
Transactional, behavioural and promotional messages deserve different rules, timing and opt-out options.
Segmentation and relevance matter more than volume. Fewer, better messages beat frequent generic ones.
Give users control through a preference centre, and honour opt-outs immediately.
Track opt-out and uninstall signals alongside taps and conversions, or you will optimise for short-term clicks at the cost of long-term trust.

What are push notifications?

Push notifications are short messages sent to a user's device by an app or a website, even when it is not open. There are two main forms:

Mobile app push: delivered through the operating system's notification service to an installed app.
Web push: delivered by a browser to people who have allowed notifications from a site, including on desktop. Support and behaviour differ between browsers and operating systems, so check the current position for your audience. Our guide to progressive web apps explains where web push fits in.

Both rely on the user granting permission and can be switched off at any time.

When should you ask for notification permission?

Permission is the foundation of the whole strategy. On many platforms, if a user denies the system prompt, you cannot easily ask again, so the prompt is a precious moment.

Value first

Do not trigger the system prompt as soon as the app opens. A refusal may be permanent. Wait until the person has done something that makes the benefit obvious, such as placing an order, booking an appointment or saving a search.

The soft ask

Show your own message first, explaining in a sentence what they will receive and why it helps, for example "Get an alert when your delivery is on its way". Only show the system prompt if they agree. If they decline your soft ask, you lose nothing and can try again at another relevant moment.

Be specific

"Stay updated" is vague. "Tell me when my order ships" is concrete.

Which types of notification should you send?

Transactional. Triggered by something the user did or something that affects them: order confirmation, delivery updates, booking reminders, security alerts, payment receipts. Expected and valued. These can usually be sent with less restraint, though still carefully.
Behavioural. Triggered by what the user did or did not do: a reminder about an abandoned basket, a nudge to finish setting up, a prompt after a period of inactivity. These need caution, because they can feel intrusive.
Promotional. Offers, new features, campaigns and content. These are the most likely to cause opt-outs and should be the most carefully targeted and limited.

Treat these as separate categories so that users can switch off promotions but keep order updates. For the retail side of behavioural messages, see our article on abandoned cart recovery.

How do you segment and personalise?

Personalisation is not only inserting a first name. It means relevance:

By behaviour: what the person has viewed, bought, saved or ignored.
By lifecycle stage: new user, active, at risk of leaving, returning.
By preference: topics or categories they chose.
By status: a customer with an open order needs different messages from someone who has never bought.

Start with a few segments you can manage and check the data behind them. Promoting something the user just returned damages trust faster than a generic message.

What is the right timing and frequency?

There is no universal number. The right frequency is the one at which users stay subscribed and still find the messages useful.

Set a cap on promotional messages per person per week, and apply it across all campaigns, so that different teams do not stack messages on the same user.
Use local time. A message that arrives at an unsociable hour in the recipient's time zone will annoy them, however good the offer.
Quiet hours: define a window, such as night time, when only truly urgent notifications such as security alerts are allowed.
Trigger on relevance, not on your schedule. A reminder an hour before an appointment is useful; a generic blast at a random time is not.

How do you write a good push notification?

Space is limited, and what shows on a lock screen is shorter still.

Put the useful part first. Assume only the first few words will be read.
Say what happened or what the user can do, in plain language.
Include a clear next step when there is one.
Avoid shouting, excessive punctuation and manufactured urgency.
Keep the tone in line with your brand.
Never imply something that is not true, such as a limited stock level you cannot back up.

Deep links

Take people straight to the relevant screen or page, not the home page. A delivery alert should open the tracking view, and an appointment reminder should open the booking. Make sure deep links work when the app is closed, when the user is logged out and when the app is not installed, with a sensible fallback in each case.

How do preference centres and opt-outs work?

Give users real control and make it easy to find.

Offer categories, such as order updates, offers, and account alerts, with separate switches.
Let people choose frequency or quiet hours if your product allows it.
Make it clear how to turn notifications off from within the app, not just in the device settings.
Honour opt-outs immediately and do not reintroduce a user through another route.

A person who cannot reduce notifications will usually turn them all off or uninstall.

Privacy, consent and platform rules

Notifications involve device identifiers and often behavioural data. Rules on consent, data use and marketing messages vary by country and sector and change over time, so ask a qualified professional what applies to you. In general terms:

Explain what you collect and why, in a privacy notice that is easy to read.
Obtain consent where it is required, and keep a record of it.
Do not send sensitive information on a lock screen where others might see it.
Follow the guidelines of each app store and browser for notifications, including rules on what messages may contain and how permission must be requested. Our mobile app launch checklist covers store requirements more generally.

How do you measure whether notifications work?

Track the whole funnel, not just taps.

Delivery: how many notifications actually reached devices, and how many failed.
Opens or taps: how many people engaged with them.
Conversion: whether the intended action happened, such as a purchase, a booking or a completed task.
Opt-out rate: how many people switch off notifications after a message or campaign.
Uninstall and churn signals: whether users who receive many messages leave more often.
Long-term retention: whether notified users remain active over time, compared with a comparable group who received fewer messages.

Where possible, hold back a small control group that does not receive a given message. It is the honest way to tell whether the notification caused the result or whether those people would have acted anyway.

Notification fatigue and testing

Fatigue builds quietly: falling tap rates, rising opt-outs and more uninstalls after campaigns. Reduce frequency, tighten segments and ask whether each message deserves to exist.

Test one thing at a time: copy, timing, a deep link destination or a segment. Run tests long enough to see a meaningful difference, and judge them on conversion and opt-outs, not only on taps. Test across devices and operating systems, with the app open, in the background and closed.

A worked example

Imagine a food delivery app that asks for notification permission as soon as it is installed and sees most users decline. The team changes the flow. After a customer places their first order, a short screen explains, "Get live updates on your delivery", with a clear yes or no. Order status messages are classed as transactional. A separate promotions category is off by default and can be switched on in a preference centre. Promotional messages are capped, sent in local time and held back overnight. The team tracks opt-outs alongside orders, and when one campaign increases both, they scale it back.

FAQ

When should an app ask for push notification permission?

Ask after the user has experienced some value, such as completing a first order or saving something, and explain the benefit before showing the system prompt. Asking on first launch usually leads to refusals that are difficult to reverse.

How often should you send push notifications?

There is no universal rule. Send transactional messages when events happen, and cap promotional messages so users stay subscribed. Watch opt-outs and uninstalls to find the limit for your audience.

What is the difference between web push and app push?

App push is delivered to an installed mobile app through the platform's notification service. Web push is delivered through a browser to users who allowed a site to notify them, and browser support varies, so check your target audience.

How do you measure the success of push notifications?

Track delivery, taps, conversions, opt-out rate and longer-term retention. A control group that does not receive the message shows whether the notification really caused the result.

Next steps

Audit your current notifications: list each type, what triggers it, who receives it and what happens afterwards. Then define transactional, behavioural and promotional categories and set caps. If you are planning notifications for a new or existing mobile product, our app development services team can help, or you can contact us to talk it through.