Notification prompt after sending a message: 5-10% opt-in vs 1-2%
Commentary byLiftArchiveOur analysis, not theirsLinkedIn asks for notification permission right after a user sends a message, offering to alert them when that person replies.
LinkedIn's product team reported 5-10% opt-in for this prompt, against 1-2% for generic ones, about 5x. The case study was published by Growth.Design.
- Notification opt-in: about 5-10% for the contextual prompt vs 1-2% for generic prompts, roughly 5x.
- Growth.Design's headline rounds this to +500%. Treat it as a range, not an exact lift.
- No figures on retention, replies or later engagement are shared.
The change
A generic permission request at login becomes a yes/no question about one named person's reply.
Simplified mockup drawn by LiftArchive from the shared screenshots.
Control
Generic notification permission requests that could appear at any time, such as at login, promising alerts in general terms.
Variant
Right after the user sends a message, a prompt names and shows the person they wrote to and asks a simple yes/no question about being notified when that person replies. The system permission dialog comes after.
Why it likely won
Our reading of the result, not the practitioner's claim.
- Timing: the user has just put effort into a message and wants to know when the reply arrives, so the ask fits what they want right now.
- Naming a real person likely feels more concrete than a vague promise of alerts.
- The ask is framed as a benefit (knowing when someone replies) rather than a feature list of sounds and badges.
- A yes/no question feels like a normal conversation and may be easier to agree to than a system "Allow" dialog.
Caveats: These are LinkedIn product-team figures relayed by Growth.Design, with no sample size or test design given. It may not have been a split test. The 1-2% baseline comes from a different prompt shown at a different moment, so timing and copy are mixed together.
Who ran it
LinkedIn ran this test. Source: Growth.Design case study. The numbers are theirs; the summary and commentary on this page are ours.
How to run this test on your app
- Hypothesis
- If we ask for push permission right after a user does something that has a natural follow-up, and name that follow-up, then more users will opt in because the value of the notification is clear at that moment.
- Primary metric
- Push notification opt-in rate (users who allow / users shown the prompt)
- Guardrails
- Notification opt-out or disable rate
- Day-7 and day-30 retention
- System dialog denial rate
- Who should test it
- Apps where users take actions that lead to a later event: messaging, social, marketplaces, delivery, habit and fitness apps. It helps less if your notifications are mostly promotional, or if there is no clear moment when an alert serves the user.
Questions
Why show a custom prompt before the iOS system dialog?
On iOS, once a user taps "Don't allow", the app can't show the system dialog again.
A soft prompt first lets you save the system ask for users who already said yes.
What if my app has no messaging?
Look for any moment with a natural follow-up: a price drop on a saved item, a workout reminder the user just set, or a delivery update.
The idea is to ask when the alert clearly helps with what the user just did.
Is higher opt-in always better?
Not if you then send alerts users didn't ask for.
Opt-in won this way is tied to a specific promise, so keep the notifications relevant or users will turn them off.