You will not get ad-blocked impressions back by out-engineering the blockers. What recovers revenue is a mix of four things: measuring the loss honestly, giving blocked readers a fair way to support you, moving the formats that can move server-side, and running a clean enough stack that fewer readers reach for a blocker in the first place.
Below: how ad blockers work in 2026, what they cost, how to measure your own block rate, the recovery tactics that hold up, and how blocking quietly distorts the reporting you run your business on.
What is an ad blocker and how does it work?
An ad blocker is a browser extension, a browser setting, or a network-level filter that stops advertising from loading. Most work from community-maintained filter lists such as EasyList: the blocker checks every script, network request, and page element against the lists and prevents the matches from executing. Google Publisher Tags, Prebid.js, most SSP endpoints, and most measurement pixels are on those lists.
Four things typically happen on a blocked page:
- Request blocking: ad and tracking requests never leave the browser, so no ad request reaches your ad server.
- Element hiding: the containers where ads would render are collapsed, so the layout closes up as if the slot never existed.
- Tracking prevention: analytics and attribution pixels are blocked, so the visit may be invisible to your analytics too.
- Domain blocking: domains known for malware or aggressive redirects are blocked outright, which is why supply-chain hygiene matters here.
The landscape shifted in 2025 when Chrome completed its move to Manifest V3, which limits how extensions can filter requests. The most powerful blocker, uBlock Origin, left the Chrome Web Store, and its lighter replacement blocks less. Firefox and Safari were unaffected, and network-level blockers were never extensions to begin with. The practical result is more variety in how thoroughly a given reader is blocked, not fewer blocked readers.
What do ad blockers cost publishers?
Statista estimated that US publishers lost $12.12 billion in ad revenue to ad blocking in 2020, up from $3.89 billion in 2016. The figure is old, but the shape has not changed: block rates run from single digits on general-interest mobile audiences to well over a third on technology, gaming, and developer sites, and on desktop more than on mobile. Your own number matters more than any industry average, and it is measurable.
How to measure your block rate
- Detect the block on page. Load a small script from a path that filter lists block (any file name containing "ads" tends to do it) and record whether it executed. Send the result to your analytics as a custom dimension. Because analytics itself may be blocked, a server-side beacon on a first-party path is more reliable than a client tag.
- Compare page views with ad requests. Per section and device, divide GAM ad requests by analytics page views. The ratio is your effective monetized share; its complement is your block rate plus whatever else prevents requests (lazy-loaded units that never came into view, for instance).
- Segment it. Block rates vary by section, device, browser, and country far more than by month. A single site-wide number hides the fact that your technology section on desktop Firefox may be 45% blocked while mobile Safari on the news section is under 10%.
How can publishers recover revenue lost to ad blockers?
1. Offer blocked readers a fair exchange
Readers who block ads are usually your most engaged and most technical. A polite, non-blocking message that explains the content is ad-funded and offers two exits, allow ads on this site or take an ad-free subscription, converts a real minority. Hard walls convert more of the readers who stay and lose more of the ones who leave; test the wall on a section before rolling it out. Whatever you choose, keep the message off pages where readers arrived from search for the first time.
2. Move video ads server-side
Server-side ad insertion (SSAI) stitches the ad into the video stream on the server, so the player receives one continuous stream and client-side blockers cannot separate ad from content. For publishers with sizeable video inventory this is the single largest recoverable slice. It changes measurement, so plan the verification and viewability reporting with your demand partners before switching.
3. Use formats that survive element hiding
Native placements built into the content template, and sponsored content served first-party, are less exposed than standard display slots. They will not replace display revenue, but they hold up on blocked page views and tend to perform well on the engaged audiences that block.
4. Keep the domain off the wrong lists
Blockers and browser protections escalate on domains associated with redirects, malware, or deceptive formats. A clean ads.txt, authorized resellers only, and refusing creative types the Better Ads Standards flag keep your domain from being treated as hostile. For networks running Multiple Customer Management, keep child sites' compliance from spilling onto the parent seat.
What about "ad reinsertion" vendors?
Services that re-serve ads through first-party paths on blocked page views exist, and most operate within the Acceptable Ads framework, which limits them to specific formats and takes a share of the recovered revenue. They can add a few percent for publishers with high block rates. Read the format restrictions and the revenue split before assuming the headline recovery rate applies to you.
How ad blockers distort your reporting
This is the part that costs ad ops teams the most time and gets the least attention. Blocked requests never reach Google Ad Manager, so:
- Page views and impressions drift apart, and the gap changes with audience mix. A traffic spike from a technical audience can show up as flat ad revenue and get investigated as a demand problem.
- eCPM looks healthier than the business is. Blocked readers are removed from the denominator, so per-impression metrics rise while revenue per reader falls.
- Attribution breaks. Analytics pixels are blocked alongside ads, so the readers you cannot monetize are also the ones you cannot see, which flatters engagement metrics on the readers that remain.
The fix is a habit: watch the ratio of ad requests to page views per section alongside revenue, so a revenue move can be attributed to traffic mix, demand, or the stack before anyone opens a ticket.
Where Optimon fits
Optimon reads your Google Ad Manager and Prebid data and tells you what changed and why, from a rule that slipped to a partner that stopped bidding. It will not bring blocked impressions back, but it keeps the rest of the stack from leaking while you work on the audience side, and it separates a demand problem from a traffic-mix problem before the morning is gone. To see how your setup looks from a reader's browser, the free site audit on optimon.io scores it from a real visitor's vantage point.
FAQ
Can Google Ad Manager bypass ad blockers?
No. Google Publisher Tags and the ad requests they make are on the standard filter lists. Recovery comes from server-side ad insertion for video, first-party formats, reader value exchange, or Acceptable Ads-compliant reinsertion, not from the ad server itself.
What percentage of users block ads?
It depends heavily on audience. General-interest mobile audiences often sit in single digits; technology, gaming, and developer audiences on desktop can exceed a third. Measure your own rate per section and device rather than relying on an industry average.
Did Chrome's Manifest V3 end ad blocking?
No. It reduced what extensions can do in Chrome and pushed the strongest blocker out of the Chrome Web Store, but lighter blockers remain, Firefox and Safari were unaffected, and network-level blocking never depended on extensions.
Should I show a message to ad-block users?
A polite message with a clear choice, allow ads or subscribe, recovers a real minority and rarely costs traffic. A hard wall recovers more per reader who stays and loses more readers; test it on one section first and keep it away from first-time search visitors.
