REVENUE CLARITY

97% of Your Traffic Is Guessed, Not Tracked.

Consent Mode removed most of your actual visitors from your own analytics, not just added a banner to your site, and your dashboard never told you.

What actually happens when a visitor declines cookies

Under Consent Mode v2, a visitor who declines non-essential cookies still loads your site, still browses, and often still buys. What changes is what Google and Meta are allowed to record about that visit. Instead of a real, observed event, the platform fills the gap with a statistical estimate built from the visitors who did consent. Industry consent-decline rates commonly land in the 90 to 97% range on cookie-strict traffic, depending on the market and the banner design. That's not a rounding error. That's the majority of a session becoming a guess.

Why your dashboard doesn't warn you about this

GA4 and most ad platforms don't label modeled data differently from observed data in the standard view. A conversion is a conversion, whether it came from a real pixel fire or a machine-learning model trained on the sliver of consented traffic. That's the core of the Trust Deficit: the number in front of you doesn't tell you which kind it is, and the two behave very differently once you start making budget decisions off them.

The practical fix isn't a better pixel

No amount of tagging cleverness recovers data a visitor legally declined to share. The fix is architectural: build your own first-party record from the events you're actually allowed to see (server-side purchases, CRM data, your own logged-in sessions) and reconcile that record against what each platform claims, rather than trusting the platform's model to fill the gap invisibly. Claimed and verified numbers should sit next to each other, clearly labeled, so you always know which one you're looking at.

See what a claimed-vs-verified reconciliation looks like against your own numbers.