Brief Summary

Push notifications (Web Push) are a fast channel that brings users back to a website and helps guide them toward an action: a purchase, a return visit, reading an article, making a payment, or registering.

Every time a marketer chooses a way to communicate with a potential customer or website visitor, they are balancing on a fine line between being intrusive and offering a helpful reminder. Let’s look at how to maintain this balance with push notifications (Web Push) and avoid losing subscribers because of an incorrect permission request.

Who should read this article:

• website owners and e-commerce businesses who want to increase repeat visits and conversion;
• marketers and SEO specialists who need to improve CTR and retention without irritating the audience;
• product managers and web developers who configure Web Push via Service Worker, VAPID, and analytics integrations.

What Are Push Notifications (Web Push) and Why Businesses Need Them

Web Push are notifications from a website that are delivered to the browser and shown by the system even when the tab is closed. The logic is the opposite of “email”: instead of you “pulling” updates, the website neatly “pushes” them based on an event.

Push notifications work on desktop and Android in browsers, and also on iPhone/iPad — but with an important limitation: Web Push is supported for web apps added to the Home Screen, not for regular website browsing in Safari.

A typical Web Push notification may include (the exact set depends on the OS and browser):

• a title and text (length limits vary);
• a brand icon/badge;
• a clickable link (a deep link to a specific page);
• action buttons (for example, “View,” “Remind Me Later,” “Add to Cart” — if supported);
• an image (rich notifications — in supported browsers).

FAQ for this section

Are Web Push and push notifications the same thing?

In the context of websites — yes. Usually, when people refer to push notifications in the browser, they mean Web Push specifically (Push API + Service Worker).

Can you send push notifications without the user’s consent?

No. Explicit opt-in is required: the user must personally grant permission in the browser/system.

How Web Push Works: Subscription, Service Worker, VAPID

Technically, Web Push relies on three things: a Service Worker (a background script), the Push API (subscription), and the Notification API (displaying the notification). During subscription, the browser creates a PushSubscription object: it contains an endpoint (the push service address) and encryption keys. To send push messages from the server side, VAPID keys are usually used (a public/private key pair).

Notifications can be delivered:

• via the browser (Web Push: website + Service Worker);
• via a mobile app (app push via FCM/APNs);
• inside the product (in-app notifications, banners, widgets, etc.).

In this article, we will only look at browser push notifications.

The first part of the process is collecting the subscription (opt-in). This is a system dialog in the format: “This site wants to send notifications: Allow / Block.” An important nuance for 2026: many browsers suppress “aggressive” permission requests. So the best approach is to first show a “soft” explanatory screen (pre-prompt) and only trigger the system request after the user clicks.

Web Push on iOS works only for web apps added to the Home Screen, and permission is requested only after user interaction. If you are planning push notifications for an iPhone audience, keep in mind that you first need to guide the user to installing the web app.

FAQ for this section

What are VAPID keys and why are they needed?

They are a cryptographic key pair used to identify your server when sending Web Push. The public key is sent to the browser during subscription, while the private key is stored on the server.

Can you do without a Service Worker?

No. A Service Worker is required to receive push events and display the notification, even when the site is not open in a tab.

Why are iOS pushes not arriving even though everything is set up?

Check that the site is installed as a web app on the Home Screen. Web Push does not work in regular Safari.

What Tasks Should Push Notifications Be Used For

Push notifications are a tool that supports business goals only when used as part of a strategy. Web Push is worth using when it is important to quickly communicate an event, and the message can fit into 1–2 sentences. The main rule: a push notification must be useful here and now, otherwise you will get blocks and unsubscribes.

Below are examples of scenarios that usually deliver the best CTR and conversion:

• online stores and marketplaces — abandoned cart, price drop, item back in stock, personalized selection, delivery status, payment reminder;
• media and blogs — publication of new content, a “best of the week” roundup, important news on subscribed topics;
• services and SaaS — task completion, report ready, billing status, deadline reminder, account changes;
• education — lesson/webinar start, homework reminder, access to a recording;
• recruitment — new vacancies based on filters, interview invitation, application status;
• finance — transactional notifications (if the channel meets the requirements), rates and limits, payment reminders.

