Getting users to tap "Allow" on a push notification permission prompt is one of the highest-leverage moments in mobile and web engagement. Yet most apps squander it — firing the system dialog on first launch with zero context, then permanently losing the ability to reach that user. If you've ever wondered how to allow push notifications in a way that actually works for both users and product teams, the answer starts long before the OS prompt appears.
This guide breaks down push notification permission flows on iOS and Android, explains the pre-permission dialog strategy that top apps use to double their opt-in rates, provides timing frameworks, shares industry benchmarks, and covers how to re-engage users who already declined.
How Push Notification Permissions Work: iOS vs Android
Before optimizing your permission flow, you need to understand the fundamental differences between how Apple and Android handle notification consent. The two platforms take radically different approaches, and your strategy must adapt accordingly.
iOS Permission Flow
On iPhone and iPad, push notification permission is a hard gate. Here's how it works:
- Your app calls the system API —
UNUserNotificationCenter.requestAuthorization()triggers the native iOS dialog. - The user sees a one-time system prompt — "App Name Would Like to Send You Notifications" with two options: Allow and Don't Allow.
- The decision is (mostly) final — if the user taps "Don't Allow," your app cannot show the system prompt again. The only way for the user to reverse this is to manually go to Settings → Notifications → Your App and toggle it on.
Starting with iOS 12, Apple introduced Provisional Authorization, which lets apps send notifications directly to the Notification Center quietly (no banner, no sound) without asking first. Users can then choose to "Keep" or "Turn Off" after seeing a real notification. This changed the game for apps willing to prove value before demanding attention.
Key takeaway: On iOS, you get one shot with the system dialog. If you want to learn how to allow push notifications on iPhone for your users at scale, you must treat that single prompt as precious real estate.
Android Permission Flow
Android's permission model has evolved significantly:
- Android 12 and below — apps could send notifications immediately after install with no permission prompt required. Notifications were on by default.
- Android 13 (API 33) and above — Google introduced a runtime permission (
POST_NOTIFICATIONS) that mirrors the iOS model. Apps must now explicitly request permission, and users see a system dialog.
If you need to allow push notifications Android style on newer devices, the flow is:
- Declare the permission in
AndroidManifest.xml:<uses-permission android:name="android.permission.POST_NOTIFICATIONS"/> - Request at runtime using
ActivityCompat.requestPermissions(). - Handle the response — users can Allow or Deny. If they deny twice, Android stops showing the system dialog (similar to iOS), and they must go to Settings to reverse it.
Key difference from iOS: Android gives you two attempts at the system prompt before it's locked, and you can direct users to settings with an in-app deep link more seamlessly. Samsung, Xiaomi, OPPO, and other manufacturers may have slight variations in their settings UI, but the runtime permission behavior is consistent across Android 13+ devices.
The Pre-Permission Dialog Strategy
The single most effective technique for increasing push notification opt-in rates is the pre-permission dialog (also called a "soft ask" or "primer"). Instead of immediately triggering the system prompt, you show your own custom in-app screen first.
How It Works
- Show a custom UI first — this is your own dialog, modal, or full-screen that explains why notifications matter. Because it's your UI, you can design it however you want and show it as many times as needed.
- If the user taps "Yes" or "Enable" — you then trigger the real system permission prompt.
- If the user taps "Not Now" — you dismiss your dialog without ever touching the system prompt. You've preserved your one-shot system ask for a better moment.
Why This Works
The math is straightforward. Without a pre-permission dialog:
- 100% of users see the system prompt → ~50% allow (average) → you've burned the prompt for the other 50%.
With a pre-permission dialog:
- 100% of users see your soft ask → ~60% engage positively → those 60% see the system prompt → ~85% of them allow (because they already said yes once) → net opt-in rate: ~51%, but crucially, you still have the system prompt available for the 40% who said "Not Now."
Over time, as those 40% experience your app and see the soft ask again at better moments, your cumulative opt-in rate climbs to 60–70%+.
Best Practices for Pre-Permission Dialogs
- Be specific about the value — "Get notified when your order ships" beats "Enable notifications for the best experience."
- Use visuals — show a mock notification or screenshot of what the user will receive.
- Offer a clear opt-out — "Not Now" (not "No") signals that this isn't a permanent decision.
- Never dark-pattern the user — avoid hiding the dismiss button or using confusing language. Trust erodes fast.
- Personalize the message — an e-commerce app should mention deals/shipping; a fitness app should mention workout reminders; a messaging app should mention new messages.
Timing Strategies: When to Ask for Permission
Timing is arguably more important than the dialog design itself. Asking at the wrong moment — no matter how beautiful your prompt — will get dismissed.
The Wrong Time
- On first launch, before the user has done anything. The user has zero context on your app's value. This is the #1 mistake and the fastest way to burn your system prompt.
- During onboarding flow overload. If you've already asked for location, camera, contacts, and microphone, adding notifications to the pile triggers "permission fatigue."
- When the user is mid-task. Interrupting a checkout flow or an intense game session guarantees a "Don't Allow."
The Right Time
The best moments to turn on push notifications requests are tied to value realization:
| Trigger Event | Why It Works | Example |
|---|---|---|
| After first key action | User has experienced core value | After placing first order, completing first workout, sending first message |
| After content consumption | User is engaged and wants more | After reading 3 articles, watching 2 videos, browsing 5 products |
| Before a relevant event | Notification has obvious immediate value | "Want to know when this item goes on sale?" / "Get notified when your driver is nearby" |
| After a return visit | User has demonstrated retention | Second or third session, showing they like the app |
| During a natural pause | User isn't interrupted | Between levels in a game, after submitting a form, after completing a tutorial |
The "Value-First" Framework
Top-performing apps follow a simple framework:
- Session 1 — focus on delivering value. No permission asks.
- Session 2–3 — if the user returns, show a contextual soft ask tied to something they just did.
- Ongoing — if they declined the soft ask, wait for a high-value trigger event (e.g., "Your friend just joined!" or "Price dropped on an item you viewed").
Industry Benchmarks: What Good Looks Like
Understanding where you stand relative to your industry helps you set realistic goals and identify opportunities for improvement.
Average Push Notification Opt-In Rates by Platform
| Platform | Average Opt-In Rate | Top Quartile |
|---|---|---|
| iOS (with pre-permission) | 55–65% | 70–80% |
| iOS (without pre-permission) | 35–45% | 50–60% |
| Android 12 and below | 80–95% (default on) | 95%+ |
| Android 13+ (with runtime prompt) | 60–70% | 75–85% |
| Web (desktop browsers) | 7–15% | 20–30% |
| Web (mobile browsers) | 3–8% | 10–15% |
Average Opt-In Rates by Industry
| Industry | iOS Opt-In | Android Opt-In |
|---|---|---|
| Ride-sharing / Delivery | 70–80% | 85–92% |
| Messaging / Social | 65–75% | 80–90% |
| E-commerce / Retail | 45–55% | 70–80% |
| News / Media | 50–60% | 72–82% |
| Finance / Banking | 55–65% | 75–85% |
| Gaming | 35–45% | 65–75% |
| Health / Fitness | 50–60% | 70–80% |
| SaaS / Productivity | 40–50% | 65–75% |
Key insight: The gap between "with pre-permission" and "without" is 15–20 percentage points on iOS. That gap alone can represent hundreds of thousands of reachable users for a mid-sized app.
Re-Engagement Strategies for Users Who Declined
Even with perfect timing and a great pre-permission dialog, some users will decline. On iOS, this means they tapped "Don't Allow" on the system prompt. On Android 13+, they hit "Deny" twice. In both cases, you can no longer programmatically trigger the permission dialog. But that doesn't mean they're lost forever.
Strategy 1: In-App Messaging with Settings Deep Link
Show an in-app banner or modal at a high-value moment explaining what they're missing, with a button that deep links directly to your app's notification settings page.
- iOS: Use
UIApplication.openSettingsURLStringto open your app's settings page. - Android: Use an
IntentwithSettings.ACTION_APP_NOTIFICATION_SETTINGSto jump to the exact notification settings screen.
Example copy: "You're missing real-time updates on your delivery. Tap here to enable notifications in Settings — it takes 5 seconds."
Strategy 2: Email / SMS Fallback with Notification Upsell
If you have the user's email or phone number, send a transactional message (e.g., order confirmation) that includes a note: "Want faster updates next time? Enable push notifications in the app for real-time tracking."
Strategy 3: Value Demonstration
Show the user what they missed. For example:
- "You had 3 flash sales while notifications were off."
- "Your friend messaged you 2 hours ago — with notifications on, you'd know instantly."
- "A price drop happened on an item in your wishlist yesterday."
This creates tangible FOMO tied to real app events, not hypothetical scenarios.
Strategy 4: Contextual Re-Ask on Feature Usage
When a user engages with a feature that naturally benefits from notifications (e.g., setting a reminder, following a topic, joining a group), present a contextual prompt: "To make sure you never miss updates from this group, enable notifications in Settings."
Strategy 5: In-App Notification Center as a Bridge
Build an in-app notification feed that shows all the alerts the user would have received as push notifications. When they see the accumulated value — messages, deals, updates — they are more likely to enable push delivery for real-time access. This approach works especially well for content and social apps where the volume of missed updates is visible and compelling.
Technical Implementation Tips
Token Management
When a user grants notification permission, you receive a device token (APNs token on iOS, FCM registration token on Android). Managing these tokens correctly is critical:
- Refresh tokens on every app launch — tokens can change after OS updates, app reinstalls, or backup restores.
- Remove stale tokens — if a push provider returns an "invalid token" error, remove it from your database immediately.
- Map tokens to user IDs — a single user might have multiple tokens (phone + tablet), and a single device might change users (shared devices).
For teams building or scaling their notification infrastructure, a dedicated push notification service can handle token lifecycle management, cross-platform delivery, and analytics out of the box — removing months of backend engineering work.
Permission Status Checks
Always check current permission status before deciding whether to show your pre-permission dialog or a settings deep link:
- iOS:
UNUserNotificationCenter.current().getNotificationSettings()returns.authorized,.denied,.provisional, or.notDetermined. - Android:
NotificationManagerCompat.from(context).areNotificationsEnabled()returns a simple boolean.
Use .notDetermined (iOS) or first-launch detection (Android) to know if you still have your system prompt available. Use .denied / !areNotificationsEnabled() to trigger the re-engagement flows described above.
A/B Testing Your Permission Flow
Treat your notification permission flow like any other conversion funnel:
- Test dialog copy — value-specific vs. generic.
- Test timing — first session vs. second session vs. event-triggered.
- Test design — modal vs. bottom sheet vs. full-screen.
- Test frequency — how often to re-show the soft ask to users who declined it.
Track your opt-in rate as a core product metric, segmented by platform, user cohort, and acquisition channel. A robust push notification platform will provide built-in analytics dashboards for permission rates, delivery rates, and engagement metrics across iOS, Android, and web channels.
Common Mistakes to Avoid
- Firing the system prompt on first launch — you get one shot on iOS (two on Android). Don't waste it.
- Using generic copy — "We'd like to send you notifications" tells the user nothing about value.
- Never re-asking — users who said "Not Now" to your soft ask are not permanently opposed. Re-ask at a better moment.
- Ignoring Android 13 changes — if you're still assuming Android notifications are on by default, you're losing a massive chunk of your newer Android audience.
- Not tracking opt-in rates — if you don't measure it, you can't improve it. Segment by platform, OS version, and user cohort.
- Asking for too many permissions at once — notification permission should stand alone, not be bundled with location, camera, and contacts.
- Forgetting web push — web push opt-in rates are low but the channel is underused. A well-timed, well-designed prompt on desktop can capture engaged users you can't reach via mobile.
Frequently Asked Questions
How do I allow push notifications on iPhone?
Go to Settings → Notifications, select the app you want to receive notifications from, and toggle Allow Notifications on. You can also customize alert styles (banners, sounds, badges) and choose whether notifications appear on your lock screen, in Notification Center, or both. If the toggle is missing, open the app first — it may need to trigger the permission request before the option appears in Settings.
How do I allow push notifications on Android?
On Android 13 and newer, go to Settings → Notifications → App notifications, find the app, and toggle notifications on. On older Android versions (12 and below), notifications are enabled by default, but you can manage them in Settings → Apps → [App Name] → Notifications. Samsung, Xiaomi, and OPPO devices have slightly different menu paths but follow the same general structure.
What is a good push notification opt-in rate?
On iOS, a good opt-in rate is 55–65% with a pre-permission dialog strategy, with top-performing apps reaching 70–80%. On Android 13+, 60–70% is typical, with top apps hitting 75–85%. On older Android versions where notifications are on by default, rates exceed 80–90%. Web push opt-in rates are significantly lower, averaging 7–15% on desktop browsers.
Can I ask for push notification permission again after a user declines?
Not with the system prompt. On iOS, once a user taps "Don't Allow," the system dialog cannot be shown again. On Android 13+, after two denials, the system dialog is suppressed. However, you can show your own custom in-app message with a deep link to your app's notification settings in the device Settings app, making it easy for users to reverse their decision with a single tap.
What is a pre-permission dialog and why should I use one?
A pre-permission dialog (or "soft ask") is a custom in-app screen you show before triggering the actual system permission prompt. It explains the value of enabling notifications in your own words and design. If the user declines your soft ask, you haven't used up the one-time system prompt — you can try again later. Apps that use pre-permission dialogs see 15–20 percentage points higher opt-in rates compared to those that fire the system prompt directly.
How do I turn on push notifications for a website?
When a website requests notification permission, your browser shows a prompt — click Allow. If you previously blocked it, you can re-enable it in your browser settings. In Chrome, go to Settings → Privacy and Security → Site Settings → Notifications and find the website in the blocked list. In Safari on Mac, go to Safari → Settings → Websites → Notifications. On iPhone, web push requires iOS 16.4+ and the website must be added to your home screen first.
When is the best time to ask users to turn on push notifications?
The best time is after the user has experienced your app's core value — not on first launch. Effective trigger moments include completing a first purchase, finishing onboarding, consuming content, or engaging with a feature that benefits from real-time updates (like following a topic or tracking an order). Studies consistently show that delaying the permission request to the second or third session increases opt-in rates by 15–30%.
How do provisional notifications differ from regular push notifications on iOS?
Provisional notifications (iOS 12+) are delivered silently to the Notification Center without showing a permission prompt upfront. They don't appear as banners, play sounds, or show badges. Each provisional notification includes "Keep" and "Turn Off" buttons, letting users decide based on actual content rather than a hypothetical promise. This is ideal for apps that want to demonstrate notification value before requesting full, prominent delivery permission.
Conclusion
Push notification permission management isn't a one-time setup task — it's an ongoing optimization discipline that directly impacts your ability to reach and retain users. The difference between a naively implemented permission flow and a well-optimized one can be 20–30 percentage points in opt-in rate, translating to hundreds of thousands of additional reachable users.
Start with the fundamentals: understand how iOS and Android permission flows differ, implement a pre-permission dialog, time your ask around value moments, and build re-engagement paths for users who decline. Measure everything, A/B test relentlessly, and treat your opt-in rate as a top-line product metric.
For teams looking to implement a complete notification stack — from permission management and token handling to segmented delivery and analytics — a purpose-built push notification solution can accelerate your timeline and provide the infrastructure needed to manage permissions, optimize delivery, and measure engagement at scale.