Turn your push subscribers into recurring ad revenue.

Web push monetization is the practice of showing paid ad notifications to a website's opted-in push subscribers in exchange for revenue share. Publishers earn per impression and per click; subscribers receive timed, frequency-capped notifications that respect their attention. Unlike display ads, push reaches users after they leave the site.

Publishers add one JavaScript snippet to their site; dlserve handles subscriber opt-in, push delivery, frequency tuning, and revenue reporting end to end. Each subscriber is scored hourly so sends happen when they're most likely to convert. No infrastructure runs on the publisher's side beyond the snippet.

Earnings depend on subscriber engagement, geography, and category — typical US web-push CPMs range from $0.50 to $3 per thousand impressions across the industry, with click rates of 1–5%. dlserve does not publish per-subscriber averages on the public landing; we share modelled estimates during onboarding once we know your audience.

Yes — push runs in the browser notification surface, completely independent of any display ads on your pages. Subscribers see push only when they're not on your site, so the two channels don't cannibalise each other. Most publishers use push alongside display, video, and affiliate revenue.

A good opt-in rate for web push is 5–15% of unique visitors, with content sites usually higher than commerce. The rate depends on prompt timing, prompt copy, and the value proposition you make to the visitor. dlserve's SDK supports timed and trigger-based prompts so you can A/B the cadence that fits your audience.

iOS Safari push is not supported in the dlserve MVP. Apple shipped web push for iOS in 2023 but only for sites the user has installed to the Home Screen — a much smaller surface than Chrome/Firefox/Edge on desktop and Android. We support the major browsers that account for the vast majority of US web-push impressions; iOS support is on the post-MVP roadmap.

dlserve collects only what's required to deliver push notifications: the W3C Push subscription endpoint, the cryptographic p256dh and auth keys (these are not personal), and the subscriber's IP and User-Agent captured only at subscribe time and on telemetry events. We do not collect names, emails, browsing history off your site, or any personal identifier of the subscriber.

Send frequency is decided per subscriber by a scoring service that recomputes every hour. The score weighs recent engagement, time since last click, time-of-day patterns, and a per-channel cap configured by the publisher. Subscribers who engage receive more sends; subscribers who churn drop in priority before they unsubscribe.

Most publishers integrate dlserve in under an hour: drop one script tag at the bottom of the page, upload a generated service worker file to your site root, and verify the opt-in prompt in your dashboard. The dashboard walks you through every step and confirms the snippet is live. Production traffic flows through dlserve from the next page view.

dlserve is US-only in the MVP. The platform is engineered to scale geographically, but the alpha is scoped to US-targeted publishers and US subscriber traffic so we can run with one demand profile, one regulatory posture, and one round of operational learnings. International support is on the post-MVP roadmap.