FAQ for this section

Which push notifications usually deliver the best CTR?

Triggered and transactional ones: “your cart is waiting,” “the price has dropped,” “your report is ready.” Mass messages like “discounts for everyone” perform worse and burn out the audience faster.

Can promotional push notifications be sent?

Yes, but only with explicit consent and frequency limits. If push notifications look like spam, browsers will more often suppress permission requests, and users will start blocking the channel.

How to Ask for Permission, What to Write, and When to Send to Avoid Getting Blocked

Before implementing push notifications, answer three questions: how to ask for permission, what to write in notifications, and who to send them to—and when. To avoid losing a potential subscriber, both the permission request and the push notifications themselves should be unobtrusive and arrive at the right moment.

How to ask for permission

Asking for notification access right away is almost guaranteed to hurt conversion. Browsers are increasingly showing quiet prompts, automatically revoking permissions from inactive sites, and introducing anti-spam restrictions. So the goal is not to force permission, but to explain the value and give the user control.

Here are some practical subscription recommendations:

• Request permission after a click (button, checkbox, menu item), not on page load—this usually leads to a higher opt-in rate and fewer blocks.
• Use a pre-prompt: briefly explain the benefit (“we’ll notify you about price drops / order status / new articles on topics you follow”).
• Let users choose topics (for example: “promotions,” “order status,” “content”) and offer “quiet hours.”
• Add a preference center: turn off push notifications, change frequency, choose categories.
• Keep iOS in mind: Web Push on iPhone works for installed web apps, so it makes sense to first suggest installation and then offer the subscription.

What to write in notifications

Your push copy is your CTR. It should be short, honest, and lead to a specific action.

• One idea = one notification. Remove everything unnecessary, keep only the value and the action.
• Personalization: dynamic fields (name, product, city, category) and segmentation increase relevance.
• Clear deep link: send users to the exact screen/page they need (cart, product page, article), not the homepage.
• Metrics: add UTM tags and distinguish campaigns so you can see the contribution of push campaigns in GA4.
• Don’t overpromise: a mismatch between the notification text and the landing page quickly leads to blocks.

Who to send to — and when

If you clearly understand who your user is and why they need push notifications, you’re already one step ahead. Segment your audience by interests and behavior (categories, viewed products, engagement depth, visit frequency), then set the sending frequency and timing accordingly.

What matters most:

• Frequency limits: 1–3 useful pushes per week is better than daily discount blasts.
• Time zone and quiet hours.
• TTL (time to live): if an event becomes outdated quickly, use a short TTL so the user doesn’t get it a day later.
• Send-time optimization (if available on your platform): send during the window when the user is most likely to click.

FAQ for this section

When is the best time to ask for push notification permission?

After the user has already received some value: read part of an article, added a product to favorites, set up a filter, or signed in. And only after their click.

What sending frequency is considered safe?

There’s no universal number. Start with 1–2 pushes per week plus event-based triggers, and monitor the block/unsubscribe rate.

Do I need separate consent if I already have email consent?

Yes. Push is a separate channel, permission is granted in the browser, and the user should clearly understand exactly what you are going to send.

Web Push Analytics: Metrics, GA4, and Measuring Impact

If you’re not measuring the impact, a push campaign quickly turns into pushing just for the sake of pushing. Today, basic analytics is прежде всего about traffic quality and contribution to conversions.

• opt-in rate: the share of visitors who granted permission for notifications;
• CTR and button clicks (if you use actions);
• conversions (purchase, lead, registration) and CR by push source;
• traffic quality: engagement, page views, returns;
• negative signals: blocks, unsubscribes, complaints/abuse;
• reaction time: time-to-click, optimal send time;
• incrementality: how many conversions push actually generated, rather than simply intercepted.

You can collect statistics in different ways:

• platform reports (deliverability, clicks, unsubscribes, segments);
• GA4: UTM tags + events/conversions to see push contribution across the funnel;
• your own tracking: storing subscription statuses, impression/click events, holdout experiments (a control group that does not receive pushes).

