Search results and measurement
Consent mode: meaning, examples and practical use
Consent mode adapts the behavior of Google tags and SDKs to a user’s communicated data-consent choices. It is a technical signaling and execution mechanism, not a consent interface by itself, and enabling it does not establish complete legal compliance.
Also known as: Hozzájárulási mód
At a glance
- The choice interface and tag behavior are separate layers.
- Basic and advanced implementations differ before consent is granted.
- Modeled results should not automatically be described as direct observations.
On this page

What is its technical role?
It communicates choices as states and enables supported tags to adapt. Google's overview separates obtaining, communicating and respecting consent. A visible banner does not by itself prove the tags behind it behave correctly.
How do basic and advanced modes differ?
With a basic implementation, Google tags remain blocked without consent. Advanced implementations can transmit limited cookieless signals while consent is denied. “No cookie” is therefore not the same claim as “no data transmission.” The selected behavior must be understood explicitly.
Example: checking after rejection
Imagine a team rejecting measurement consent and inspecting network requests and stored data. It compares the result with the intended implementation. Actual behavior provides evidence that button wording alone cannot supply.
How can reporting change?
The quantity of observed data and eligibility-dependent modeling can change. A configuration change can therefore interrupt comparability with earlier periods. This is distinct from sampling. Determine applicable data-handling requirements for the actual situation rather than treating the presence of one technical setting as a universal compliance certificate.