What Are Web Push Notifications? Do They Still Work in 2026?

You're browsing a site, doing your own thing, and out of nowhere a small alert pops up on your screen - no tab open, no email involved. That's web push. It's become one of the go-to ways for online stores to bring shoppers back without ads or an app.

But with browsers cracking down harder on notification permissions every year, a fair question comes up: do they still work in 2026? Short answer: yes, if you know what they're actually good at and where they fall short. That's exactly what this piece walks through.

What Are Web Push Notifications & How Do They Work?

Understanding Web Push Notifications

A push notification for a website is a small pop-up that shows up on a visitor's screen - desktop or mobile - straight from their browser. No app to download, no inbox to check.

Image source: Pushpad

Every web push notification is made of the same few pieces:

1. Title - the headline of the message
2. Description - a short line of body text
3. Icon - usually your logo
4. Image (optional) - a larger visual, sometimes called a "hero image"
5. CTA button (optional) - a clickable action, like "Shop Now"

The structure stays the same across every use case - what changes by industry is how those five pieces get filled in. Our push notification template breaks down into variants so you're adjusting an existing one rather than building the format from zero.

Web Push vs App Push vs Email

There are three common channels for re-engaging customers after their first visit: web push, mobile app push, and email. Web push runs through the browser, mobile app push runs through a dedicated app like a banking or delivery app, and email runs through an inbox. Here's how the three line up side by side.

• Choose Web Push when: You run a small-to-medium ecommerce store without an app, you have a limited budget and want something quick to set up, or your audience mostly browses on desktop or Android.

Image source: Sleeknote

• Choose App Push when: You already have an app as a core sales channel, you need to send sensitive real-time alerts like OTP codes or delivery tracking, or iPhone users make up a large share of your revenue.

Image source: Pushwhoosh

Lean on Email when the message needs more than a headline — a product story, multiple images, detailed terms — or when you're building a longer-term relationship rather than prompting an immediate action.
Most stores don't pick one over the others — they run web push alongside email, each covering the gap the other leaves. Deciding exactly which message goes where is its own question, and it's exactly what our breakdown of email vs push notifications walks through.

How Do Web Push Notifications Work?

Here's the process in four steps:

1. Ask for permission - a prompt appears asking if the visitor wants to receive notifications.

2. They click "Allow" - their browser saves that permission.

Image source: PushPushGo

3. You send a message from your push notification tool.

4. It appears on their screen - even if they're not on your site right now, as long as their device is on and the browser is running in the background.

Even if they're not on your site right now. As long as their device is on and the browser's running in the background, boom - your message shows up.

Hard Opt-in vs Soft Opt-in: How You Ask for Permission

Step 1 isn't one thing - it's a choice between two very different approaches, and that choice quietly decides how big your subscriber list ever gets.

• Hard opt-in fires the browser's native "Allow / Block" prompt the instant someone lands on your site. It's fast, but it's also unforgiving: a first-time visitor with zero context for who you are is far more likely to hit "Block" out of pure reflex - the same reflex that's been trained by every other site that's interrupted them with a prompt before. Once that happens, the decision is permanent. No browser lets you ask that person again on that device.
• Soft opt-in shows your own message first - something like "Get instant sale alerts for your favorite items" - and only shows the native browser prompt to people who click through on that. This filters out the knee-jerk blockers before they ever reach the point of no return, and it means you can wait for a real signal of interest - time on site, a product view, an item added to cart - instead of asking the second someone arrives. It's why most stores that build a real subscriber list end up here rather than sticking with the hard opt-in.

The practical difference shows up exactly at the moment of that click: someone who's already spent a minute browsing, or just added something to their cart, has a reason to say yes. Someone who's seen a prompt fire before they've even scrolled has no reason to say anything but no.

Is It Legal? Opt-in Prompts as Consent

Web push is consent-based by design: nobody gets messaged without clicking "Allow" first, and no email or phone number is collected just to subscribe someone.

That said, don't assume "no personal data" means no compliance obligations, especially if you have EU customers. Once someone opts in, their browser is assigned a unique ID so your platform knows which device to message - and under GDPR, that ID counts as personal data, even without a name attached to it. 

Most push tools built for Shopify handle this compliance layer on their end, but it's worth confirming with whichever app you choose rather than assuming it's automatically covered.

Two Ways to Send Notifications

What Are Types of Web Push Notifications for Ecommerce (With Real Examples)

