
To measure adblock revenue loss, multiply the pageviews you could have monetized by your measured block rate and your page RPM, then divide by 1,000, and do it separately for desktop and mobile: monthly loss = pageviews × block rate × page RPM ÷ 1,000. Your block rate comes from Google Ad Manager’s or AdSense’s Ad blocking extension rate (desktop only) or from your own bait test logged to GA4. For context, eyeo’s Ad-blocking report 2026 estimates 1.1 billion ad-blocking users in Q4 2025, about 30% of the internet population.
This page gives you the formula with a worked example, three ways to measure your own block rate (with code and exact GA4 and Ad Manager steps), the current statistics labeled by method and date, and the recovery options with their real tradeoffs.
The adblock revenue loss formula, with a worked example
Page RPM (revenue per 1,000 pageviews) already bakes in ad density, fill rate and eCPM, so you do not need to multiply those separately. If you only know eCPM, use ads per page × fill rate × eCPM as your page RPM.
Monthly adblock loss = Σ by device (monetizable pageviews × block rate × page RPM ÷ 1,000)
Three rules keep the number honest:
- Count pageviews from a source blockers cannot hide from. Server or CDN logs count everyone. GA4 undercounts, because tracking filters can stop the analytics request itself; Admiral, an adblock recovery vendor, warns that when analytics requests are blocked, reports can miss activity.
- Split by device. Google’s extension rate covers desktop page views only, and desktop and mobile RPMs differ, so one blended rate hides most of the error.
- Use the RPM of the traffic that is blocked. If blocked users skew toward a high-RPM country or section, your sitewide RPM understates the loss, and vice versa.
Adblock loss calculator worksheet (worked example)
The figures below are a hypothetical publisher with 1,000,000 monthly pageviews. Replace each input with your own numbers; the right column tells you where to find them.
| Input or step | Desktop | Mobile | Where your number comes from |
|---|---|---|---|
| A. Monthly pageviews | 400,000 | 600,000 | Server or CDN logs, split by user agent |
| B. Block rate | 25% | 10% | Desktop: Ad Manager or AdSense extension rate. Mobile: your bait test in GA4 |
| C. Blocked pageviews (A × B) | 100,000 | 60,000 | Calculated |
| D. Page RPM | $14.00 | $8.00 | Ad Manager or AdSense revenue ÷ (pageviews ÷ 1,000) |
| E. Monthly loss (C × D ÷ 1,000) | $1,400 | $480 | Calculated |
| Total monthly loss | $1,880 | E desktop + E mobile | |
| Annualized loss | $22,560 | Monthly × 12 | |
That $22,560 is a ceiling, not money you can get back. To estimate what is recoverable, apply two of your own inputs: the share of blocked pageviews you expect to win back (from Ad Manager’s Ad blocking recovery message conversions, or the Acceptable Ads share of your blocked traffic), and the RPM those recovered pages will earn. Recovered pageviews usually earn less, because the Acceptable Ads Standard excludes animated, expanding, overlay, pre-roll and rich media ads. In the example, if you win back 20% of blocked pageviews at 60% of normal RPM, the recoverable figure is $22,560 × 0.20 × 0.60 = $2,707 a year. Those two percentages are placeholders for the math, not benchmarks.
Vendor calculators exist, but they do not show their work. AdPushup’s adblock recovery calculator asks for monthly pageviews, ad density, eCPM and ad block rate. Admiral’s calculator returns conservative, typical and optimized scenarios from its own detection dataset. Neither page publishes the formula, so run the worksheet above alongside them.
Adblock measurement: three ways to get your real block rate
Every block rate depends on what is being detected. Pick the method that matches the question you are asking, and label the number with its method when you report it.
| Method | What it detects | What it misses | Effort |
|---|---|---|---|
| Ad Manager or AdSense Ad blocking extension rate | Desktop page views with an ad blocker extension installed | All mobile and tablet traffic; blocking that is not an extension | Paste one tag, wait for data |
| Bait element plus ad-request test, logged to GA4 | Cosmetic filtering and blocked ad-script requests, on any device | Visitors whose blocker also stops GA4 | About an hour, plus 24 to 48 hours for the dimension to populate |
| Server-log reconciliation | The gap between pageviews served and ad requests received | Cannot tell an ad blocker from an ad error or a timeout | Needs log access and a join by page and day |
Blockthrough, whose traffic data eyeo uses for its country rates, runs the bait approach at scale: its software requests a predefined array of “bait” URLs and infers a blocker when those requests are interrupted, according to the methodology in eyeo’s 2026 report.
Option 1: Google Ad Manager and AdSense ad blocking reports
Funding Choices, Google’s old messaging product, has moved into the Privacy & messaging tab of Ad Manager, AdSense and AdMob. That is where the ad blocking numbers live now.
In Google Ad Manager: click Reporting, then Reports, then New report, and change the Report type to “Privacy & messaging”. You can also click Privacy & messaging, click Manage on a message type card, then View reports on the metrics card (Google Ad Manager Help). That same help page says the legacy Reports tool is being fully deactivated in Q3 2026; the Privacy & messaging report is also listed as a report type in Interactive reports.
| Ad Manager metric | Google’s definition | Use it for |
|---|---|---|
| Ad blocking extension rate | Percentage of page views where users had ad blocker extensions installed. Desktop page views only. Mobile and tablet were removed in mid-February 2024, retroactively. | Your desktop block rate (input B) |
| Ad blocking recovery messages shown | Number of times a recovery message was shown | Denominator for recovery |
| Ad blocking recovery message conversions | Messages shown that resulted in users adding the site to their allowlist | Your recovery share |
| Allow-ads page views | Page views from blocker users who saw the message and later allowed ads | Recovered inventory |
| Allow-ads conversion rate (cookie-based) | Marked Deprecated; Google says it may not be accurate | Do not use |
The ad blocking metrics have no data for dates before you enabled them, so turn them on before you need the number.
In AdSense: go to Privacy & messaging and click Manage on the ad blocking recovery message card. The metrics card shows messages shown, extension rate and conversions aggregated over the last 30 days; Download reports gives a CSV you can split by device category, date, domain and operating system (AdSense Help). You must paste the ad blocking tag between the <head> tags of your site, and AdSense starts detecting ad blockers even if the message is unpublished: create the message and leave it in Draft to collect data without showing anything (AdSense Help).
Option 2: A bait element and ad-request test, logged to GA4
This catches mobile blocking, which Google’s extension rate ignores. It runs two checks: whether a decoy element with ad-like class names gets hidden by cosmetic filters, and whether a request to Google’s ad script fails. It sends the result to GA4 as an event using the standard gtag event syntax, which must load below the Google tag.
(function () {
function report(status, method) {
if (typeof gtag === 'function') {
gtag('event', 'adblock_check', {
adblock_status: status,
adblock_method: method
});
}
}
var bait = document.createElement('div');
bait.className = 'ad-banner adsbox ad-placement';
bait.style.cssText = 'position:absolute;left:-9999px;width:1px;height:1px;';
bait.innerHTML = ' ';
document.body.appendChild(bait);
window.setTimeout(function () {
var hidden = bait.offsetHeight === 0 ||
window.getComputedStyle(bait).display === 'none';
bait.remove();
if (hidden) { report('blocked', 'bait_element'); return; }
fetch('https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js',
{ method: 'HEAD', mode: 'no-cors', cache: 'no-store' })
.then(function () { report('not_blocked', 'ad_request'); })
.catch(function () { report('blocked', 'ad_request'); });
}, 300);
})();Put it in a script tag in your footer, or in a Google Tag Manager Custom HTML tag that fires after the Google tag. Then register the parameter in GA4:
- Confirm the event arrives: open your site, then check that
adblock_checkappears in GA4’s Realtime or DebugView. - In GA4, go to Admin, and under Data display click Custom definitions.
- Open the Custom dimensions tab and click Create custom dimensions.
- Dimension name:
Adblock status(no hyphens allowed; spaces and underscores are fine). Scope: Event. Event parameter:adblock_status. Scope and parameter cannot be changed after saving. - Click Save. You need Editor access or above at the property level (GA4 Help).
- Repeat for
adblock_methodif you want to see which check fired. - After 24 to 48 hours, build a report with Adblock status and Device category as dimensions and Event count for
adblock_checkas the metric. Block rate = blocked events ÷ alladblock_checkevents, per device.
Limits to know: event names and parameter names can be up to 40 characters, parameter values up to 100, and 25 parameters per event (GA4 collection limits). A standard property allows 50 event-scoped custom dimensions (GA4 Help). The built-in bias: users whose blocker also stops GA4 never send the event, so this method understates your block rate. Treat it as a floor and compare it with your server-side pageview count. If you want help wiring this into a broader reporting setup, the digital marketing analytics guide covers GA4 event design for service firms.
Option 3: Reconcile server pageviews with ad requests
No client code, and it counts the visitors GA4 misses. For each page and day, compare pageviews served (server or CDN logs) against ad requests or impressions recorded by your ad server. If a page serves 10,000 views with three ad slots and Ad Manager records 21,000 ad requests instead of the expected 30,000, the 30% shortfall is the upper bound of your block rate on that page. The weakness is that a slow ad load, a consent decline or a script error looks identical to a blocker, so use this to bound the number, not to report it.
How many people use ad blockers: 2026 statistics, labeled by method
Usage numbers fall into three families that are not interchangeable: vendor user counts, survey panels, and measured pageview rates. Quote the method with the number.
| Statistic | Figure | Period | Method | Source |
|---|---|---|---|---|
| Global ad-blocking users, all devices | 1.1 billion (about 30% of internet population) | Q4 2025 | Vendor estimate from Opera, Brave, AdGuard, Chrome-Stats and other data | eyeo 2026 |
| Growth in ad-blocking users | +13% since the 2023 report | 2023 to Q4 2025 | Vendor estimate | eyeo 2026 |
| Desktop ad-blocking users | 448 million, down 4% since 2023 | Q4 2025 | Vendor estimate | eyeo 2026 |
| Mobile ad-blocking users | 629 million, up 27% since 2023 | Q4 2025 | Vendor estimate | eyeo 2026 |
| Users in low and middle income countries | +23% since 2023, while higher income countries fell 14% | 2023 to 2025 | Vendor estimate | eyeo 2026 |
| Internet users who block ads at least sometimes | 29.5% (about 1.77 billion) | Q2 2025 | GWI survey, ages 16 to 64 | GWI via DataReportal, compiled by Backlinko |
| US internet users who block ads | 32.5% | Q2 2025 | GWI survey | GWI via DataReportal, compiled by Backlinko |
| Ad-blocking users in 2023 | 912 million, up 11% from Q4 2021 | Q2 2023 | Vendor estimate | eyeo/Blockthrough 2023 |
| Average measured adblock rate | 21% across 10B+ pageviews on 9,453 sites | Report published July 2022 | Pageview detection | Blockthrough 2022 |
The mobile share is the story. eyeo says most mobile ad-blocking users are in low or middle income countries, where people block to save data costs and speed up slow networks, while in higher income countries more browsers ship blocking as a default feature. eyeo counts anyone who “explicitly took action” to use a product with ad blocking (extension, browser, app, VPN or DNS), which is why its user count and Google’s extension-only rate will never match.
Ad block rate by country
eyeo’s 2026 report includes a 2025 reference table of ad block rates by country, headed as GWI Consumer Insights Platform data. Selected rows:

