---
title: "What Is Google Consent Mode v2? — SealMetrics Glossary"
description: "Consent Mode v2 lets Google tags load without cookies when consent is rejected, then models the missing data statistically. A modelling layer, not measurement."
canonical_url: "https://sealmetrics.com/glossary/consent-mode-v2/"
lang: "en"
content_type: "glossary"
owner: "content"
llm_priority: "useful"
last_verified: "2026-08-16"
source: https://sealmetrics.com/glossary/consent-mode-v2/
publisher: SealMetrics
---

Definition

# Google Consent Mode v2

Google’s framework that allows Analytics and Ads tags to load without storing cookies when the visitor has rejected consent, then statistically models the missing data so that GA4 and Google Ads reports show estimated totals instead of only the consenting fraction.

## How it works

When a visitor rejects cookies, Consent Mode v2 prevents the analytics cookie from being written but still fires a “cookieless ping” — a request that records the event without any identifier. Google then aggregates the cookieless pings across many properties and uses a machine-learning model trained on the consenting visitors to estimate what the rejecting visitors probably did: how many sessions, how many conversions, by channel. The estimates appear in GA4 and Google Ads as if they were measured.

## Modelled, not measured

This is the important distinction. Consent Mode v2 fills the gap; it does not close it. The number you see in GA4 with Consent Mode enabled is the consenting 13–40% of EU visitors plus a statistical estimate of the rest. The estimate is useful when you need a ballpark — directionally correct for cross-channel comparisons in stable markets — and unreliable when you need exact reconciliation against CRM revenue, when a new channel mix breaks the training assumptions, or when you are auditing for compliance and the data subject asks “was my visit measured?”.

## When measurement is the right answer

For board-level revenue decisions, for CFO reconciliation, for the cost-of-customer calculations a serious finance team will defend — modelling is the wrong layer. [Cookieless analytics](https://sealmetrics.com/glossary/cookieless-analytics/) measures every visitor on the same anonymous-aggregate basis, with no model in between. See the architectural argument on the [complete data pillar](https://sealmetrics.com/complete-data/).

Consent Mode v2 models what it can't observe. SealMetrics counts what actually happened — compare modelled against measured on your own traffic.

[Book a demo](https://sealmetrics.com/demo/)[See pricing](https://sealmetrics.com/pricing/)

### Related concepts

- [Consent Management Platform (CMP) Software that displays cookie consent banners and manages user preferences. Required under GDPR for websites using cookies or collecting personal data. EU rejection rates vary widely by market — roughly 40-60% on average, and higher in Germany.](https://sealmetrics.com/glossary/consent-management-platform/)
- [GDPR Analytics Compliance Meeting GDPR requirements for web analytics: lawful basis for processing, data minimization, purpose limitation, and — if using cookies — valid consent collection before tracking.](https://sealmetrics.com/glossary/gdpr-analytics-compliance/)
- [Data Loss in Analytics The gap between actual website traffic and what analytics tools report. Caused by consent rejection, ad blockers, browser restrictions, and data sampling. Typically 70-87% in the EU.](https://sealmetrics.com/glossary/data-loss-in-analytics/)
- [Cookieless Analytics Web analytics that captures visitor data without using browser cookies, enabling 100% traffic measurement regardless of consent status or browser restrictions.](https://sealmetrics.com/glossary/cookieless-analytics/)

Learn more: [Why GA4 Shows 13% of EU Traffic](https://sealmetrics.com/blog/why-ga4-shows-13pct-eu-traffic/)

Quick answer

Google Consent Mode v2 is the framework that allows Google Analytics 4 and Google Ads tags to keep working — partially — when a visitor rejects cookie consent. Instead of writing a cookie, the tag fires an anonymous “cookieless ping” that records the event without an identifier. Google then uses a machine-learning model to estimate what the non-consenting visitors probably did across sessions and conversions, and surfaces those estimates in the dashboard alongside the measured consenting visitors.

The result is a modelled total, not a measured one. Useful for directional cross-channel comparisons; unreliable for revenue reconciliation against a CRM, for new-channel attribution where the training data is sparse, or for compliance audits where every individual data subject’s visit must be accounted for. Cookieless first-party server-side measurement removes the model entirely — every visitor is counted on the same anonymous-aggregate basis, with no estimation layer between the event and the number.