Ask when the request has a concrete meaning

A permission prompt works best after a visitor has seen the value of the site and taken an action that makes notifications relevant. The website can explain the choice, but only the browser can grant notification permission.

Good moment
After a save, follow, reminder, or deliberate settings choice.
Poor moment
On the first page view, before the visitor knows what will be sent.

Separate explanation from browser permission

A custom explanation can describe the notification category, expected frequency, and how to stop messages. It must not imitate the browser prompt or make declining difficult. The browser's native control remains the final consent step.

Useful prompt formula

Tell the visitor what will be sent, what event triggers it, and how often it is likely to arrive. Then use a button that clearly asks to enable browser notifications.

Choose a meaningful trigger

After a saved action

A saved search, followed topic, tracked item, or requested reminder gives the notification a concrete purpose.

After repeat engagement

A returning reader or customer has more context than a first-page visitor. Page count alone is imperfect, but it can prevent an immediate interruption.

Inside notification settings

An account preference screen is appropriate for operational alerts, product changes, and category-level controls because the person is already making a messaging decision.

Avoid dead-end pre-prompts

If a visitor dismisses the explanation, remember the choice for a reasonable period. If the browser permission state is denied, do not repeatedly call the permission API. Explain how to change browser settings only when the person actively asks to troubleshoot notifications.

Measure the entire permission path

  • Visitors eligible to see the explanation
  • Explanations displayed
  • Enable buttons selected
  • Native prompts shown
  • Permission granted, denied, or dismissed
  • Subscriptions successfully stored
  • Subscribers who later revoke permission or opt out

A high grant rate can be misleading if the explanation is shown only to a tiny, heavily filtered audience. Report the denominator for each stage using the definitions in the push notification metrics guide.

Special case for iPhone and iPad

Web Push is available to Home Screen web apps on supported iOS and iPadOS versions. The permission request must follow direct user interaction. The iPhone and iPad Web Push guide explains the installation, manifest, permission, and device-testing sequence.

Permission review checklist

  • The notification benefit is specific.
  • The expected category and frequency are visible.
  • The user takes a clear action before the browser prompt.
  • Declining does not block normal site use.
  • Dismissal and denial states are respected.
  • An unsubscribe or preference path is available.
  • The subscription is stored only for the verified origin that created it.

Primary technical references

Map every permission state to one interface

StateShowDo not show
Not yet decidedA specific benefit, expected frequency, and an affirmative subscribe action.An automatic browser prompt or a fake native dialog.
Granted, no current subscriptionA repair or resubscribe action that explains what will happen.A claim that notifications are already active.
Granted and subscribedTopics, pause controls, test notification, and unsubscribe access.Another permission request.
DeniedA quiet status and optional browser-settings help when requested.Repeated prompts, blocking overlays, or instructions on every visit.

Test the promise, not button color

The web push notification service should receive only subscriptions created after this understandable choice; prompt conversion never justifies weakening the permission standard.

Before comparing visual treatments, compare value propositions that represent genuinely different subscriber choices: a single order event, a weekly digest, or alerts for a saved topic. Measure from eligible explanation views through stored subscriptions and later opt-outs. After permission, apply the frequency-cap framework so the ongoing message volume still matches that promise.

Keep a holdout when practical so you can compare whether subscribers return for the requested outcome rather than only whether they accepted the prompt. Record the wording, audience, eligibility rule, and test dates so the result is reproducible and can be reviewed later.