In this article · 14 sections
- 01Why people turn notifications off
- 021. Ask for permission with context
- 032. Send only what is useful
- 043. Personalise by behaviour
- 054. Control frequency
- 065. Time them well
- 076. Write clear, honest copy
- 087. Make them accessible and respectful
- 098. Consider other channels
- 109. Measure what matters
- 1110. Stay compliant
- 12Common mistakes
- 13Checklist
- 14Final thoughts
Push notifications are one of the most powerful tools for bringing users back to an app. They are also one of the fastest ways to lose them. A useful alert at the right moment feels like a helpful assistant. A pointless one feels like spam, and people respond by muting notifications or deleting the app.
This guide covers how to use push in a way that earns attention instead of burning it.
Why people turn notifications off
Understanding the failure modes helps you avoid them:
- Irrelevant content, meaning messages that are not about the person
- Too many, especially several a day with no new information
- Bad timing, such as late at night or mid-meeting
- Vague or manipulative copy, like “Don’t miss out!”
- Asking too early, before the user knows why they should say yes
1. Ask for permission with context
On iOS, users must opt in to notifications. On Android 13 and later, apps also request notification permission at runtime. In both cases, the system prompt is often a one-time chance, so the timing matters.
- Wait until the user has seen value in the app
- Show a short pre-permission screen explaining the benefit (“Get a reminder when your order ships”) before the system prompt
- Ask in the context of a feature, not on first launch
- Respect a “no”. Provide a way to enable alerts later in settings
Our onboarding guide explains this in more depth.
2. Send only what is useful
A good test: would the user thank you for this message? Notifications generally fall into categories:
| Type | Example | Value |
|---|---|---|
| Transactional | Order shipped, payment received, verification code | High; expected |
| Personal / social | New message, friend request, someone replied | High; time-sensitive |
| Reminders | Appointment tomorrow, task due | High when user-set |
| Content / updates | New article from an author you follow | Medium |
| Promotional | Sale, new feature | Low unless carefully targeted |
Prioritise the first three. Use promotional messages sparingly and only for segments likely to care.
3. Personalise by behaviour
Segmenting beats blasting everyone.
- Base messages on what the user did or said they care about
- Use preferences the user set, such as topics or frequency
- Trigger messages by events, like an abandoned cart, instead of by calendar alone
- Avoid using sensitive data in message text, since notifications can appear on lock screens
4. Control frequency
There is no universal ideal number. Decide based on your product: a messaging app sends many, a budgeting app few.
- Set caps on how many promotional messages a person can receive per day or week
- Group related events into digests where it makes sense
- Offer granular settings so people can choose categories and quiet hours
- Watch opt-out and uninstall rates after changes in volume
5. Time them well
- Use the user’s local time zone
- Avoid sending outside reasonable hours unless the message is urgent and expected
- For time-sensitive alerts, such as security events, send immediately
- Test send times with different segments
6. Write clear, honest copy
- Lead with the most important information, since text is truncated
- Be specific: “Your table for 2 at 7:30 pm is confirmed” beats “Reservation update”
- Use plain, friendly language
- Include a clear next step that opens the right screen via deep link, not just the home screen
- Avoid false urgency and misleading claims
- Add rich media like images only when it helps
7. Make them accessible and respectful
- Keep messages understandable without images
- Avoid putting private information on the lock screen
- Honour system-level settings and focus modes
- Provide an easy way to manage or turn off categories inside the app
8. Consider other channels
Push is not always the right channel. In-app messages suit users who are already active. Email suits longer or less urgent content. SMS should be reserved for critical or opted-in cases, and is subject to regional rules. Choose the channel that fits the message.
9. Measure what matters
Look beyond open rate.
- Delivery and open rates by message type
- Conversion to the action you wanted
- Opt-out rate and uninstalls after campaigns
- Retention of users who received notifications compared with a holdout group that did not
The holdout comparison is the honest test of whether a notification adds value. See improving app retention for how to read cohorts.
10. Stay compliant
Marketing messages may be subject to consent and anti-spam laws in some regions. Be transparent in your privacy policy about how notification data and device tokens are used, and honour opt-out requests promptly.
Common mistakes
- Asking for permission on first launch
- Sending the same message to everyone
- Daily promotional blasts
- Vague copy that does not say what happened
- Linking to the home screen instead of the relevant content
- Never measuring opt-outs
Checklist
- Permission requested in context with a pre-explanation
- Messages categorised: transactional, social, reminder, promotional
- Segments and behaviour-based triggers
- Frequency caps and quiet hours
- Local time zone scheduling
- Clear copy with deep links
- User controls for categories
- Opt-out, uninstall and retention tracked
- Legal and privacy requirements reviewed
Final thoughts
Treat every notification as a request for someone’s attention and make sure it is worth it. Fewer, better messages build the trust that makes people leave notifications on. For help designing engagement flows, see our app development service or contact us.