Ad blockers hide visitors: how to get a more complete traffic count
Short answer: Yes, ad blockers, privacy browsers and cookie refusals can stop your analytics from counting some visitors, and no one can give you a single percentage that fits your site. The gap depends on your audience: a tech-heavy audience hides far more than a plumber's customers. Measure your own gap by comparing real enquiries with the actions Google Analytics 4 (GA4, Google's free visitor-counting tool) recorded, then decide whether a fix is worth paying for. Fixes run from doing nothing to switching to a first-party analytics tool, and small sites rarely need the most expensive one.
Your analytics says 400 visitors and your inbox says more people got in touch than that suggests, so you suspect ad blockers are hiding part of your traffic.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
You are probably right that some visitors are missing. What matters is how many, whether it changes any decision you make, and what a fuller count costs. This guide explains what blocks counting, how to measure your own gap in 20 minutes, the fixes in order from free to costly, and who should simply ignore the problem.
It is written for a business owner or agency owner, not a developer. Where a term is technical, I explain it once. For the related questions of which pages bring enquiries and whether you can see who visited, see which pages bring enquiries and who is visiting my website. One option below is Ploy, an AI website builder that serves its own analytics from your site's domain.
This page may contain affiliate links from which Blur Studio earns commissions.
What actually hides visitors from analytics
"Ad blocker" is shorthand for several different things. Ad blocking is about ads. Analytics blocking comes from filter lists in blockers and from browser privacy features. In practice, these reduce your count:
- Blocker extensions and privacy browsers. They stop known analytics scripts from loading, so the visit never reaches your report.
- Safari's tracking limits. WebKit, the engine behind Safari, documents these. A cookie created in JavaScript on a landing page reached through a tracking link has its life capped at 24 hours. Script-written storage is deleted after 7 days without the person interacting with the site. A returning visitor after a week can therefore look new.
- Cookie refusal. If your banner holds back analytics until people accept, refusers are not fully counted. Google's consent mode can model some of the missing behaviour, but only above minimums (at least 1,000 events a day with analytics storage denied for 7 days, and 1,000 daily users with it granted over 7 of the previous 28 days), and meeting them does not guarantee eligibility. See cookie banners and consent.
- People who leave before the page loads, and visitors who turn off JavaScript. These are small but real.
Direction matters too. GA4 excludes known bots automatically, using Google research and the International Spiders and Bots List kept by the advertising industry body IAB, and you cannot switch that off or see how many were removed. So bots you do not know about may inflate your count while blockers deflate it. Your number is wrong in both directions.
How big is the gap?
Not one number fits everyone. The best known figure comes from Plausible, a company that sells privacy-friendly analytics. In a three-day test in August 2021, on a site with a post trending on Hacker News and Reddit (two sites where tech-minded readers share links), Plausible counted 50,947 visitors while Google Analytics (the older version, Universal Analytics) counted 21,054. Plausible said that meant Google Analytics was missing 58.67 percent of visitors. That was a vendor test on a technical audience, in 2021, over three days. It is an upper-end example, not a typical rate for a local business. Plausible's own article also says the two tools measure differently, which adds to the gap.
Treat other percentages you read, from vendors including Ploy's own feature page, as claims unless the source gives a sample and a date. The right question is not "what does the internet say" but "what is my gap".
Step 1: measure your own gap in 20 minutes
- Pick a period of 28 to 30 days.
- Count real enquiries from your inbox, form tool and phone log. Exclude spam and calls that did not come from the website.
- Count GA4 key events for the same period. A key event is an action you flagged as important, such as a form sent.
- Divide. GA4 events divided by real enquiries is your capture rate.
Interpret it like this (my rule of thumb, not an industry standard):
| Capture rate | What it suggests | What to do |
|---|---|---|
| 85 to 100% | Tracking is fine | Nothing |
| 60 to 85% | A normal gap | Use GA4 as a ranking of pages, not an exact count |
| Under 60% | Blockers, consent settings or a broken goal | Test the goal first, then consider a fix below |
Test the goal before you blame blockers. Submit a test form from your phone on mobile data and check that the event shows in GA4's real-time report. A wrongly set goal looks exactly like blocked traffic. If forms are not arriving at all, use the forms not sending checklist.
Worked example (made-up numbers)
A dental clinic's site shows 1,200 visits and 18 form key events in March. The clinic's receptionist counted 25 online enquiries. Capture rate: 18 divided by 25 is 72 percent. The clinic's audience is local and mixed in age, so a normal gap is plausible.
The decision: does a 28 percent undercount change anything? The clinic uses the report to choose which two pages to improve. The ranking of pages is the same whether it counts 18 or 25 events, so the answer is no. They keep GA4 and use the receptionist's count as the headline. Spending on a fix would not change a decision.
Now change the story. An online software seller shows 3,000 visits and 40 trial sign-ups in GA4, but the sign-up database shows 90. Capture is 44 percent, and the audience is technical. Here the gap changes decisions, such as which campaign to pay for, so a fix is worth a look.
Step 2: the fixes, from free to costly
Fix 0: accept the gap and cross-check
Free. Report the real enquiry count as your headline and GA4 as a ranking. For most small business sites this is the right answer.
Fix 1: count from the source of truth
Free. Your form tool, booking system or customer database counts every submission, because it records on the server, not in the visitor's browser. Add a hidden field for the page and a "how did you hear about us" question. This does not count visitors who never enquired, but it makes enquiry numbers exact.
Fix 2: a privacy-friendly analytics tool served from your own domain
Several tools are built to be lighter than GA4 and can be set up to load from your own domain, which blockers are less likely to match. Prices below come from each vendor's own page as of November 2026, so check the pages for current terms.
| Tool | What it is | Entry price shown |
|---|---|---|
| Plausible | Simple, open source, cookie-free analytics | Starter $9 a month (one site), Growth $14, Business $19, each priced for up to 10,000 monthly pageviews; currency not named on the page; 30-day free trial, no card |
| Fathom | Simple privacy-focused analytics | $15 a month for up to 100,000 pageviews across 50 sites, in USD; 7-day trial, card required |
| Simple Analytics | Simple privacy-focused analytics | Self-serve $20 a month for one user; a free plan allows 5 websites with 1 month of history and a badge; 14-day trial, no card |
| PostHog | Product analytics with session recordings | Free monthly allowance of 1 million events and 5,000 recordings; events kept 1 year on free |
Caveat: none of these vendors' pricing pages promise a tool that no blocker can touch. A first-party setup may reduce the loss. Do not expect it to remove it, and test it against your own enquiry count.
Fix 3: server-side tagging
Server-side tagging means your analytics events pass through a server you control before going to Google. Google lists its benefits as better page performance, more detailed privacy controls and better data quality. It is not free. Google's overview page gives $30 to $50 per server per month and recommends at least 3 servers, which is about $90 to $150 a month. Google's planning page says approximately USD 50 per instance per month, so the same 3 servers would be about $150. Google's pages differ on the starting minimum (2 or 3 servers), so the monthly figure runs from roughly $60 to $150. Logging and traffic costs come on top. It also needs a developer to set up. For a small site this is rarely worth it. Check the current Google pages before you budget.
Fix 4: server or CDN logs
Your host or content delivery network counts every request, including from blocked visitors. But logs count requests, not people, and they include bots, so they will run higher than reality. Use them as an upper bound, not a conversion count.
Where Ploy fits
Ploy is an AI website builder and host, and its built-in analytics records page views, clicks, form sends, scroll depth and traffic sources, and Ploy's docs state that events are sent to your site's own domain. Its feature page also says GA4 and PostHog scripts are served first-party and that analytics is included on every plan with no traffic cap. Ploy also logs visits from AI crawlers (programs from AI companies that read web pages, such as OpenAI's GPTBot, Perplexity's PerplexityBot and Anthropic's ClaudeBot) separately from people.
Do not assume this makes your count blocker-proof. Ploy's docs state no recovery rate for blocked visitors and no rules for filtering bots out of human totals. Ploy's feature page cites a range of visitors using ad blockers without naming a source, so I do not repeat it. And Ploy follows each visitor's cookie choice: on refusal, the anonymous ID resets daily, the IP address is not stored and a returning visitor on a later day counts as new.
Plans as of November 2026: Free $0, Starter $50 a month, Pro $300 a month, Enterprise by quote. Analytics only helps if your site is on Ploy, so I would never move a site only to fix a count. If you are choosing a platform anyway, see the Ploy review. The test in Step 1 works on any platform, so run it before and after any change.
Consent still applies
A fuller count does not remove your duties. Counting people who tried to opt out can break privacy rules in some places. Cookie-free does not always mean consent-free. Some regulators, such as France's CNIL, allow narrow exemptions for simple audience measurement, with conditions. Check your local rules and the regulator's current page, and ask a privacy lawyer if you are unsure. This is information, not legal advice. See whether visitor tracking is allowed.
Copy-ready checklist
- Count real enquiries for 30 days.
- Count GA4 key events for the same 30 days.
- Test the goal with a form sent from your phone.
- Work out your capture rate.
- Decide whether any decision you make would change at a 70 percent versus a 100 percent count.
- If not, stop and keep the cross-check.
- If yes, try a first-party analytics tool for one month in parallel with GA4.
- Compare the three counts: real enquiries, GA4, the new tool.
Test plan with pass and fail
- Pass: the new tool's count sits within 10 percent of your real enquiry count over a month, while GA4 sits further away.
- Fail: both tools are within 10 percent of each other. The fix added cost and no information.
- Fail: the new tool counts more than your real enquiries. Look for test submissions, spam or bots.
The thresholds are my rule of thumb.
Who should skip all of this
- Local service businesses whose real decisions come from the phone log and the inbox.
- Sites with fewer than about 30 enquiries a month, where the noise is larger than the gap.
- Anyone who would not act differently at a 100 percent count.
Who should look closer: sites with a technical audience, sites that spend on ads and judge campaigns by tracked sign-ups, and agencies whose clients question the numbers.
How I'd approach this
I would measure first and spend second. Run the 20-minute gap test, fix any broken goal, and make the form tool or customer database the source of truth for enquiry counts. Only if the gap changes a decision, run a lightweight first-party analytics tool alongside GA4 for one month and compare the three numbers. I would leave server-side tagging for sites where tracked sign-ups drive real ad spend.
If your tracking was set up wrongly, or you want a custom dashboard that reads from your forms or database directly, Blur Studio builds that and fixes broken tracking: see what that includes.
First week plan: Day 1, count last month's real enquiries. Day 2, count GA4 key events and work out the capture rate. Day 3, send a test form and confirm the goal fires. Day 5, add the page and source fields to your form. Day 7, decide: stop, or start a one-month trial of a first-party tool.
A closely related page covers the same ground from another angle: A Simple Monthly Website Report for Clients, Without Analytics Screens.
Related guide: A Weekly Website Report That Writes Itself: Options.
Related guide: Ad Ideas for a New Client in an Unfamiliar Niche.
I'm not a lawyer, accountant or other licensed adviser, and this page is general information, not advice. Rules and prices differ by country and change often, so treat it as a direction to think along, and please check with a lawyer or the relevant regulator before you act on it.
Questions people ask
How many visitors do ad blockers hide?
It depends heavily on your audience, so there is no honest single figure. A vendor test by Plausible in August 2021, on a technical audience over three days, found Google Analytics missing 58.67 percent of visitors, which is an upper-end example. Measure your own gap by comparing real enquiries with GA4 key events.
Does Google Analytics 4 count bots?
GA4 automatically excludes known bots and spiders, using Google research and the IAB International Spiders and Bots List. You cannot turn that off or see how many were excluded, so unknown bots can still appear in your counts.
Does server-side tracking bypass ad blockers?
It can reduce losses, but none of Google's pages promise it bypasses all blockers, and visitors who disable JavaScript or block your own domain may still be missed. Google's planning page puts server cost at roughly USD 50 per instance per month, so check the current pages before budgeting.
What is the cheapest way to get a more complete count?
Count from your form tool or customer database, which records every submission on the server. Then, if needed, try a low-cost first-party analytics tool such as one of the plans shown in the table above, in parallel with GA4 for one month.
Does Safari affect my analytics?
Yes. WebKit's documentation says cookies created in JavaScript after a tracking-link landing are capped at 24 hours, and script-written storage is deleted after 7 days without interaction. Returning visitors can therefore look like new visitors.
Is cookie-free analytics legal without a cookie banner?
Not automatically. Some regulators, such as France's CNIL, allow narrow exemptions for limited audience measurement, but conditions apply and rules differ by country. Check your local law and the regulator's current page. See cookie banners and consent.
Does Ploy's analytics get around ad blockers?
Ploy serves its tracking from your site's own domain and follows each visitor's cookie choice, but its docs do not state how many blocked visitors it recovers, so I would not call it blocker-proof. Run the capture-rate test before and after.
Should I worry about this for a small local business?
Usually not. If your decisions come from the inbox and phone log, a 70 percent capture rate in GA4 still ranks your pages correctly. Worry when tracked sign-ups drive ad spend or when clients dispute the numbers.
More in this topic: Websites: simple stats and reports for owners and clients (9 guides) →
Sources
- Plausible: Google Analytics and ad blockers study
- WebKit: tracking prevention
- Google Analytics Help: known bot exclusion
- Google Analytics Help: consent mode modelling
- Google: server-side tagging
- Google: server-side tagging overview
- Google: planning server-side infrastructure
- Plausible pricing
- Fathom pricing
- Simple Analytics pricing
- PostHog pricing
- Ploy docs: analytics