Blocking rates differ sharply by audience and topic, and technical audiences block most. Measuring your own rate matters more than any benchmark, and aggressive recovery frequently costs more in lost visitors than it recovers.

The share is not uniform

Published averages are close to meaningless for an individual site, because the variation by audience is enormous.

Technical, gaming and privacy-adjacent audiences block heavily. General consumer, local, and older audiences block far less. Mobile blocking is generally lower than desktop, though it varies by platform and region.

Which means a publisher comparing themselves to a headline figure is comparing against a number that describes nobody.

Your own rate is measurable and worth knowing before deciding anything.

Measuring it

The straightforward approach is comparing a count that a blocker will suppress against one it generally will not.

Your analytics, if it is not itself blocked, records sessions. Your ad server records requests. The gap between them, adjusted for pages without ad slots, approximates the blocked share.

That is rough, since some blockers also suppress analytics, which understates the gap. It is enough to distinguish a small problem from a large one, which is the decision it informs.

Segment it. Blocking differs by device, by traffic source, and by section of the site, and a single figure hides where the problem actually is.

Why people block

Worth understanding before responding, because the reason determines what works.

Research and stated reasons consistently centre on interruption, page weight, tracking, and the sheer volume of advertising rather than advertising as such.

Which is uncomfortable and useful. A meaningful share of blocking is a response to how advertising was implemented rather than a rejection of the model.

A site with a heavy ad load, intrusive formats, and slow pages produces blockers. A site with a restrained load produces fewer.

The responses, from best to worst

Reduce what caused it

Fewer slots, no formats that cover content, no automatic sound, and a page that loads quickly. This addresses the cause and improves the site for everybody who did not block.

It is slow, unglamorous, and the only response that reduces the rate over time.

Ask, politely, once

A dismissible message explaining that advertising funds the site and inviting an exception. A modest share comply, particularly on sites people value.

It works when it is honest, brief, and does not block anything.

Offer an alternative

A paid option, a membership, or a supporter arrangement. Serves the readers who genuinely do not want advertising and is worth something at any scale.

Block the blockers

Withholding content until the blocker is disabled. Recovers some revenue and loses visitors, and the ones lost are frequently the engaged readers who return most.

It also produces an arms race you do not win, since detection and counter-detection escalate continuously.

Circumvent silently

Technical measures to serve advertising despite the blocker without the visitor knowing. Carries consent and transparency questions, and it is a poor position to be in if described publicly.

The arithmetic before recovery

Rarely run and it usually settles the question.

The revenue recovered from blocked visitors who comply, against the visitors lost who leave rather than comply, valued over their lifetime rather than that session.

A returning reader who leaves permanently is worth many single sessions, and blocking-wall approaches lose disproportionately from that group.

For most small publishers the arithmetic favours reducing the cause and asking politely, and does not favour a wall.

What this means for planning

Treat the blocked share as a permanent reduction in addressable inventory rather than a problem to solve.

Plan revenue on the servable share. A publisher forecasting on total traffic is forecasting on inventory that does not exist.

And accept that the audience most valuable in other respects, meaning engaged, technical and returning, is the audience most likely to block. Which is an argument for having something to sell them other than advertising.

The load question underneath all of this is set out in ad density and page views: the tradeoff nobody measures properly.

Frequently asked questions

Are published blocking rates useful?

Barely. Variation by audience is enormous, with technical and gaming audiences blocking heavily and general consumer audiences far less. Measure your own.

How do I measure my own rate?

Compare analytics sessions against ad server requests, adjusted for pages without slots. It is rough, since some blockers suppress analytics too, but enough to size the problem.

Why do people block?

Stated reasons centre on interruption, page weight, tracking and volume rather than advertising as such, which means implementation is part of the cause.

What response actually reduces the rate?

Reducing what caused it: fewer slots, no formats covering content, no automatic sound, faster pages. Slow, unglamorous, and the only durable answer.

Do blocking walls work?

They recover some revenue and lose visitors, disproportionately the engaged readers who return most, and they start an escalation you do not win.

How should I plan around it?

Treat the blocked share as a permanent reduction in addressable inventory and forecast on the servable share rather than total traffic.

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.

Never measured what share of your audience blocks?

We work it out by section and device, which usually shows the problem is narrower than it feels.

Start a Conversation