FAQ for this section

Why aren’t clicks the main metric?

Clicks are easy to inflate with loud wording, but what matters to the business is conversions and traffic quality: purchase, lead, retention.

How do you measure impact correctly?

Use UTM tags, track conversions in GA4, and periodically run a control group test (where some subscribers do not receive pushes) to evaluate incrementality.

How to Reduce Negativity: Blocks, Unsubscribes, and Complaints

Negativity in a push channel shows up quickly: the user either blocks notifications or simply stops responding. Start with diagnosis: at which stage is interest being lost — during the permission request, when the notification is received, or after the click on the landing page?

What usually helps reduce negativity:

• An honest pre-prompt and requesting permission only after a click.
• Categories and settings (frequency, topics, “do not disturb”).
• Relevance: triggers and segments instead of sending the same thing to everyone.
• Spam protection: monitor complaints and don’t use push notifications as cheap advertising. Browsers are strengthening anti-spam mechanisms and may limit delivery.

FAQ for this section

Why do users block push notifications?

Most often because of early/intrusive permission requests and irrelevant mass campaigns without frequency limits.

Can a user be brought back after blocking?

Technically, only if they enable permission again themselves in the browser/system settings. That’s why prevention is better: control frequency and make sure every notification delivers value.

Services and Platforms for Push Notifications

Web Push tools can generally be divided into two approaches: SaaS platforms (quick start, segmentation, triggers, reports) and self-managed sending (your own server + a Web Push library, more control, more development).

How to choose a push notification service for a website

• Browser support and iOS limitations. Check how the platform works with Safari/iOS (a web app added to the Home Screen).
• Triggers and segments. Cart, category view, repeat visit, RFM segments, geo, etc.
• Frequency control and anti-spam. Frequency capping, quiet hours, unsubscribes, topic management.
• Analytics integrations. GA4, webhooks, CDP/CRM, UTM tags, event export.
• Migration and data ownership. Clarify whether you can export the subscription base and what happens if you switch providers.

FAQ for this section

Can you transfer a subscriber base from one service to another?

Often, no. A subscription is tied to the provider’s keys/endpoints and rules. In some cases, migration is possible by keeping the same VAPID keys and handling the transfer carefully, but this should be clarified before launch.

What should you choose: SaaS or your own server?

SaaS delivers results faster (segments, triggers, reports). Your own server gives you control and independence, but it requires development, security, and ongoing support.

Alternatives to Push: Email, SMS, Messengers, and In-App

And finally, let’s analyze the specifics of push notifications compared to their historical competitors — SMS and email campaigns:

• Speed. Push wins when timing matters: “cart,” “payment,” “price dropped,” “new content released.”
• Opt-in and control. Like email, Web Push requires consent. The difference is that permission is granted in the browser, and it’s easy to lose due to intrusiveness.
• Cost. Usually cheaper than SMS, but the cost depends on the platform and volume. Plus, there is also a “cost” in the form of the risk of a negative reaction.
• Platform limitations. On iOS, Web Push is tied to installing a web app on the Home Screen. In Chrome and other browsers, anti-spam restrictions and “quiet” permission prompts are increasing.
• Alternative channels. For many niches, email sequences, in-app notifications, and messengers (Telegram bots/channels) work well, while Web Push serves as a fast trigger-based channel within a broader mix.

Web Push is a strong channel if you use it as a service tool (value, frequency, segments), rather than as a banner replacement. And the stricter browsers become, the more important strategy quality and analytics are.

FAQ for this section

What should you choose instead of push if subscriptions are not converting well?

Check your email sequences and in-app notifications, and add a Telegram channel or bot for your постоянная audience. A combination of channels often works better than relying on just one.

Why do push notifications sometimes fail to arrive?

There are different reasons: the user disabled permission, the browser applied anti-spam restrictions, the TTL expired, or the device is in power-saving mode. Start with delivery diagnostics in the platform reports.

Can push be used for critical transactions?

For critical events, it’s better to duplicate the channel (email/SMS/in-app), because Web Push depends on permissions and browser policies.