---
title: "Why GA4 Doesn't See Part of Your Traffic"
description: "Consent rejection, ad blockers and browser limits hide part of your traffic from GA4. How much depends on the store. At Incapto it was 29% of visits."
summary: "GA4 doesn't see part of your traffic: visitors who reject the consent banner, visitors whose ad blocker stops the tag, and visitors whose browser cuts the cookie short. How much depends on the store and the channel, so it has to be measured on each site. In our experience with clients, between 40% and 60% of traffic…"
canonical_url: "https://sealmetrics.com/blog/why-ga4-misses-traffic/"
lang: "en"
author: "Rafa Jiménez"
author_url: "https://sealmetrics.com/authors/rafa-jimenez/"
date_modified: 2026-09-21
content_type: "blog"
owner: "content"
llm_priority: "useful"
last_verified: "2026-09-21"
source: https://sealmetrics.com/blog/why-ga4-misses-traffic/
publisher: Sealmetrics
---

Data Quality

# Why GA4 Doesn't See Part of Your Traffic

Quick answer

GA4 doesn't see part of your traffic: visitors who reject the consent banner, visitors whose ad blocker stops the tag, and visitors whose browser cuts the cookie short. How much depends on the store and the channel, so it has to be measured on each site. In our experience with clients, between 40% and 60% of traffic doesn't accept cookies, and of those who do, 40% don't accept on the first pageview, which is the page that carries the traffic source. When Incapto ran GA4 and Sealmetrics side by side on its Shopify store for 48 days, GA4 missed 29% of visits and 45% of pageviews, and the gap was uneven by channel. Sealmetrics measures without cookies and without processing personal data, so it meets the CNIL and AEPD criteria for consent-exempt audience measurement (self-assessed) and does not lose visits to consent rejection. It attributes revenue on last click, back to the campaign and keyword that earned it.

