Push Ads
Notification-style messages straight to the device.
Overview
Push ads are clickable messages delivered as notifications to a user's browser or device, styled to look like a native system notification with an icon, title, and short body. Users opt in by allowing notifications from a site, after which advertisers can reach them even when they're not actively browsing. They're prized for high visibility and re-engagement, but heavily dependent on genuine opt-in.
How it works
When a user grants notification permission to a website, a subscription token is created and stored with a push provider. Advertisers (via a push ad network) then send campaigns to these subscriber lists. The browser or OS displays the notification natively; clicking it opens the advertiser's landing page. Web push uses the standard Push API and service workers under the hood.
Common uses
- →App and site re-engagement
- →Flash sales and time-limited offers
- →Content and news alerts
- →Affiliate and performance campaigns
Pros & cons
Pros
- ✓High visibility — appears as a system notification
- ✓Reaches users outside the browsing session
- ✓Strong for re-engagement and retention
- ✓Bypasses traditional ad blockers
Cons
- ✗Requires explicit user opt-in
- ✗Easy to overdo and drive unsubscribes
- ✗Quality varies hugely across push networks
- ✗Tighter browser restrictions year on year
Live examples
Simulated mockup — illustrative, not a real ad
Web push opt-in & delivery
Step 1: site requests permission
↑ Walk through the opt-in → subscribe → delivery flow that powers web push ads.
Live ad — served by Google AdSense
And here's the real thing: an actual ad served into the page. What appears depends on the advertiser auction and your browser — it won't always match the format above.
Ad slot
Awaiting AdSense ad unit
Key metrics
Avg. CTR
1–5%
Pricing model
CPC or CPM
Opt-in rate
5–10%
Delivery
Even when not browsing
Advertisement
Ad slot
Awaiting AdSense ad unit