Subscribers unsubscribe from push notifications mainly because they get too many, the alerts aren’t relevant, or they never really meant to subscribe. Other common causes are poor timing, misleading prompts and messages that don’t match what was promised. Some losses aren’t choices at all, such as cleared browser data or expired subscriptions.
I look at unsubscribes as feedback, not failure. Every web push list loses people over time, and that’s normal. What matters is spotting the causes you control and fixing them before the list shrinks faster than it grows. Here’s what I check, in the order I check it.
Quick facts:
- Users can block or remove a site’s notification permission at any time in browser settings, as Chrome Help explains.
- When a subscription is gone, the push service returns an error such as 404 or 410, so the sender knows to remove it (RFC 8030).
- Prompts that appear before people understand the value lead to more denials and weaker subscribers, per web.dev permission best practices.
- In web push, “unsubscribe” usually means blocking notifications, since there’s rarely an unsubscribe link inside the alert.
Why do subscribers unsubscribe from push notifications?
Subscribers unsubscribe from push notifications when the cost of the interruption outweighs the value. Too many messages, off-topic messages, bad timing and a mismatch with what the prompt promised all tip that balance. Accidental or pressured subscriptions also fade fast.
Here are the main causes I see, with what you can do about each:
| Cause | What it looks like | Fix |
|---|---|---|
| Too many notifications | Blocks rise after busy days | Cap daily sends; batch updates |
| Irrelevant content | Low CTR across many segments | Segment by category, location or device |
| Bad timing | Alerts arrive at night locally | Schedule by subscriber time zone |
| Misleading prompt | Fast drop-off after subscribing | Say exactly what subscribers will get |
| Prompt on first load | Many subscribers who never click | Ask after engagement, not instantly |
| Dull or repetitive copy | Declining CTR on similar campaigns | Test titles, images and CTA buttons |
How do people actually unsubscribe from web push?
People unsubscribe from web push by blocking the site in their browser or operating system settings, or by clicking a browser option such as “turn off notifications” on the alert. Unlike email, there’s usually no unsubscribe link in the message itself.
That has a practical effect: an annoyed subscriber doesn’t just leave your list, they block your site. If you ever want them back, the browser won’t show your prompt again until they change the setting manually. That’s why preventing unsubscribes matters more in push than in email.
Which unsubscribes are not the subscriber’s choice?
Some subscriber loss is technical, not a decision. Subscriptions disappear when people clear browsing data, reinstall a browser, switch devices, or when the push service expires a subscription.
When that happens, your next send gets an error from the push service, often a 404 or 410 response, and a good push panel removes the record. You’ll see this as “expired” or “invalid” subscriptions rather than active unsubscribes. It’s a normal part of list hygiene, and the push provider shutdown post explains why subscriptions are tied to the setup that created them.
How many push notifications is too many?
Too many is whatever makes your own block rate climb, because the right number depends on your content and audience. A news site with breaking stories can send more than a weekly blog, as long as each send earns its place.
My approach is simple:
- Set a starting cap, such as one to three sends a day for active publishers.
- Track unsubscribes and CTR for two weeks.
- Raise or lower the cap one step at a time.
- Use segments so heavy readers can get more and casual readers fewer.
- Batch small updates into one roundup instead of many single alerts.
How do you make notifications more relevant?
You make notifications more relevant by sending each one only to the people likely to care. Segmentation by category, location, device, browser or subscription page lets you avoid blasting everyone with everything.
For example, a sports publisher can send cricket alerts only to people who subscribed from cricket pages. An online store can send local delivery offers only to the countries it ships to. Relevance is the single biggest lever I know for keeping subscribers, and the web push best practices for publishers post has more examples.
How does the opt-in prompt affect unsubscribes?
The opt-in prompt sets expectations, so a vague or pushy prompt creates subscribers who leave quickly. If you ask on first page load, many people click “Allow” just to get rid of the box, then block you later.
Ask after someone has read or scrolled, and tell them what they’ll get, such as “new reviews twice a week”. Follow up with a welcome notification that confirms it. Both steps make the subscriber’s decision deliberate, which keeps them longer. My guide to improving web push opt-in rate covers prompt design in detail.
How do you measure unsubscribes?
You measure unsubscribes by tracking active subscriber count, new subscribers and removed or expired subscriptions over time, alongside CTR for each campaign. A rising removal count after a change tells you what to undo.
Look at the trend, not single days. Compare unsubscribes per campaign type, send time and segment. If one type of campaign keeps causing drops, change or stop it. The push notification metrics guide lists the numbers worth watching.
Where LaraPush fits
LaraPush gives you the controls that reduce unsubscribes: segmentation by device, browser, OS, country, region, subscription date, subscribed URL, referrer and last visit, scheduling, customisable prompts with delay and re-prompt control, a Welcome Push, and per-campaign analytics. The audience segmentation page shows how segments work. It’s self-hosted, from $499 one-time (see LaraPush pricing), with no sponsored ads added to your notifications. The trade-off is that you run your own VPS, and there’s no free plan.
Frequently asked questions
There’s no single normal rate, because it depends on your niche, frequency and prompt design. Track your own removals per campaign and per week, and treat a sudden rise after a change as the signal to act, rather than chasing an industry average.
Usually you see that a subscription stopped working, not why. When a user blocks your site or clears data, the push service returns an error on the next send, and the panel marks that subscription as expired or removes it.
Only if the browser allows your prompt to show again. If someone blocked notifications for your site, the browser won’t show the native prompt until they change the setting themselves, so prevention matters more than winning people back.
It can. Notifications that arrive late at night in the subscriber’s time zone feel intrusive. Scheduling sends for local daytime hours, or segmenting by country or region, reduces that risk.
A welcome notification confirms what subscribers signed up for and sets expectations from the first message. That clarity helps subscribers who joined deliberately stay longer, especially when the following messages match what the welcome promised.