March 6, 2026 7 min read By [Rafa Jiménez](https://sealmetrics.com/authors/rafa-jimenez.md) Updated September 21, 2026

## Key Takeaways

- GA4 doesn’t see part of your traffic: consent rejection, ad blockers and browser restrictions each remove a share, and sampling degrades what is left. How much depends on the store and the channel.
- In our experience with clients, between 40% and 60% of traffic doesn’t accept cookies, and of those who do, 40% don’t accept on the first pageview, the page where the traffic source is recorded.
- At Incapto (Shopify, Consent Mode, 48 days), GA4 missed 29% of visits and 45% of pageviews. The extra traffic Sealmetrics saw ran from +11% in direct to +133% in organic social.
- Google Consent Mode v2 models missing data but cannot recover what was never collected: it estimates, it does not measure.
- There is no universal percentage. The only number that matters is your own, measured side by side with GA4.

Open GA4 right now and look at yesterday’s sessions. The number on your screen is not wrong, exactly. It is real data from real visitors. The problem is what it leaves out, and that the report gives you no way to know how much.

This is not a bug. It is not a misconfiguration. It is the structural result of how cookie-based analytics works in the European Union in 2026. The wider argument — why incomplete data produces wrong decisions and what [complete data](https://sealmetrics.com/complete-data.md) changes — lives on the pillar; this post is the mechanism underneath it.

## Three ways GA4 loses sight of a visit

GA4 does not lose your data in one place. It loses it in three successive layers, each acting on what the previous one left. The term for this cumulative erosion is [data loss in analytics](https://sealmetrics.com/glossary/data-loss-in-analytics.md). What follows is how each layer works. How big each one is on your site is a separate question, and the honest answer is that it has to be measured, not looked up.

## Layer 1: the visitors who say no

Under [GDPR and the ePrivacy Directive](https://eur-lex.europa.eu/eli/reg/2016/679/oj), any website using cookies for analytics must obtain consent before firing tracking scripts. In our experience with clients, between 40% and 60% of traffic doesn’t accept cookies. Where a site lands in that range depends on the sector, the strength of the brand, the traffic mix and the design of the banner.

When a visitor clicks “Reject” on your cookie banner, GA4 never loads. That visitor does not exist in your analytics. No pageview, no session, no event. They are invisible.

The deeper problem is that [consent rejection is not random](https://sealmetrics.com/blog/consent-banner-impact-on-analytics.md). The people who reject are not a representative sample of the people who visit, so losing them does not just shrink your data. It bends it.

## The hidden layer: cookies that arrive too late

Acceptance is not the end of the problem. In our experience with clients, of those who do accept cookies, 40% don’t accept on the first pageview: they browse first and click the banner later.

Why does this matter? Because the landing page is where the traffic source is recorded. The referrer, the UTM parameters, the campaign data — all of it is captured on the first page view. If cookies are not active on that page, GA4 sees the rest of the visit but never learns where it came from. The session lands in direct, in unassigned, or nowhere useful.

So even the visitors GA4 does count are not all attributed. Part of what looks like measured traffic is traffic with no origin you can decide anything with.

## Layer 2: ad blockers stop the tag

Some of the visitors who accepted cookies run browser extensions that block analytics scripts. uBlock Origin, AdBlock Plus, Brave’s built-in shields and dozens of similar tools all target gtag.js and the Google Analytics collection endpoint.

Unlike consent rejection, ad blocking is silent. The visitor accepted your cookie banner, they are browsing your site, they may even be converting — but GA4 never fires because the script was blocked before it could load.

How many of your visitors block depends on who they are: the share is higher on desktop than on mobile, and higher in technical audiences — software, SaaS, developer tools — than among general shoppers.

## Layer 3: browser restrictions erode the rest

Safari’s [Intelligent Tracking Prevention](https://sealmetrics.com/glossary/intelligent-tracking-prevention.md) ([ITP](https://webkit.org/tracking-prevention/)) caps third-party cookies at 7 days and client-side first-party cookies at 24 hours in many scenarios. Firefox’s Enhanced Tracking Protection (ETP) applies similar restrictions.

The effect is subtle but significant: returning visitors appear as new visitors because their identifier expired. Sessions fragment. Attribution chains break. A customer who visited your site five times over two weeks looks like five different people in GA4.

This does not remove visitors from your count entirely, but it distorts session data, inflates new-user metrics and breaks multi-session attribution for the visitors the first two layers left in place.

## What the gap looked like on one store

A mechanism is not a number. To see the size and the shape of the gap, you have to run a second measurement next to GA4. When Incapto did that on its Shopify store, with Consent Mode active, for 48 days between 14 June and 31 July 2026, this is what came out.

Incapto: GA4 next to Sealmetrics

Visits GA4 did not record 29%

Pageviews GA4 did not record 45%

Extra traffic seen in direct +11%

Extra traffic seen in organic social +133%

Real orders Sealmetrics recorded 95.7%

One store, one period. Visits, pageviews and orders cover 14 Jun → 31 Jul 2026; the channel figures cover 28 Jul → 6 Aug 2026. Your gap will be different: measure it on your own traffic.

Two things stand out. First, the gap is not the kind that makes a report look broken. It makes it quietly wrong, in a consistent direction, which is why nobody notices. Second, the loss was not even. Channels carrying people who already know the brand barely moved; the ones bringing new people in from an external click lost far more. The [Incapto case study](https://sealmetrics.com/case-studies/incapto.md) has the full channel breakdown and the caveats on each figure.

## Why this is not solvable inside GA4

Google’s answer to consent-based data loss is [Consent Mode v2](https://support.google.com/analytics/answer/9976101). When a visitor rejects cookies, Consent Mode sends “cookieless pings” to Google, which then uses machine learning to model the missing data and fill in the gaps.

This sounds promising until you examine what it actually produces. Consent Mode does not measure the visitors who rejected cookies. It estimates what those visitors probably did based on the behavior of visitors who accepted. The resulting numbers are modeled data, not measurement. Incapto had Consent Mode active throughout the 48 days above.

Modeled data is acceptable for high-level trends. It is not acceptable for campaign-level attribution, conversion path analysis, or revenue decisions. When Google tells you that “estimated conversions” from a campaign are 47, that number is a statistical projection, not a count of real events.

And Consent Mode does nothing about ad blockers or browser restrictions. If gtag.js never loads, no ping is sent — modeled or otherwise.

## What complete data looks like

The alternative is analytics that does not depend on cookies, does not load client-side scripts that can be blocked, and does not require consent for basic measurement.

Sealmetrics uses a [cookieless](https://sealmetrics.com/glossary/cookieless-analytics.md), server-side approach. A lightweight script (under 1 KB), which can be served from a subdomain of your own domain, collects events. No cookies are set. Because nothing is stored on or read from the visitor's device, the cookie-consent requirement has nothing to attach to, and no visits are lost to consent rejection. How complete the rest of the coverage is depends on the implementation, which is why the Incapto figures are reconciled against the store’s real orders rather than asserted.

You can [see how the architecture works](https://sealmetrics.com/how-it-works.md) or [estimate your own data loss](https://sealmetrics.com/data-loss-calculator.md) from your market and consent rates before you measure it.

## Is this unique to GA4?

To be fair: no. Any cookie-based analytics tool — Adobe Analytics, Piwik PRO in its default configuration, Matomo with cookies enabled — faces the same three-layer problem. GA4 is not uniquely bad. It is the most widely used tool that demonstrates a structural limitation shared by the entire category.

The [detailed comparison between Sealmetrics and GA4](https://sealmetrics.com/vs-ga4.md) covers pricing, data ownership, and compliance alongside data completeness. Data completeness is the starting point, but it is not the only difference.

### Related articles

- [How Consent Banners Destroy Your Analytics Data](https://sealmetrics.com/blog/consent-banner-impact-on-analytics.md)
- [GA4 Data Sampling: Why Your Traffic Numbers Are Wrong](https://sealmetrics.com/blog/ga4-data-sampling-problem.md)
- [Cookieless Analytics Explained: How to Measure Without Cookies](https://sealmetrics.com/blog/cookieless-analytics-explained.md)

## Related reading

[How Consent Banners Destroy Your Analytics Data](https://sealmetrics.com/blog/consent-banner-impact-on-analytics.md)

6 min read

[What Is Data Loss in Analytics? Causes, Impact, and Solutions](https://sealmetrics.com/blog/what-is-data-loss-in-analytics.md)

7 min read

[GA4 Data Sampling: Why Your Traffic Numbers Are Wrong](https://sealmetrics.com/blog/ga4-data-sampling-problem.md)

7 min read