Push Ad Server
GoAdserver is a push ad server for publishers and push ad networks. Turn your visitors into push subscribers you own, earn from ads delivered to them after they have left your site, and sell push and web push traffic to advertisers under your own brand.
Collect your own subscribers
The Push Collector shows the browser’s permission prompt on your pages, and every visitor who allows notifications becomes a subscriber in your account. Two small files do the work: a service worker at the root of your site and a collector script, loaded from us or self-hosted so it keeps working for visitors with ad blockers. Every subscriber is stored with when and where they opted in, their language and, when they arrived on a tracked click, that click.
Segments and delivery rules
- Segments: group subscribers by traffic source, activity, opt-in age or whether they came from a tracked click, with a live count of who matches.
- Delivery rules: recurring notifications filled from the ad auction, run every few hours or once a day, with a frequency cap per subscriber and a maximum reach per run. This is where push revenue comes from.
- Your own campaigns: send your announcements to everyone or to a segment, and send them again later.
Every push format
Besides classic push notifications, GoAdserver serves push-style formats on the page itself: web push and native web push units with configurable position and item count, plus push click and native click zones. Advertisers buy them on CPM, CPC or CPA with the same targeting as every other format. See all formats on the ad formats page.
Run a push ad network
Push networks sign up publishers who collect subscribers and advertisers who buy the notifications. GoAdserver runs both sides in one white-label platform: self-serve campaigns with bids per country, creative approval, targeting by country, device, operating system, browser, language and time of day, real-time statistics for both sides, and payouts and invoices. Bot filtering runs on every request, and outside buyers and sellers connect over RTB.
Measure what each push earns
Push statistics show impressions, clicks, CTR and revenue from auctioned pushes, next to subscriber growth, so a collector that stops working shows up as a flat line. Conversions come back through postbacks and the built-in tracker, so advertisers see which pushes paid off.
How it works
- Create a push ad zone for each site.
- Install the collector: host the service worker at your site root and add the embed code to your pages.
- Grow your list: every visitor who allows notifications becomes a subscriber.
- Build segments by source and opt-in age.
- Switch on a delivery rule and earn from every auctioned push it sends.
What advertisers get
Push advertisers create campaigns self-serve: a title, a message, an icon and an image, the landing page and the bid, with separate bids per country where they want them. Creatives are approved before they run. Campaigns target by country, device, operating system, browser, language, connection and time of day, with frequency caps per visitor and daily budgets that pace delivery. Conversions come back through postbacks, so advertisers can buy on CPA as well as CPM and CPC, and see which notifications actually paid off in real-time reports.
Frequently asked questions
Do subscribers belong to me?
Yes. Subscribers are collected on your own sites and stored in your account, with their opt-in date, source and language.
Does the collector work with ad blockers?
Load it from your own site (self-hosted) and it keeps working for visitors who block third-party scripts.
How often should I send?
Once a day is plenty for most audiences. The frequency cap on each delivery rule keeps the same subscriber from being pushed too often.
Why do I need HTTPS for push?
Browsers only register the service worker that receives notifications on secure sites. On plain HTTP the permission prompt never appears, so every site that collects subscribers needs HTTPS, and every subdomain needs its own copy of the service worker at its root.
Good push practice, built in
- Frequency caps keep the audience from unsubscribing.
- Segments by opt-in age reach people while they still remember your site.
- Inactive subscribers are marked, and segments can leave them out.
- HTTPS only, as browsers require for push.
Want to see it on your own traffic? Talk with our team or compare the plans.
Documentation
Set it up step by step in the GoAdserver documentation: Push ads.