Web Push for Publishers: Build a List That Earns After the Visit

Almost every monetization format has the same limitation: it only earns while someone is on your page. They leave, and the earning stops. Web push is the exception. A visitor who subscribes becomes an asset you can reach — and earn from — for months after that first visit. That is why web push monetization behaves less like a banner and more like an email list that pays its own bills.

This guide covers how it actually works, how to install it, how to ask for permission without wrecking your UX, and what it pays.

What makes web push different

A web push subscriber is a real browser-level permission. Once granted, notifications can be delivered to that browser whether or not the person ever returns to your site. The economics follow from that one fact:

• Banner revenue is a flow. It tracks today's traffic. A slow week is a slow week.
• Push revenue is a stock. It tracks your accumulated list. A slow week still earns, because last month's subscribers are still reachable.

That is why push tends to compound. Every visit that converts into a subscriber raises the floor of what your site earns next month, independent of whether that visitor ever comes back. It is the closest thing to owning an audience without owning an inbox.

How it works under the hood

Two pieces, and browsers are strict about both.

The service worker

Browsers require the code that receives a push to live on your origin — it cannot be loaded from someone else's domain. So you host a single file at your domain's root, and its entire contents are one line importing Adgora's worker:

importScripts('https://ad.adgora.net/push/sw.js');

That keeps the browser's security model happy while the actual logic stays maintained by the network, so you never have to update it.

The tag

On your pages you add the push snippet and declare which zone the subscriber belongs to. That snippet handles the subscription flow and registers the subscriber against your zone so the earnings land in your balance.

The subscription itself is a real, encrypted browser push subscription — the same standard your bank's web app uses — not a fake in-page toast pretending to be a notification. That distinction matters: real subscriptions reach the user after they leave, which is the entire point.

The permission prompt is the whole game

Everything about web push economics reduces to one moment: whether the visitor clicks Allow. And the single most common mistake is firing that prompt the instant someone lands.

Think about what you are asking. A stranger who has read nothing is being asked for permanent access to their notification tray. The rational answer is Block — and Block is not a "maybe later." It is a permanent no for that browser, and you cannot ask again. Every hasty prompt does not just fail; it permanently destroys that subscriber.

What works instead:

• Earn the ask. Wait until they have scrolled, spent time, or returned — until there is a reason to want more from you.
• Say why. A short pre-prompt explaining what they will receive converts far better than the naked browser dialog.
• Ask once, well. One well-timed ask beats three desperate ones, because the browser only gives you one real chance.

Opt-in rate is the metric that decides your push revenue for the next year. Treat it accordingly.

How advertisers reach your subscribers

Advertisers buy push on CPC or CPM and target the subscribers they want. When someone subscribes on your site, geo, device, operating system, and browser are captured, so an advertiser can aim at, say, Android users in Germany — and the message they receive is relevant instead of random. Relevance is what keeps subscribers subscribed, which protects your asset.

A frequency cap governs how often any one subscriber can be sent an ad, so your list is not burned for a short-term spike. Dead subscriptions — people who cleared their browser or revoked permission — are pruned automatically when the push service reports them gone, so your list stays honest rather than inflated with numbers that cannot be reached. From the advertiser's side of the same system, see push notification ads.

What it pays, and how you get it

Publishers keep a straight 70% revenue share on push, the same as every other format, credited as sends and clicks are billed. Withdraw from a $10 minimum to a TON wallet in TON or USDT — the mechanics are in the publisher payouts guide.

Read push revenue alongside your other formats using eCPM, but remember it is measured differently: banner eCPM is revenue per thousand impressions of today's traffic, while push revenue is a function of a list you built over months. A site with modest traffic and a well-grown list can out-earn a busier site with none.

A sane rollout

1. Host the one-line service worker at your domain root.
2. Add the push snippet with your zone.
3. Delay the prompt until the visitor has engaged — then explain the value before you ask.
4. Watch opt-in rate first, revenue second. The list is the asset; revenue follows it.
5. Keep your other formats running — push complements them, it does not replace them.

If you have not set up monetization at all yet, start with the website monetization guide, then layer push on top. Create a publisher account to get your push zone, or see what the network offers on the publisher overview.

Key takeaways

• Web push turns a visit into an asset — subscribers earn after they leave, so revenue compounds with list age.
• Install is two pieces: a one-line service worker on your own domain plus the zone snippet. Browsers require the worker on your origin.
• The permission prompt decides everything — never ask on arrival; a Block is permanent.
• Subscriber geo/device/OS/browser enable relevant targeting; a frequency cap protects your list from burnout.
• Dead subscriptions are pruned automatically, so your list stays real.
• Straight 70% share, $10 payout floor, settled in TON or USDT.