In ecommerce specifically, that behavior-based triggering shows up at a handful of predictable moments in the shopper's journey - the cart they didn't finish, the item they were waiting on, the price they were hoping would drop, the sale they didn't want to miss. 
Each of those moments has become its own type of web push notification, with its own trigger and its own timing. Here's what that looks like in practice.

Cart Abandonment

This is the one most stores start with, and for good reason: when someone adds items to their cart and leaves without checking out, they're not a cold lead - they were 90% of the way to buying. Fire the first reminder within 15–30 minutes while that intent is still warm, and if it goes unanswered, a second nudge around the 24-hour mark often catches people who just got distracted.

In practice, that might read as something like

• "You left something behind! Your cart is waiting - grab it before it's gone,"
• Lean on urgency with "⏰ Your cart won't hold forever - complete your order for [Product]."
• A small incentive works too: "Still thinking it over? Here's 10% off to help you decide."

Back-in-Stock

Popular items that sell out and come back are one of the easiest wins in ecommerce, because the demand is already proven - you're not trying to convince anyone, just reminding them the thing they wanted is available again. The catch is speed: send this the moment inventory updates, since a popular restock can sell out a second time within hours.

• Something like "Good news - [Product] is back in stock! Grab yours before it's gone again" does the job
• Add a bit of scarcity with "Limited restock - only a few left of [Product]."

Flash Sale / Event

Unlike the two above, this one isn't triggered by what an individual shopper does - it's tied to the calendar. You send once when the sale goes live, then once more a few hours before it ends, which concentrates traffic and urgency into a short window instead of letting it trickle in over days.

The tone here is usually more direct: "24 hours only - 30% off sitewide. Ends tonight," or, closer to the deadline, "Last call: 3 hours left to save 30%."

Price Drop

For shoppers who viewed or wishlisted something but didn't pull the trigger at full price, a price-drop alert can be exactly the nudge that gets them back - these are people who were price-sensitive, not uninterested. Send it the moment the price actually changes; waiting even a day means someone else might grab it first.

• Something simple works fine here: "Price drop: [Product] is now $10 off".
• A bit more personal: "Still on your list? [Product] just dropped to $XX."

Welcome / Onboarding

The very first message someone gets right after subscribing does more work than people give it credit for - it sets the tone for whether they stay subscribed at all. Send it immediately, while their interest in you is at its peak, and use it to build a little trust and, often, nudge a first purchase.

• A common pattern: "Welcome! Here's 10% off your first order,"
• Paired with something that manages expectations, like "You're in - expect deals and restock alerts, no spam."

Do Web Push Notifications Work on Every Browser and Device?

Web push notifications look solid on paper - but the real picture depends heavily on which browser, and which device, your shoppers are using.

Firefox and Edge: Full Support, No Extra Steps

These are the easiest browsers to work with - no special conditions, no workarounds.

• Firefox - supported since version 44+, full functionality out of the box.
• Edge - supported since version 17+, runs on the same engine as Chrome, so it inherits the same broad feature set.

Visitors on either browser see the standard "Allow" prompt and that's it - no Home Screen installs, no extra hoops.

Image source: OneSignal

Chrome: Full Features, But Increasingly Strict Rules

Chrome (50+) offers the fullest feature set of any browser - images, action buttons, the works - and it's still where the large majority of web push subscribers come from. It's also the browser that's gotten sharply stricter since 2023, automatically revoking permissions and throttling delivery for sites it flags as low-value or abusive - and by 2026, Google reported these defenses were blocking over 7 billion such notifications a day on Android alone.

What actually gets a site throttled. Chrome doesn't just look at volume - it weighs three signals together:

1. How many notifications you send relative to how much time people actually spend on your site
2. How often you show permission prompts relative to session length
3. How much genuine engagement (foreground time, clicks) your site gets overall

Score poorly on that combination, and Chrome caps you at 1,000 messages per minute - anything past that limit simply doesn't go through. For a list of 100,000 subscribers, that turns a broadcast that used to take seconds into something that can take well over an hour.

The takeaway: a sending habit that works fine on day one can quietly get throttled by month three if engagement doesn't keep pace. Send less, but send smarter - and treat this as a planning constraint from the start, not a surprise to react to later.

Safari and iOS: Support With a Catch

The catch: iPhone visitors can't just click "Allow" like on desktop. They first have to add your site to their Home Screen, then the permission prompt appears. That's an extra, unfamiliar step for most shoppers - and it's fair to assume a large share of iPhone visitors will never complete it, however clearly it's explained on the page.

If a meaningful chunk of your traffic is on iPhone, check your Shopify analytics before betting your strategy on this channel alone. For iOS-heavy stores, app push or email/SMS will often reach more of that audience than web push ever will.

