An effective push strategy earns permission by asking in context, then sends notifications that are timely, personal, and useful, such as reminders users set, updates they care about, and progress milestones. Limit marketing pushes, respect platform rules and quiet hours, and personalize timing and content. Measure retention and opt-outs alongside open rates, because a notification that annoys users can cost more than it earns.
Earn permission first
On iOS, apps must ask permission to send notifications, and on Android 13 and later, notifications require a runtime permission too. The request is often a one-time chance, because users who decline rarely enable notifications later in settings. Ask when the value is obvious, such as right after a user sets a reminder or follows a topic.
A short explanation screen before the system prompt, describing exactly what users will receive, can raise opt-in rates. iOS also offers provisional authorization, which delivers notifications quietly to the notification center so users can decide later. Our onboarding best practices guide covers permission timing in context.
Send notifications users want
The best notifications are ones users explicitly asked for or would clearly want: reminders they set, messages from people they know, order and delivery updates, price drops on saved items, and milestones in their own progress. These feel like a service, not marketing.
Promotional notifications, such as sales or new features, should be used sparingly. Apple's guidelines say push notifications should not be used for promotions or direct marketing unless users have explicitly opted in, with a way to opt out in the app. Offer granular notification settings so users can keep useful categories and switch off others.
Personalize content and timing
Personalization goes beyond a first name. Use behavior to choose content, such as reminding a learner of the lesson they stopped mid-way, and to choose timing, such as sending at the hour each user usually opens the app. Respect time zones and quiet hours.
Use platform features thoughtfully. iOS interruption levels, such as time-sensitive notifications, should be reserved for genuinely urgent messages. Rich notifications with images or actions can improve engagement when they add real value, such as a reply button on a message.
Frequency and fatigue
Too many notifications lead users to disable them or uninstall the app. There is no universal ideal frequency; it depends on the category and user preference. A messaging app can send many; a finance app should send few. Set caps per user, and lower frequency for users who stop engaging.
Watch opt-out rates and uninstall rates after campaigns. If a notification type drives opens but also drives opt-outs, it may be destroying long-term value. Our guide to reducing app uninstalls covers notification fatigue as a churn driver.
Lifecycle notifications
Map notifications to the user lifecycle: onboarding nudges to reach the aha moment, habit reminders in the first weeks, re-engagement for lapsing users, and win-back messages for those who have gone quiet. Each stage needs different content and frequency.
Re-engagement works best when it offers something new or valuable, such as new content, a relevant feature, or progress the user has not seen. For subscription apps, pair notifications with win-back offers where appropriate.
Measure what matters
Open rate is a starting point, but measure downstream impact: retention, sessions, conversions, and revenue for users who receive notifications compared with a holdout group that does not. Holdout tests reveal whether notifications create value or simply claim credit for opens that would have happened anyway.
Track opt-in rate, opt-out rate, and notification-related uninstalls. Our guide to DAU/MAU stickiness explains how to see whether notifications improve habitual use.
Push and in-app messaging work together
Push notifications reach users outside the app; in-app messages reach them while they are already engaged. Use in-app messages for feature education, upgrade prompts, and surveys, where interrupting someone's day would be excessive. Reserve push for timely information that is worth pulling the user back into the app.
Coordinate the two so users do not receive the same message twice. If a user has already seen an in-app announcement about a new feature, do not push it again. A shared messaging calendar and suppression rules across channels prevent overlap, and keep the total volume of messages proportionate to the value you provide.
Common push notification mistakes
Asking for permission on first launch without context is the most common mistake, wasting the one chance to earn opt-in. Another is sending generic broadcast messages to everyone, such as We miss you!, which feel spammy and drive opt-outs.
Teams also measure only opens and ignore the long-term cost of annoyed users. Sending at bad times, ignoring time zones, or overusing urgent interruption levels erodes trust. Finally, missing in-app notification settings forces users to choose between all notifications and none.
A worked example: a language app's reminders
A language app asks for notification permission on first launch and gets low opt-in. It then sends daily generic reminders at 9am in the server's time zone. Opt-outs are high. The team moves the request to after users finish their first lesson, with an explanation: Want a daily reminder at the time you choose?
Reminders now arrive at each user's chosen time, reference their streak or next lesson, and stop after several ignored days, replaced by a weekly summary. A holdout test shows users receiving the new reminders retain better at day 30 than the holdout, and opt-outs fall.
How to do it, step by step
- Audit current notificationsList every notification type, its trigger, frequency, and performance, including opt-outs.
- Move permission requests into contextAsk after a user action that shows the value, with a short explanation first.
- Prioritize user-requested notificationsFocus on reminders, updates, and milestones users want, and limit promotions.
- Personalize and capUse behavior for content and timing, respect time zones, and set per-user frequency caps.
- Test with holdoutsMeasure retention and revenue against a holdout group, not just open rates.
Before and after examples
Illustrative examples written for a generic app in this category, not client results. Swap in your own product, audience, and data.
System prompt on first launch.
After first lesson: Want a daily reminder at a time you choose? Then the system prompt.
Why it works: Context and control raise opt-in.
We miss you! Come back.
Your 12-day streak is waiting. Your next lesson is about ordering food, about 5 minutes.
Why it works: Specific, personal value beats guilt.
Daily promotional pushes to everyone.
User-chosen reminders plus at most one promotional message a week for opted-in users.
Why it works: Lower volume of relevant messages preserves trust.
Action plan
- Ask for permission in context
- Prioritize notifications users requested
- Limit promotions and follow platform rules
- Personalize timing and content
- Cap frequency and respect quiet hours
- Measure impact with holdout groups
Metrics to monitor
- Push opt-in rate
- Open rate by notification type
- Opt-out and uninstall rates after sends
- Retention versus holdout
- Conversions attributed to notifications
Record the baseline, release date, audience, markets, and external changes before interpreting movement. Rankings and conversion are useful signals, but a decision is stronger when activation, retention, and business value confirm that the page attracted the right users.
Frequently asked questions
When should I ask for push notification permission?
After a user action that shows clear value, such as setting a reminder, with a brief explanation before the system prompt.
How many push notifications are too many?
It depends on the category and the user. Watch opt-outs and uninstalls, cap frequency, and lower volume for disengaged users.
Can I send marketing push notifications on iOS?
Apple's guidelines require users to explicitly opt in to promotional notifications and to have a way to opt out in the app.
Do push notifications improve retention?
Relevant, well-timed notifications usually do. Test with a holdout group to confirm they create value rather than annoyance.
Keep reading
Go deeper on this topic
More in Retention and Engagement
Browse all 6 Retention and Engagement guides
Work with ASOWin
Primary sources
Platform capabilities and limits can change. Verify current requirements in these official resources:
