Cookie banner traffic loss calculator
Most analytics tools use cookies and collect personal data to identify visitors. Both require consent. Consent requires a banner. And every visitor who declines or simply ignores the banner disappears from your data entirely.
Google Analytics cannot track what it has no permission to touch. The result is a gap between the traffic you actually have and the traffic your dashboard shows you. This calculator estimates the size of that gap.
Cookie banner traffic loss calculator
Enter your reported monthly visitors and adjust the consent acceptance rate to match your audience:
If you want to close this gap entirely, Plausible Analytics is built without cookies, without personal data collection and without any cross-site tracking. Because nothing personal is collected, no consent banner is required under most privacy regulations and every visitor is counted, not just the ones who clicked accept.
What consent rate should I use?
If you have access to your consent management platform’s data, use the actual acceptance rate from there. That will give you the most accurate estimate.
If you do not have that data, these are reasonable starting points based on published research:
- EU/EEA-focused sites: 40–50%. GDPR requires that declining consent be as easy as accepting it. Sites that comply properly see lower acceptance rates. A clearly labeled “Reject All” button will reduce acceptances.
- Mixed global audiences: 50–60%
- US-focused sites: 65–75%. CCPA requirements are less restrictive than GDPR and do not require an opt-in consent model.
Banner design has a significant effect. Hiding the reject option or using dark patterns can push acceptance higher, but those practices carry legal risk under GDPR and are increasingly scrutinized by data protection authorities.
Why the gap grows with EU traffic
GDPR requires that declining consent be as easy as accepting it. A compliant banner must make “Reject All” as prominent and accessible as “Accept All.” That legal requirement directly pushes acceptance rates down on sites that serve European visitors. Sites that bury the reject option or use dark patterns to discourage it may see higher acceptance, but risk regulatory action.
Beyond regulation, privacy-conscious audiences decline at higher rates regardless of where the banner is required. Technical readers, developer communities and ad-heavy sites where visitors associate cookies with ad tracking all tend to see wider gaps.
A study by Orbit Media comparing Google Analytics 4 to Plausible found that GA4 captured only 55.6% of actual traffic, with consent declines as the primary cause. We cover this in more detail in our guide to web analytics accuracy.
The bounce effect
The data gap has a second dimension that the calculator above does not capture.
Some visitors leave immediately when they see a cookie banner, without clicking accept or decline. They close the tab. These visitors never register in analytics at all, not even as a declined consent event. They are not counted in your GA totals. They are not counted in the invisible visitors estimate above.
The banner itself is friction. A fraction of your audience treats it as a reason to leave.
This means the true traffic gap is likely larger than the estimate above.
Where the data gap hits hardest
The consent rate in the calculator above is a single average across all your visitors. In practice, it varies significantly by traffic source, and the variation matters.
Visitors who arrive directly or through a branded search already know you. They chose to come. That prior relationship makes them more likely to trust your site and accept the consent prompt. Their data tends to be relatively well represented in GA.
Visitors arriving from a paid ad or a non-branded organic search are encountering your site for the first time. There is no prior relationship, no established trust. They are more likely to decline. These are also the visitors you spent money to acquire, the ones whose behavior you most need to understand to evaluate whether your campaigns are working.
The result is that GA’s blind spot is largest where it matters most. You get a reasonably complete picture of your returning audience, and a distorted picture of the new visitors you are actively trying to grow.
This is not a limitation you can route around with better attribution models or consent mode estimates. It is structural to any analytics tool that depends on visitor consent.
How cookieless analytics closes the gap
Cookie consent banners exist because personal data is being collected and stored. Remove the personal data collection, and the legal basis for requiring consent goes away. More on why banners exist and what they mean for your site in our cookie consent banners explainer.
Plausible does not use cookies. It does not store any personal data. Sessions and pageviews are measured using aggregate, anonymized counts with no persistent identifiers. Because nothing personal is collected, there is nothing to consent to, and no banner is required in most jurisdictions including under GDPR and CCPA.
Every visitor shows up. The ones who would have declined, the ones who would have bounced from the banner, the ones who block tracking scripts out of habit. None of them disappear.
The consent acceptance rate stops being a variable in your analytics accuracy because consent is no longer part of the equation.
Whether a consent banner is required depends on your specific setup, audience location and any other tools running on your site. If you are running Plausible alongside other tracking tools that use cookies, those tools may still require consent. For a detailed legal assessment of when consent is and is not required, see our guide written by a data protection lawyer. Nothing on this page is legal advice.
If your GA data shows 28,400 visitors per month with a 45% consent rate, your actual traffic is closer to 51,600. Switching to Plausible does not manufacture traffic. It makes the traffic you already have visible.
