Web Push Notifications: The Complete Guide for 2026

Web push is the only marketing channel where a visitor can leave your website and still hear from you — without giving you an email address, downloading an app, or remembering you exist. One click on a prompt, and you have a direct line to their device.

This guide covers how the technology actually works, what changed in 2025–26 (especially on iOS), and the playbook we see working across Indian e-commerce, media, and SaaS sites.

How web push actually works

Three pieces cooperate to deliver a push notification, and none of them is your server doing the heavy lifting:

1. The service worker — a small JavaScript file on your domain that the browser runs in the background, even when your tab is closed.
2. The push service — infrastructure operated by the browser vendor (Google, Mozilla, Apple). Your message goes here first, encrypted.
3. VAPID keys — a public/private key pair that proves the message really came from you. The private key signs every send.

When a user clicks Allow, the browser returns a unique subscription token. Your platform stores it; to send, it encrypts the payload against that token and hands it to the push service, which wakes the service worker on the device to display the notification.

Browser support in 2026

• Chrome / Edge (desktop + Android) — full support, including images and action buttons.
• Firefox — full support on desktop and Android.
• Safari macOS — supported since Safari 16 via the standard Push API.
• Safari iOS — supported since iOS 16.4, but only for sites added to the Home Screen. Treat iOS as a bonus audience, not your base case.

Practical takeaway: for Indian traffic — overwhelmingly Android Chrome — web push covers the vast majority of your visitors with no app required.

The opt-in prompt decides everything

The single biggest mistake: firing the native browser permission dialog the instant the page loads. Users reflexively hit Block — and a Block is close to permanent, because browsers suppress re-asking.

The fix is a soft prompt: your own dismissible UI that explains the value first. Only when the user accepts your soft prompt do you trigger the native dialog. Acceptance rates routinely double or triple.

• Show after engagement — second pageview, 30 seconds on page, or add-to-cart — never on first paint.
• Say what they get: “Get order updates & price-drop alerts” beats “We would like to send you notifications.”
• Offer a polite decline (“Not now”) and respect a cooldown of 5–7 days before asking again.

A push subscriber who opted in for a clear reason is worth ten who clicked Allow by accident.

What to send (and what not to)

• Transactional — order shipped, payment received, booking confirmed. Highest CTR, zero unsubscribes.
• Behavioral — back-in-stock, price drop, cart reminder. Send within minutes of the trigger, not next morning.
• Editorial — breaking story or new post for media sites; works brilliantly with auto-push on publish.
• Avoid — generic daily blasts. Frequency without relevance is how channels die; cap yourself at a few per week unless users chose more.

Measuring success honestly

Track three numbers per campaign: delivery rate (sent vs. devices reached), display rate (the service worker confirmed render), and CTR (clicks ÷ displayed). A healthy promotional push lands 3–10% CTR; transactional often clears 20%.

Add UTM parameters to every click URL so revenue shows up attributed in your analytics — ReachBell appends them automatically.

Launch checklist

1. Serve your site over HTTPS (mandatory for service workers).
2. Add the SDK snippet and service-worker file to your domain.
3. Design a value-first soft prompt with a sensible trigger.
4. Wire transactional events first — they earn trust for everything else.
5. Set a frequency cap and quiet hours before your first big campaign.

Web push rewards restraint: respect the channel and it quietly becomes one of your highest-ROI retention tools. Ready to try? ReachBell’s free tier covers your first 1,000 subscribers — setup takes about five minutes.