Consent loss: calculate the revenue you cannot see

Cookie-based analytics tools like GA4 cannot record anything until a visitor clicks “Accept”. In reality, 30 to 60 percent of visitors reject tracking or dismiss the banner entirely. For online stores, that means 20 to 40 percent of all purchases never show up in your reports, even though orders are flowing normally.

Here is the critical distinction: that revenue is not gone. The orders are real, and the money is in your bank account. What is lost is the attribution: for a massive share of your sales, you have no idea which ad campaign, search keyword, or landing page brought the customer in.

As long as this remains a percentage, nobody acts. Once there is a clear financial figure attached to it, fixing the problem becomes an obvious priority.

You do not need a data science team for this, just three numbers you already have access to:

• 1. Your real consent rate: The ratio of consents to banner views from your CMP. Important: visitors who ignore or close the banner must be counted in the total.
• 2. Your real orders and revenue: Taken straight from your store backend (Shopify, WooCommerce, Stripe, or accounting). This is your ground truth.
• 3. Your analytics-reported numbers: What your analytics tool reports for the exact same month and time zone.

Keep in mind: consent loss is not evenly spread. Mobile visitors and social media traffic reject cookie banners far more frequently than desktop users. The very channels you spend ad dollars on are systematically underreported in your dashboards.

Calculate on a monthly basis to smooth out weekly variations:

Consent rate      = consenting sessions / all real sessions
Invisible orders  = orders (backend) - conversions (analytics)
Invisible revenue = revenue (backend) - revenue (analytics)
Blind factor      = revenue (backend) / revenue (analytics)

The blind factor is your most practical everyday metric: it tells you what multiplier to apply to your analytics reports to see reality. At a blind factor of 1.67, an ad campaign reporting €1,000 in sales actually generated around €1,670.

If you cannot measure total sessions because your tracker sits behind a banner, estimate your consent rate backwards from revenue: revenue (analytics) / revenue (backend). For high-level marketing discussions, this approximation is more than solid enough.

Let us look at a typical mid-sized online store. Real numbers come from the store backend, while analytics numbers come from a standard GA4 setup behind a cookie banner:

Here is what the calculation reveals:

• 288 invisible orders per month (720 minus 432).
• €24,480 in untracked monthly revenue, adding up to €293,760 per year that cannot be attributed to any marketing campaign.
• Blind factor of 1.67: every revenue report in analytics is roughly 40% below reality.

The real harm happens in your advertising accounts, not in spreadsheets. Consider our example store spending €5,000 a month on Google Ads:

The exact same campaign produces two opposite decisions! This is why e-commerce founders constantly complain that Google Ads, Meta, and their store backend all report completely different figures. Beyond ads, A/B tests take months to reach significance, and reporting meetings turn into arguments over data discrepancies rather than strategy.

Google’s Consent Mode v2 uses mathematical modeling to estimate missing data. In practice, it falls short for most businesses:

• High volume requirements: Modeling only kicks in above high thresholds (at least 1,000 events per day with denied consent over seven days). Smaller and mid-sized stores get zero modeling.
• Estimates, not facts: Modeled values cannot be verified against bank deposits or store receipts. You cannot tell whether a spike is real or a modeling glitch.
• The banner stays: Your visitors still face an annoying cookie banner on their first click.

The cleanest way to get reliable numbers is running a side-by-side comparison:

• 1. Install a cookieless tool in parallel: Keep your existing setup running and add a cookieless tool like MetriXs. It loads without consent prompts and captures all real visitors. Both tools coexist cleanly.
• 2. Run for two to four weeks: You will immediately see your true visitor counts and measure your exact consent gap.
• 3. Cross-reference store orders: Compare MetriXs revenue with your store backend. You will find that the numbers line up.
• 4. Drop the banner: Once you are satisfied, turn off Google Analytics and remove the cookie banner for good. WordPress has an official plugin, and Shopify has a dedicated app.

MetriXs tracks revenue, orders, average basket size, and discount codes in real currency and attributes them accurately, with no cookies and no banner.

Consent loss is not a theoretical debate, it is simple subtraction. In our example, the cookie banner blinded the store to 288 orders and €24,480 every month. Run your own numbers once: seeing your real revenue gap settles the analytics question faster than any debate about principles.