Even on browsers with full support, a few constraints apply no matter which one you're using:

• Subscriptions don't move with the person.

Switch browsers, or get a new phone, and that subscriber has to opt in again. There's no carry-over like there is with email.

This has a practical side effect: your subscriber count can look bigger than your real audience. The same person on a laptop and a phone counts as two separate subscribers — Shopify can't merge them into one profile the way it does with email.

• Character limits are tight and inconsistent across browsers.

Treat these as a snapshot, not a fixed spec — they shift as browsers update. The safe rule: keep titles under ~40 characters. Don't put anything critical in the body text either, since overflow gets cut with "…" instead of wrapping to a new line.

Images and action buttons aren't universal either. A notification built and tested in Chrome may show up as plain text somewhere else.

• Ad blockers block silently, with no error on your end.

Some of the people in your subscriber count opted in but will never actually see a message. There's no way for your dashboard to tell the difference.

And once someone's blocked notifications, there's no coming back the easy way. Unlike an unengaged email subscriber, they'd have to manually change a browser setting to start seeing your messages again.

What Are the Benefits of Web Push Notifications?

Web push holds a real edge over both channels in three places that matter most for ecommerce - store owners leveraging Shopify push notifications: it's easier to get someone to opt in, it costs nothing extra per message, and it delivers the instant a shopper needs to see it - no inbox, no carrier fee. Here's the side-by-side breakdown:

• No single channel wins outright - web push sits in the middle: faster and cheaper to reach someone than SMS, more attention-grabbing than email, but with less room to say much once you have their attention. That's exactly why it works best as an addition to email/SMS, not a replacement for either. Most stores end up running both, which raises the real question: which message goes? Our breakdown of email vs push notifications walks through exactly that split.
• Easy to personalize and segment - instead of blasting the same message to everyone, you can group subscribers by what they've browsed, what's sitting in their cart, or where they're located, and let automation handle the timing. A cart sits untouched for 20 minutes? A reminder fires on its own. An item comes back in stock? The subscribers who wanted it get notified the moment it happens, not whenever you next log in to send a blast.

When Web Push Backfires: Why Users Opt Out and How to Prevent It

Consider a common pattern: a store runs a big sale and sends four notifications a day for a week straight. By the end of that week, opt-outs spike - and once someone blocks notifications from a site, there's rarely a way to win them back short of asking them to change the setting manually themselves.

The usual causes are predictable: too many notifications, poor timing (nobody wants a promotional alert at 6 am), and content that isn't relevant to that specific subscriber.

The fix is less about volume and more about targeting:

• Segment by behavior instead of broadcasting to your whole list
• Cap how many promotional sends go out per week (2–3 is a reasonable ceiling - beyond that, opt-outs climb sharply)
• Reserve the highest-frequency notifications, like flash sales, for the moments that actually justify urgency
• Keep transactional messages (order confirmations, shipping updates) separate from promotional ones - they don't count against the same "annoyance budget"

How to actually avoid it:

• Cap promotional sends per week - treat 1–2 broadcast/promotional notifications a week as a ceiling, not a starting point.
• Lean on triggered notifications over broadcasts. Cart abandonment, back-in-stock, and price-drop alerts are inherently more relevant to the individual receiving them than a sitewide blast, so they carry a much lower opt-out risk per send.

Image source: XFlow workflow

Reserve high-frequency sending for genuine exceptions - a flash sale with a hard deadline justifies two sends in the same day; a routine restocking notice does not.

Watch engagement, not just subscriber count. A shrinking click rate is an earlier warning sign than a subscriber-count drop - by the time people are actively opting out, you've likely already been over-sending for a while.

FAQs about Web Push Notification

Is web push notification a more effective marketing tool than email and SMS?

Not exactly "better" - more like a different tool for a different moment. Web push tends to win on speed and click-through rate for short, urgent messages. Email still wins for longer, detailed content and relationship-building. Most successful stores use both together.

What is the Web Push API?

The underlying web technology - standardized by W3C - that lets a website message a browser even when the tab isn't open. You don't need to understand it to use it; platforms like OneSignal or PushEngage handle it behind the scenes.

Can I create web push notifications without coding?

Yes. Most push notification apps, including several built for Shopify specifically, run entirely through a dashboard - no developer needed.

Why did my notifications suddenly stop reaching some subscribers?

More common in 2026 than before: Chrome now automatically revokes permissions for people who haven't engaged with a site in a while, or for sites sending too much with too little response. Shrinking delivery numbers are often a sign to slow down and get more targeted, not to send more.