Quick answer
An ad blocker is software, usually a browser extension, that cancels requests matching filter-list rules for ads and often trackers. A blocked analytics script never records the visit. The useful question is how large your own gap is and whether it differs between audience groups.
Formula: Gap = (server count − analytics count) ÷ server count
What an ad blocker does
An ad blocker is software, most often a browser extension, that stops a page from loading or showing things its rules classify as advertising. Many also block trackers, which is why they matter to analytics: a blocker does not know the difference between an ad network's script and a measurement script; it only checks each request against its rules, and cancels the ones that match. A blocked analytics script never runs, so the visit is never recorded.
That makes the useful question for an analyst not "how many people use ad blockers" (a global figure is not your audience) but how big the gap in your own data is, and whether it is random. A 5% gap spread evenly changes nothing about your conclusions. A 20% gap concentrated in one browser or audience can change them.
How blockers decide what to block
Blockers work from filter lists, which are sets of rules maintained by communities. EasyList is the main list aimed at advertising; EasyPrivacy is a supplementary list aimed at tracking, including tracking scripts and information collectors. Extensions such as uBlock Origin read rules of two kinds:
| Rule type | What it does | Effect on analytics |
|---|---|---|
| Network filter | Cancels a request that matches a hostname, URL pattern or resource type, for example a script from a given domain | The analytics script, or the request that sends the visit, is blocked, so there is no data |
| Cosmetic filter | Hides an element on the page, for example an ad slot or a banner | No effect on measurement; only what the visitor sees changes |
Rules can be written against a hostname (a bare hostname blocks requests to that site and its subdomains) and can be limited to third-party requests or to scripts. Two consequences follow. First, blocking happens at the request, not at the cookie, so an analytics tool that writes no cookie is still blocked if its script or its collect endpoint matches a rule. Second, the lists change all the time, so the gap you measured last quarter is not guaranteed this quarter.
Browser privacy signals are a related but separate cause of missing data. Do Not Track and Global Privacy Control are signals the browser sends; they do not block anything themselves, but a tool can choose to stop when it sees one. Global Privacy Control is sent as the Sec-GPC: 1 header.
What a blocked visit looks like
You cannot see a visit that was blocked, only the traces around it. Check these before concluding that a blocker is the cause:
| Symptom | Likely cause | How to check |
|---|---|---|
| Your own visit never shows in real-time, but works in a private window with no extensions | A blocker or privacy extension | Switch extensions off, reload, and compare |
| No request to the analytics host in the browser network panel | The browser or an extension cancelled it | Open the network panel and look for the script and collect requests |
| The script loads but no data arrives | A content security policy blocks the collect host | Compare the policy's script and connect rules with the analytics hosts |
| Counts differ from a server-side number by a stable percentage | A mix of blockers, closed tabs and declined consent | Measure the gap, as in the example below |
A content security policy that blocks the collect host looks almost the same as a blocker, so rule it out first: the site's own policy is fixable, a visitor's extension is not.
Worked example: sizing the gap from server numbers
Sample data: over four weeks, the server recorded 1,000 sign-ups (each one is written to the database when the account is created). The analytics goal for sign-ups shows 872.
| Device | Server sign-ups | Analytics sign-ups | Missing | Gap |
|---|---|---|---|---|
| Desktop | 600 | 498 | 102 | 17.0% |
| Mobile | 400 | 374 | 26 | 6.5% |
| Total | 1,000 | 872 | 128 | 12.8% |
How to recompute: gap = (server − analytics) ÷ server. Total: (1,000 − 872) ÷ 1,000 = 12.8%. Coverage = analytics ÷ server = 872 ÷ 1,000 = 87.2%, so scaling the analytics count up by 1 ÷ 0.872 = 1.147 reproduces the server figure.
Two things the table says. First, the 12.8% is an upper bound for blockers, because the missing sign-ups also include visitors who closed the tab before the event fired, who declined analytics consent, or who completed the action in a way that was not tracked. Second, the gap is not random: desktop loses 17.0% and mobile 6.5%. Desktop is 60.0% of real sign-ups but 498 ÷ 872 = 57.1% of measured ones, so the measured device mix understates desktop by 2.9 points. Any comparison of desktop and mobile conversion rates built from the analytics data alone is biased by that difference.
Is the gap random?
Judge it with a rule: the gap matters when it differs between the groups you compare.
- If every segment has about the same gap, rates and trends stay reliable. The absolute count is low, but the ratio between groups holds.
- If gaps differ (by browser, device, country or audience), compare groups only within the same segment, or scale each segment with its own coverage.
- Do not apply a single scaling factor to pageviews. The 1.147 factor was measured on sign-ups, which are completed by people who are logged in and follow a particular path; blockers affect visitors who never sign up differently.
- Keep the check running. If coverage falls from 87.2% to 80% after a script change, a list or a policy has changed.
Audiences differ in how many of them use blockers, so the size of the gap varies from one product to another. Treat any expectation about your audience as a hypothesis and test it with your server numbers.
Measuring around blockers without evading them
A visitor who installs a blocker has made a choice, and a measurement tool should respect it. What you can do legitimately is make the key numbers independent of the browser and measure the gap:
- Record key conversions on the server. Send orders and sign-ups as server-side events at the moment they are written to your database; see server-side tracking. A server event is not affected by a visitor's extension.
- Reconcile against your own systems. Compare analytics counts with the orders table, the account table or the payment processor over several weeks, as in the example above.
- Know what the script cannot do. Pageviews and browsing behaviour still depend on the script running. Treat them as a large sample, not a complete count.
- Use the right pixel or script for the right job. A tracking pixel is blocked by the same request rules as any other script.
Cookie type does not matter here: a first-party cookie is a storage question, and cookieless analytics does not turn a request into one a blocker will not cancel.
Common mistakes
- Using a global blocker share as your gap. Your gap is a property of your audience, so measure it.
- Assuming cookieless means unblockable. Blockers act on requests, not on cookies.
- Testing your install with your own blocker on. You will conclude that the install is broken when it is the extension.
- Blaming the blocker for a policy problem. A content security policy that omits the collect host drops data in the same way.
- Scaling every number by one factor. The factor depends on the metric and the segment.
- Reading a flat number as proof there is no gap. If the analytics number matches the server number exactly, check that both are counting the same thing.
Ad blockers in TapCub
Take the 12.8% gap in the example and use it for a decision. The background is in do ad blockers block TapCub.
- Rule out your own browser. Open Web analytics › Realtime and visit your site in a window with no extensions; if the visit appears there but not in your normal browser, an extension is the cause. In the network panel, a blocked visit shows no request to the TapCub hosts.
- Rule out your policy. If your site sets a content security policy, it has to allow the hosts of the TapCub script, the collect endpoint and (if you use it) chat, because each has its own host. A policy that blocks them drops the data without an error on the page.
- Measure the gap. Take a number you also record on your server, such as sign-ups or orders, and compare it with the same goal in Web analytics › Goals over a few weeks. The difference is a rough upper bound on what blockers, closed tabs and declined consent hide.
- Send the numbers that matter from the server. Send orders and sign-ups as server-side events so those totals do not depend on the script. Pageviews and browsing behaviour still do.
- Know the defaults. TapCub does not try to bypass a browser blocker. Do Not Track and Global Privacy Control also stop the script by default; the script tag can be set to ignore them, but that choice is yours and needs legal advice.
TapCub counts what its script and server events send. It does not recover visits that were blocked, and it does not estimate them for you.
Sources
- EasyList, easylist.to: EasyList for advertising, EasyPrivacy for tracking.
- uBlock Origin wiki, Static filter syntax: network and cosmetic filters, hostname rules and the
third-partyandscriptoptions. - W3C, Global Privacy Control: the
Sec-GPC: 1header andnavigator.globalPrivacyControl.
Was this explanation clear?
We use your answers to fix and expand this page.
Couldn’t send. Please try again in a minute.
Thanks for the feedback. We’ll use it to improve this page.You’ve already sent feedback on this page. Thanks.

Technical Engineer
Focuses on tracking code, SDKs, and API integrations, with practical guidance on implementation checks and troubleshooting.