Working · 2026-11SecondaryRetentionLifecycle

Contextual push permission prompt

Ask for notification permission right after a relevant user action, naming a specific benefit, instead of at first launch.

Also called: permission priming, retention triggers

Claim and evidence

The claimBy using _behavioral retention triggers_, Linkedin achieves a **5-10% conversion rate** (vs 1-2% for random prompts)

LinkedIn · growth.design · undated

What the numbers show

5–10%

conversion for LinkedIn's behaviour-triggered prompts, per Growth.Design (not independently verified)

growth.design
1–2%

conversion for random prompts, same write-up

growth.design
50%

of users block notifications, per the same write-up

growth.design

Why it works

Diagram, not data
User just did arelevant actionSoft promptnames thebenefitOn yes, thesystem dialogCompare withthe defaultprompt
User just did a relevant actionSoft prompt names the benefitOn yes, the system dialogCompare with the default prompt

Users agree when the value is concrete and the moment is relevant (just sent a message). Generic prompts at random times get refused, and with OS-level permission, a refusal is hard to reverse.

How to run it

  1. Pick the action where a notification clearly helps
  2. Show a soft in-app prompt first, name the person or event
  3. Only then trigger the OS permission dialog
  4. Compare opt-in rate against the default prompt

Before / after

Before
Turn on notifications?
Allow
Don't allow
Generic ask at a random moment
After
Message sent
Want to know when they reply?
Notify me
Not now
Ask right after an action, naming the benefit

Generalised wireframe of the pattern, not a copy of any company's screen.

Ways to run it

Design options to test, not promised results.

  1. Option AAfter a sent message

    Ask right after the user sends a message, naming the person they'll hear back from, as LinkedIn does.

  2. Option BAfter following something

    Ask when the user follows a topic, event or account, tying the prompt to that update.

  3. Option CSoft prompt first

    Always show your own screen first and trigger the system dialog only on a yes.

Dated examples

  1. —

    LinkedIn

    Growth.Design write-up of LinkedIn's contextual notification prompt after an action.

    Page reports 5-10% conversion vs 1-2% for random prompts (not independently verified).

    “By using _behavioral retention triggers_, Linkedin achieves a **5-10% conversion rate** (vs 1-2% for random prompts)”
    ✓ quote checked word-for-word on the page

    growth.design · undated

Does it still work?

Workingas of 2026-11

Android 13 now requires an explicit permission, and Batch reports Android opt-in fell from 85% to 67% in a year; iOS 58% to 56%. Priming matters more. source

Risks

  • LinkedIn numbers come from a design-blog write-up, not LinkedIn
  • Over-priming can annoy users

Sources

  1. growth.design · Growth.Design · undated
    “Notifications are crucial for retention. Unfortunately, 50% of users block them.”
    ✓ quote checked word-for-word on the page
  2. growth.design · Growth.Design · undated
    “By using _behavioral retention triggers_, Linkedin achieves a **5-10% conversion rate** (vs 1-2% for random prompts)”
    ✓ quote checked word-for-word on the page
  3. batch.com · Batch · undated
    “In just one year, Android opt-in rates have fallen from 85% to 67%.”
    ✓ quote checked word-for-word on the page

Change log

  • 2026-11-20 — harvest v0.1 (retention)