Analytics and Tracking

Ad Blocker

Also called Content blocker, adblock

Extension, browser or network filter that stops ads and tracking scripts loading, and a common cause of undercounted traffic.

Quick facts: Ad Blocker

Category
Analytics and Tracking
Also called
Content blocker, adblock
Level
Beginner
Affects
Analytics accuracy, ad reach, conversion counts
Where to see it
uBlock Origin, AdGuard, Brave, browser DevTools network tab
In this article4
  1. How ad blockers work
  2. Why ad blockers matter
  3. Common mistakes with ad blockers
  4. How to act on it

How ad blockers work

An ad blocker is a filter sitting between the browser and the internet. It carries community-maintained lists of URL patterns known to serve advertising or tracking, and when a page tries to fetch something matching a pattern, the request is cancelled. A second set of rules hides the leftover empty space so the page still looks tidy.

They arrive in several forms. Browser extensions such as uBlock Origin and AdGuard are the familiar ones. Some browsers, Brave among them, block by default with nothing to install. Network-level blockers run on a router or a small home server and cover every device in the house, including phones and smart televisions, which is why blocking is not only a desktop problem.

The important detail for marketers is that the same lists catch measurement, not just advertising. Tag managers, analytics libraries and ad-platform pixels sit on the tracking lists, so a blocked visitor is invisible in reporting even though they saw the whole page.

Why ad blockers matter

Blocked visitors do not stop being customers. They browse, they read, they buy and they fill in forms — the transaction lands in your system while the visit and the conversion never reach your analytics. So the numbers you plan with are lower than reality, and the discrepancy is largest for audiences who are comfortable installing browser extensions.

Blocking is also uneven across placements. A banner pulled in from an ad network’s own domain is easy to filter. An ad shown inside an app’s own feed, where it is served from the same place as the content around it, is much harder — which is one reason in-feed social advertising holds up better than open-web display. In Nepal, where a large share of traffic arrives through in-app browsers on Android, extension-based blocking is less common than on desktop, but it is still present and should not be assumed away.

Common mistakes with ad blockers

The most expensive mistake is treating the measured group as if it represented everybody. If you cut a campaign because analytics shows no conversions from it, check whether the platform, your CRM or your order records tell a different story first.

The second is a self-inflicted one. Filter lists match on words in a URL, so a folder called /ads/, a file named ads.js or a form container with a class of advert can be blocked on your own site — sometimes removing a working enquiry form. Name things after what they do, not after advertising.

The third is putting up a wall that detects blockers and demands they be switched off. It irritates people, invites a counter-filter within days, and rarely earns back the traffic it costs.

How to act on it

Accept the gap and measure around it. Anchor decisions on records the browser cannot influence — orders, enquiries, signed quotes, answered calls — and use browser-based tracking for shape and direction rather than for a final count. Watching the size of the gap over time tells you more than trying to estimate it once.

Where the measurement genuinely matters, move it off the page. Server-side collection from your own domain, with the events your business actually cares about, is more durable than another script in the browser. Getting that right is what an analytics and tracking setup is for, and it is worth doing before you next argue about which channel deserves the budget.

Do and do not

Do

  • Compare analytics against orders and enquiries you can count
  • Avoid the word ads in file and folder names
  • Collect key events from your server, not only the browser

Do not

  • Assume blocked visitors behave like measured ones
  • Block your content until someone disables their blocker
  • Kill a channel on browser data alone

Questions people ask about this

Do ad blockers stop Google Analytics from working?

For the people using them, usually yes. Common privacy filter lists include tag managers and analytics libraries, so the script never loads and the visit is never recorded. The page itself works normally, and the visitor may still buy or enquire. That is why your own order and enquiry records will often show activity your analytics missed.

Can I detect visitors who are blocking my tags?

Only partially, and it is rarely worth the effort. Detection scripts get added to filter lists quickly, and any figure you produce is an estimate of an invisible group. A steadier method is to compare a number the browser cannot affect, such as orders placed, with the same number in analytics, and track how far apart they sit.

Should I ask people to whitelist my site?

For a business site selling a service, no. Whitelist requests belong to publishers who lose revenue directly when ads are blocked. For everyone else the ask breaks the visit for no gain and reads as though you are hiding something. Spend the effort on server-side measurement and on records you own instead.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.