For News, magazines, newsletters, creators
Push notification re-engagement for News, magazines, newsletters, creators
News, magazines, newsletters, creators lose a share of their audience to inbox fatigue every month. Web push notifications sent to an installed PWA sit on the lock screen instead, giving lapsed users a lightweight nudge to come back.
Why email re-engagement plateaus
Re-engagement email campaigns compete with a full inbox and are frequently caught by spam filters after a subscriber has gone quiet for a while.
How web push differs
Push notifications from an installed PWA are delivered by the browser directly, bypassing inbox filtering entirely. For media & publishers, this is most useful for time-sensitive updates that lose value if seen a day late.
Segmenting by recency
Rather than pushing to everyone, segment by last-active date and adjust frequency — someone who opened the app yesterday needs a different cadence than someone dormant for a month.
Avoiding notification fatigue
Push permissions can be revoked at any time; sending too frequently is the most common cause of unsubscribes, so most teams cap re-engagement sends to a few per week at most.
Example notification
Here’s what’s new since your last visit.
Something new just went live — take a look.
FAQ
Do we need an email address to send push?
No — push relies on a browser subscription created when the user installs and opts in, not an email address.
How is this different from a native app’s push notifications?
The delivery mechanism is the same underlying browser push API; the difference is there is no app-store install required to opt in.
Can users turn push off?
Yes, at any time from their browser or device notification settings — it is fully reversible.