| Country | 2025 ad block rate | Country | 2025 ad block rate |
|---|---|---|---|
| Indonesia | 41% | France | 29% |
| Vietnam | 39% | Australia | 29% |
| China | 35% | UK | 27% |
| Poland | 34% | India | 25% |
| USA | 33% | Italy | 24% |
| Canada | 33% | Mexico | 22% |
| Austria | 33% | South Korea | 17% |
| Germany | 31% | Japan | 15% |
Ghana is the lowest in the table at 9%. Use these as a sanity check for your own measured rate by country, not as a substitute for it: they are survey shares of people, while your loss formula needs a share of pageviews.
Ad blocker use by age and gender
GWI data published by DataReportal and compiled by Backlinko (page updated March 19, 2026) shows men block more than women in every age band, and use falls after 55:
| Age | Women | Men |
|---|---|---|
| 16 to 24 | 24.7% | 34.1% |
| 25 to 34 | 28.3% | 34.5% |
| 35 to 44 | 27.5% | 34.5% |
| 45 to 54 | 24.2% | 32.0% |
| 55 to 64 | 21.4% | 28.0% |
| 65+ | 22.9% | 31.7% |
eyeo’s 2026 report adds that ad-block users skew toward Gen Z, higher education and higher income, and that 73% of them say they would be at least somewhat likely to create an account or log in for editorial content, against 62% of non-users. That second number matters for recovery: a login wall may convert this audience better than an ad wall.
Why people block ads
In the same GWI data, the top reasons are “there are too many ads” (63.5%), “ads get in the way” (53.5%) and “to protect my privacy” (42.4%), followed by irrelevant ads (39.8%), inappropriate content (37.2%), device performance (31.7%) and data collection (26.6%). Respondents could pick several reasons. The performance motive lines up with what slow, ad-heavy pages cost you elsewhere, covered in these page speed statistics; the privacy motive matches the broader trends in data privacy marketing statistics.

