Push traffic is the clickable notification format that lands a short ad — an icon, a headline, a line of copy — straight onto a user's screen, on desktop or mobile, even when they are nowhere near the website they subscribed to. For affiliates it is one of the cheapest, fastest ways to buy volume, which is exactly why it rewards discipline and punishes lazy campaigns.
The appeal is simple: enormous reach at very low cost per click, a self-serve buying model, and near-instant feedback on whether a creative works. The catch is that push audiences are broad and cold, quality varies wildly between networks, and the format itself is in the middle of a structural shift as browsers clamp down on classic push in favour of in-page push. This guide covers how the format works, the two flavours you will buy, the economics behind them, the verticals that fit, the 2026 Chrome rate-limit reality every buyer is now navigating, and how to target and stay compliant. If push is new to you, start with traffic sources explained for where it sits among the other channels.
Push advertising is built on a subscription. A publisher — a content site, a downloader, a streaming portal — shows a small browser prompt asking the visitor to allow notifications. When the user clicks "Allow", their browser token is added to the publisher's subscriber base, or pooled into the push ad network the publisher works with. From that moment the user can receive notification ads, delivered by the browser or the operating system, without ever returning to the original site. Delivery is resilient: if the device is offline, the message queues and appears the next time the user comes online.
As an affiliate you do not build that subscriber base yourself. You buy access to it. You upload a creative — icon, title, description, sometimes a large image — set your bid, choose your targeting, point the click at your landing page, and the network fans your ad out to matching subscribers. Because the user already opted in to some notifications, push sits in an unusual middle ground: warmer than a random display impression, but far colder than someone who searched for your product. That gap is the whole reason bridge pages and pre-sell content matter so much on push, a discipline it shares with native ads.
There are two formats that look almost identical to a user but work very differently underneath. Classic push is a true browser or OS notification sent to a subscribed device — it can arrive when the browser is closed and relies on the subscription token. In-page push (sometimes called in-page notification or "web push lookalike") is not a real notification at all: it is a banner styled to resemble one, served while the user is actively on a publisher's page. Because in-page push does not need a subscription, it reaches iOS and Safari users that classic push cannot, and it is not exposed to browser-level notification limits.
| Dimension | Classic push | In-page push |
|---|---|---|
| Delivery | Real browser/OS notification, device can be idle | Banner shown while user is on a page |
| Needs subscription? | Yes — opted-in token | No — served to live visitors |
| Device reach | Android & desktop mainly; limited on iOS/Safari | Broad, including iOS & Safari |
| Audience temperature | Warmer — user chose to subscribe | Colder — user did not opt in |
| List fatigue | Real risk — stale subscribers, higher bots | Lower — always live traffic |
| Browser rate limits | Exposed to 2026 Chrome limits | Not affected by Push API limits |
For years classic push was the default and in-page was the fallback. That balance is now reversing, and understanding why requires looking at both the economics and the 2026 browser changes below.
Push is bought almost entirely on CPC — you pay per click, not per impression, which keeps the downside contained while you test. Bids are among the lowest of any paid channel: entry clicks in cheap tiers can start well under a cent, while premium GEOs command far more. That low floor is the format's superpower and its trap. Cheap clicks make it easy to gather statistically meaningful data fast, but they also attract low-quality inventory, bot activity, and subscribers who clicked "Allow" by accident years ago. The headline CPC means little on its own; what matters is your cost per conversion after the junk is filtered out.
The subscription model also has a hidden decay. A classic push list ages: subscribers churn, devices die, and the freshest tokens — usually the first few days after opt-in — convert far more than tokens that are months old. Good networks let you target subscriber freshness and activity for exactly this reason. Judge every push campaign on real return, not the raw click price, and lean on traffic quality analysis to separate networks that sell you fresh, human clicks from those recycling exhausted lists.
Push rewards offers with a broad appeal, a simple value proposition, and an impulse trigger — the format gives you a headline and an icon, so anything that needs heavy explanation struggles. It has historically performed on nutra and health angles, e-commerce and product-of-the-day offers, finance lead generation, sweepstakes and prize flows, dating, VPN and utility software, crypto, and app installs. What these share is a low-friction action and a message that fits in a notification. Because the audience is cold and broad, the creative and the angle do most of the heavy lifting — the same offer with a curiosity hook versus a benefit hook can differ several times over in conversion rate. Match the offer's complexity to the format before you blame the traffic.
This is the change reshaping push right now, so it is worth stating precisely. Beginning in January 2026, Chrome started rolling out Push API rate limits aimed at sites that send large volumes of notifications with little genuine user engagement. Chrome scores a site daily on how many push messages and permission prompts it produces relative to time users actually spend there. Sites flagged as disruptive get throttled, with an escalating penalty — roughly a one-day limit on first offence, seven days on the second, fourteen on a third, and a reset only after a long stretch of clean behaviour.
Two points are widely misread, so flag them as the current understanding — details may still shift as the rollout matures. First, Google has framed this as targeting abusive publishers, not advertisers: the limit hits the sending site's Push API, and Google's own guidance says nearly all sites are unaffected because the threshold is high and only excessive, low-value senders trip it. Second, notifications sent while a site is open via the Notifications API are not covered, and in-page push is untouched because it never uses the Push API at all. The practical effect for buyers is a steady shift of budget and inventory toward in-page push and toward networks whose publishers keep engagement healthy. Do not treat classic push as dead — treat it as a channel where list quality now has teeth, and diversify so a single browser change cannot wipe out a campaign, a habit covered in managing campaign risk.
Push targeting is broad by nature, so the discipline is in slicing the buy and cutting fast. The levers that matter most are GEO, device and operating system, browser, connection type, and — on the best networks — subscriber freshness and publisher-level source IDs. The winning workflow is to launch wide, let data accumulate cheaply, then blacklist the source IDs that spend without converting and whitelist the ones that do. Because clicks are so cheap, you reach significance quickly, but you must actually act on it: a push campaign left unpruned bleeds budget into dead inventory within days.
Creative refresh is the other constant. Push audiences fatigue fast — the same icon and headline that crushed in week one decays as the same subscribers see it repeatedly — so rotate creatives on a schedule rather than waiting for performance to collapse. Set your bid to buy enough volume to test without overpaying for premium placements you have not yet proven, then scale the winners. For the full launch-optimise-scale loop that applies here, see the campaign optimisation workflow, and revisit choosing the right traffic source if push keeps fighting your offer.
Push has a reputation problem it earned honestly: years of misleading creatives styled as system alerts, fake message icons, and "your device is infected" scare copy trained both users and browsers to distrust the format. That history is a large part of why Chrome built its rate limits, and why serious networks now police creatives. Keep your ads honest — no fake close buttons, no impersonating a chat or antivirus alert, no deceptive claims — because the platforms increasingly detect and reject these, and the deceptive angle that wins today gets your account and your offer banned tomorrow. Respect the advertiser's approved messaging, keep claims defensible in regulated niches like finance and health, and remember that clean creatives are now also a deliverability advantage, not just a legal one. If a term here is unfamiliar, the traffic glossary defines the vocabulary buyers use daily.
No — but it is changing. The limits target sites that send excessive, low-engagement notifications, not advertisers, and Google says nearly all sites are unaffected. The real effect is that stale, low-quality subscriber lists get throttled, so list freshness matters more and budget is shifting toward in-page push. Treat classic push as a channel that now demands quality, not a dead one.
Classic push is a real browser notification sent to a subscribed device even when the browser is closed; in-page push is a banner styled to look like a notification, shown while the user is actively on a page and requiring no subscription. In-page reaches iOS and Safari and sidesteps the Push API limits, which is why it is growing.
Because inventory is vast and audiences are cold and broad, priced on CPC that can start below a cent in low tiers. The low price is genuine, but it also attracts bots and exhausted subscriber lists, so your real cost is per conversion after filtering, not the click price on the dashboard.
Offers with broad appeal, a simple hook and a low-friction action — nutra, e-commerce, finance lead generation, sweeps, dating, VPN and utility software, crypto and app installs. Anything that needs a long explanation struggles, because a notification only gives you an icon, a headline and a line of copy.
A practical tour of affiliate traffic sources — native, social, search, push and in-app — with the strengths, costs and use cases of each.
Core · 12 min readThe mistake is rarely a bad traffic source — it is a good source pointed at the wrong offer.
Core · 11 min readNative converts — but not if you point cold clicks straight at an offer.