Adblock revenue losses at industry level: what the big numbers mean
The most quoted figure is eyeo’s projection of $54 billion in lost ad revenue for 2024, about 8% of projected global digital ad spend of $695 billion (an eMarketer figure), from the 2023 eyeo Ad-Filtering Report. eyeo’s July 2026 Guide to Ad Filtering repeats the $54 billion figure and says losses would be about $116 billion a year without ad filtering and other mitigation. Three cautions before you cite either:
- Both are projections from a company that sells ad recovery through Acceptable Ads and Blockthrough, not audited losses. eyeo’s 2026 report did not publish an updated dollar figure.
- Publishers themselves cannot pin it down: 94% of publishers surveyed by Blockthrough said they “cannot precisely quantify the revenue loss incurred due to adblocking” (2022 report).
- An industry percentage tells you nothing about your site. A news site and a gaming site with the same traffic can have very different block rates and RPMs, which is why the worksheet above uses your own inputs. For how ad spend splits across channels, see the US digital ad spend statistics; for how open-market CPMs are trending, the programmatic advertising statistics.
“Adblock revenue leakage” is the same loss described as a rate: the share of potential ad revenue that never reaches you because ads did not render. In the worked example, $1,880 lost out of roughly $10,400 in potential monthly revenue (400,000 × $14 ÷ 1,000 plus 600,000 × $8 ÷ 1,000) is 18% leakage.
Chrome Manifest V3, uBlock Origin and Safari: what changed for your block rate
Chrome’s move to Manifest V3 changed how the most capable blockers run, which can shift your measured rate even if nobody uninstalls anything. The dates below are from Google’s Manifest V2 support timeline (last updated September 9, 2026):
| Date | What happened in Chrome |
|---|---|
| June 3, 2024 | Phase-out begins on Beta, Dev and Canary with warning banners |
| October 9, 2024 | Installed Manifest V2 extensions start being disabled on Stable |
| March 31, 2025 | MV2 extensions disabled by default on all channels; users can still re-enable |
| July 24, 2025 (Chrome 138) | MV2 disabled everywhere; users can no longer turn them back on. Chrome 138 is the last version that runs MV2 with the enterprise policy |
| Chrome 139 | ExtensionManifestV2Availability policy removed; MV2 extensions stop working |
| August 31, 2026 | All remaining MV2 extensions removed from the Chrome Web Store |
The full uBlock Origin is no longer in the Chrome Web Store: its GitHub README notes the listing was removed on August 31, 2026, says it “works best” on Firefox, and quotes Microsoft’s plan to move Edge consumers off Manifest V2 by the end of 2026. Chrome users now get uBlock Origin Lite, built on the MV3 declarativeNetRequest API and available for Chrome, Edge, Firefox and Safari. Its FAQ says filter lists update only when the extension updates, dynamic filtering is only partly possible, generic cosmetic filtering is off by default, and it is “less effective at dealing with websites using anti-content blocker” because many filters cannot be converted. The MV3 API also caps rules: 30,000 guaranteed static rules per extension, 30,000 dynamic rules and 1,000 regex rules (Chrome declarativeNetRequest reference). Firefox is keeping Manifest V2 alongside V3, so full uBlock Origin still runs there.
What it means for you: measure before and after rather than assume. eyeo counts desktop ad-blocking users down 4% since 2023, but a Chrome user who switched to a lighter blocker can still block your ads, and your bait test will tell you which way your audience moved.
Safari and iOS work differently. Since 2015, Safari content blockers have been JSON rule lists (a trigger plus an action such as block or css-display-none) that WebKit compiles ahead of time, and the extension never sees which pages the user visits (WebKit blog, June 2015). AdGuard documents a cap of 150,000 rules per content blocker and splits its filters across six blockers to work around it. Because Google’s extension rate excludes mobile, iPhone blocking only shows up in a client-side test like Option 2.
Recovering adblock revenue: options and honest tradeoffs
| Option | How it works | Upside | Tradeoff |
|---|---|---|---|
| Acceptable Ads | Ad filtering users of AdBlock, Adblock Plus and partner tools see ads that meet the Acceptable Ads Standard | eyeo reports 400M+ users and 96% with Acceptable Ads enabled (2026 report); its guide says about 90% of publishers it works with allowlist without cost | Format limits: above-content ads max 200px high, above-the-fold ads max 15% of the visible page, no animated, overlay, pre-roll or rich media. eyeo charges a licensing fee to large platforms. Does not reach users of blockers outside the program |
| Ad blocking recovery message (Ad Manager or AdSense) | A message asks desktop users with blockers to allow ads, with an optional custom choice button | Free, measurable through recovery message conversions | Desktop browsers only. Google ended one-click allowlisting, so users must change blocker settings themselves |
| Server-side ad insertion (video) | Ads are stitched into the same stream as the content on the server, as with Ad Manager Dynamic Ad Insertion for live and on-demand video | No separate ad request in the player for a blocker to drop | Video only, needs streaming infrastructure; it does nothing for display inventory |
| Login or subscription ask | Offer free registration or a paid tier instead of ads | eyeo found 73% of ad-block users likely to log in or create an account, versus 62% of non-users | Builds a first-party relationship but replaces ad revenue only if conversion and pricing work |
| Forcing ads past the blocker | Circumvention scripts | More impressions in the short term | eyeo reports forced banner ads cut time on page by 10% to 20% and lower how users rate the site |
Two vendor claims you will meet, both unaudited: eyeo’s guide says monetizing ad filtering users can add 15% to 20% more page views, and Admiral says its publishers commonly recover 30% or more of lost adblock revenue. Test against your own conversions metric before you budget on either.
My view: for most sites the right order is measure for 30 days, turn on Acceptable Ads if your formats already comply, then test a recovery message on desktop and a login offer on mobile. Privacy-safe formats help too, since blockers’ users are the most tracking-averse readers you have; the contextual advertising statistics and native advertising statistics show where that inventory is heading. If ad revenue is a material line for your business and you want a second pair of eyes on the numbers, you can book a consultation.
Frequently asked questions
How do you measure adblock revenue loss?
Multiply monetizable pageviews by your measured block rate and your page RPM, then divide by 1,000, separately for desktop and mobile. Take pageviews from server logs, the desktop block rate from Google Ad Manager or AdSense's Ad blocking extension rate, and the mobile rate from a bait test logged to GA4. Example: 400,000 desktop views x 25% x $14 RPM / 1,000 = $1,400 a month.
How many people use ad blockers?
eyeo's Ad-blocking report 2026 estimates 1.1 billion ad-blocking users across desktop and mobile in Q4 2025, about 30% of the internet population: 448 million on desktop and 629 million on mobile. GWI survey data for Q2 2025 puts the share of internet users aged 16 to 64 who block ads at least sometimes at 29.5%.
How many people use ad blockers in the USA?
GWI survey data compiled by Backlinko puts US ad blocker use at 32.5% of internet users in Q2 2025, and eyeo's 2026 country table lists the USA at 33% for 2025. These are shares of people. Your own measured share of pageviews is usually lower, because many users do not block on every device or site.
Is there an adblock loss calculator?
AdPushup and Admiral offer adblock recovery calculators, but neither publishes its formula. You can build your own in a spreadsheet: pageviews by device, block rate by device, page RPM by device, then pageviews x block rate x RPM / 1,000. Treat the result as a ceiling and apply your own recovery share and recovered RPM to estimate what you can win back.
Does Google Ad Manager show my adblock rate?
Yes. The Privacy and messaging report includes Ad blocking extension rate, the percentage of page views where users had an ad blocker extension installed. It covers desktop page views only, since mid-February 2024, and has no data before you enabled it. AdSense shows the same rate on the ad blocking recovery message card under Privacy and messaging.
Does uBlock Origin still work on Chrome?
Not the full version. Chrome 138 disabled Manifest V2 extensions for all users in July 2025, Chrome 139 removed the enterprise exception, and remaining MV2 extensions left the Chrome Web Store on August 31, 2026. Chrome users can install uBlock Origin Lite, an MV3 version that its own FAQ says is less effective against anti-adblock sites. Firefox still supports the full extension.
What is adblock revenue leakage?
It is adblock loss expressed as a share of potential ad revenue: the revenue you would have earned if every pageview rendered ads, minus what you actually earned because blockers stopped them. In a worked example with $10,400 of potential monthly revenue and $1,880 lost to blocking, leakage is about 18%. Measure it per device, since block rates and RPMs differ.
Advertising & ad-tech research
About the author
Christoph Olivier Christoph Olivier is the founder of CO Consulting and a fractional CMO who has managed millions of dollars in ad spend and built a combined audience of over a million followers across social platforms. He works with 7- and 8-figure businesses, primarily in tax, M&A, consulting, real estate investing, capital raising, and financial services. His edge is a practitioner’s command of every major marketing channel, theory and execution, backed by the original marketing data reports he publishes here on CO Consulting.