Google Analytics Consent Mode is a Google framework that lets a website communicate a visitor’s consent choices to Google. Google tags then adjust how they collect and store data based on those choices. Consent Mode works with a consent banner or Consent Management Platform (CMP); it does not provide the banner itself.
If you use Google Analytics 4 (GA4), you may have noticed that privacy and measurement no longer fit neatly into a simple “install the tracking code and collect everything” model. Visitors can make different consent choices, privacy rules can vary by region, and Google needs to know what those choices mean before its tags determine how they behave.
That is where Google Analytics Consent Mode comes in. It connects the consent decision made by a visitor with the behavior of Google tags used for analytics and advertising.
The important part is understanding what Consent Mode does, what it does not do, and what happens to your GA4 measurement when someone accepts or rejects consent.
What Is Google Analytics Consent Mode?
Google Analytics Consent Mode is a framework that communicates a user’s consent status to Google so Google tags can adjust their behavior. It can control how Google Analytics and advertising-related tags handle storage and data use based on the consent state.
Consent Mode sits between your consent solution and Google’s measurement systems. A typical flow looks like this:
- A visitor arrives at your website.
- Your consent banner or CMP presents the relevant choices.
- The visitor grants or denies specific types of consent.
- The consent solution communicates those choices to Google.
- Google tags adjust their behavior according to the consent state.
- GA4 and other Google products receive the type of measurement data permitted by that state.
Google describes this process as three core steps: obtain the user’s consent, send the user’s choice to Google, and ensure Google tags comply with that choice.
How Consent Mode Works With GA4
GA4 can use Consent Mode to understand whether analytics-related storage has been granted or denied. The relevant consent state is communicated through parameters such as analytics_storage.
When analytics storage is granted, Google Analytics can use the storage allowed by the consent state. When analytics storage is denied, Google tags change their behavior instead of simply treating the visitor as though unrestricted analytics storage were available.
This distinction matters because “consent denied” does not always mean that every form of communication with Google disappears. The result depends on the Consent Mode implementation and the consent types involved.
What Consent Mode Does – and Does Not Do
Consent Mode communicates consent choices and changes Google tag behavior. It does not replace the system that obtains the visitor’s consent.
Google explicitly states that Consent Mode does not provide a consent banner or widget. A website still needs a banner, CMP, or another appropriate consent solution to obtain the user’s choice.
If you are evaluating the technology responsible for collecting and managing those choices, see our guide to Consent Management Platform.
This distinction is essential: a CMP manages consent collection, while Consent Mode communicates consent to Google and changes tag behavior.
How Google Analytics Consent Mode v2 Works
Consent Mode v2 expanded Google’s consent framework with two additional advertising-related consent signals: ad_user_data and ad_personalization. These work alongside the existing ad_storage and analytics_storage signals. Google says Consent Mode was updated in November 2023 to include the two additional parameters.
The four signals have different purposes.
analytics_storage
analytics_storage controls storage related to analytics, such as analytics cookies. It is the consent signal most directly connected with Google Analytics measurement.
If analytics storage is denied, Google tags must adjust their behavior rather than treating the visitor as having granted analytics storage.
ad_storage
ad_storage controls storage related to advertising, including advertising cookies. Google documents this consent type as controlling advertising-related storage.
This matters when your website uses Google Ads or other Google advertising features alongside GA4.
ad_user_data
ad_user_data controls consent for sending user data related to advertising to Google. Google notes that this consent type is relevant to measurement use cases such as enhanced conversions and tag-based conversion tracking.
It is therefore different from simply asking whether advertising cookies may be stored.
ad_personalization
ad_personalization controls consent for personalized advertising.
A visitor might therefore make different choices about analytics, advertising storage, advertising-related data use, and personalized advertising. Consent Mode gives Google separate signals for those decisions.
What Happens to GA4 Data When Users Deny Consent?
The answer depends on the consent type and the Consent Mode implementation.
When a visitor grants the relevant consent, Google tags can operate normally within the permissions represented by that consent state. When consent is denied, consent-aware tags change their behavior and avoid the storage or data use that the denied consent restricts.
The most important difference appears when comparing Basic and Advanced Consent Mode.
When a Visitor Grants Consent
When the required consent is granted, Google tags can send the fuller measurement data permitted by the consent state. For analytics, this can allow GA4 to use the relevant storage and measurement capabilities.
Consent Mode does not create a separate version of GA4. Instead, it changes how Google’s tags behave before and after the consent decision.
When a Visitor Denies Consent
With denied consent, Google tags do not simply continue behaving as though the visitor had granted permission.
In Advanced Consent Mode, Google says consent-aware tags can send cookieless pings while consent is denied. These signals can communicate consent state and certain measurement information without writing the relevant cookies.
That creates an important distinction:
Cookieless measurement is not the same thing as unrestricted cookie-based tracking.
The data available to Google is different, and Google can use appropriate modeling techniques to help fill measurement gaps where eligible.
Cookieless Pings and Consent Signals
When consent is denied, consent-aware Google tags can communicate information through cookieless pings. Google documents different types of consent and measurement signals, including consent state information and other signals used for modeling.
This is one reason it is misleading to describe Consent Mode simply as “turning Google Analytics off.”
A better mental model is:
Consent choice -> consent signal -> tag behavior -> available measurement
The resulting data depends on what the visitor allowed and how your Consent Mode implementation is configured.
Basic vs Advanced Consent Mode
Google provides two primary Consent Mode implementation approaches: Basic Consent Mode and Advanced Consent Mode. They differ mainly in when Google tags load and what happens before the visitor grants consent.
| Feature | Basic Consent Mode | Advanced Consent Mode |
| Google tags before consent interaction | Blocked | Load with consent-aware defaults |
| Data before consent | No data is sent | Cookieless pings can be sent when consent is denied |
| Consent state before interaction | Not transmitted because tags are blocked | Communicated according to the configured defaults |
| After consent is granted | Tags load and operate according to consent | Tags update their behavior according to consent |
| Modeling | General model | Advertiser-specific modeling |
| Implementation approach | Simpler data flow | More measurement capability but requires careful configuration |
How Basic Consent Mode Works
With Basic Consent Mode, Google tags are prevented from loading until the visitor interacts with the consent banner. Google states that no data is transmitted to Google before that interaction.
If the visitor grants consent, the Google tags load and Consent Mode APIs communicate the relevant consent states.
If the visitor does not consent, Google tags remain blocked and no data is transferred to Google, including the consent status itself.
This provides a straightforward data-flow model, but it also means Google has less information available for certain modeling capabilities.
How Advanced Consent Mode Works
Advanced Consent Mode allows Google tags to load before the visitor makes a consent choice. The tags use configured default consent states and adjust their behavior when the visitor interacts with the consent banner.
When relevant consent is denied, Google says the tags can send cookieless pings instead of using the relevant cookies. When consent is granted, the tags can send the full measurement data permitted by the consent state.
Google says this implementation can provide improved modeling compared with Basic Consent Mode because it can support an advertiser-specific model rather than only a general model.
Choosing an Implementation Approach
There is no universal answer that Basic or Advanced Consent Mode is right for every website.
The decision depends on factors such as:
- Your consent architecture
- The regions in which consent is required
- Your CMP configuration
- Your privacy requirements
- Your measurement goals
- Your Google Ads setup
- Your development and testing resources
The key is to understand the data flow before choosing an implementation.
If your organization wants to use Advanced Consent Mode, pay particular attention to the default consent configuration and how your CMP interacts with Google tags. A configuration that looks correct in the banner can still produce incorrect tag behavior if the underlying consent signals are not being sent correctly.
Does Google Analytics Consent Mode Make a Website Compliant?
No. Consent Mode should not be treated as a complete legal compliance solution.
Consent Mode is a technical framework for communicating consent choices and adapting Google tag behavior. Your website still needs an appropriate consent and privacy approach for the jurisdictions and activities that apply to your business. Google itself describes consent management as a broader process that includes obtaining consent, communicating the choice, and ensuring tags respect it.
Consent Mode and GDPR
For websites dealing with users in jurisdictions where specific consent requirements apply, Consent Mode can be an important technical component of the measurement setup.
However, implementing Consent Mode does not by itself determine whether your organization satisfies GDPR or another privacy law. Legal requirements depend on your processing activities, users, jurisdictions, and other factors.
Consent Mode and US Privacy Requirements
For US businesses, privacy obligations can vary by state and by the type of data processing involved.
That means you should avoid treating “USA” as one single consent regime. A website serving users in different states may have different obligations depending on its business model, data practices, and applicable laws.
Consent Mode can help your technical implementation respect the consent signals you collect, but it does not replace legal advice, privacy disclosures, or a properly designed consent-management process.
Why Consent Mode Alone Is Not a Compliance Solution
Think of compliance as a larger system.
Privacy requirements -> consent strategy -> consent collection -> Consent Mode -> tag behavior -> verification
Consent Mode sits inside that system. It does not replace the other components.
How to Set Up Google Analytics Consent Mode
The exact setup depends on whether you use a CMP, Google Tag Manager, gtag.js, or another implementation.
Google’s current documentation recommends starting with a mechanism that obtains user consent before configuring the consent signals sent to Google.
Choose a Consent Banner or CMP
First, establish how your website will obtain the visitor’s consent choice.
You can maintain your own consent solution or use a Consent Management Platform. Google documents integrations with numerous CMP providers and notes that many CMPs can handle sending consent states to Google.
Your consent solution should clearly map the choices presented to visitors to the relevant consent signals used by Google.
Configure Consent Mode
Configure the default consent state before the visitor makes a choice, then update that state when the visitor interacts with the consent mechanism.
For websites using their own consent solution, Google’s developer documentation says the implementation should set a default consent state and then update it based on the user’s interaction.
The relevant signals can include:
- analytics_storage
- ad_storage
- ad_user_data
- ad_personalization
Connect Consent Mode to GA4
Your Google tag and GA4 configuration must be able to receive and respect the consent state.
If you use Google Tag Manager, Google provides consent settings that can control tag behavior. Google tags with built-in Consent Mode support can automatically adjust their behavior according to the consent state.
Configure Google Tag Manager When Needed
Google Tag Manager provides a Consent Overview feature and consent settings that can help control tags that do not have built-in consent checks.
This is especially useful when a website contains third-party tags beyond Google Analytics and Google Ads.
Do not assume that installing Consent Mode automatically makes every third-party script consent-aware. Tags without built-in consent checks may require additional configuration in Tag Manager.
Test the Implementation
Do not publish a Consent Mode configuration based only on what the consent banner appears to do.
Test at least two states:
Consent granted
Verify that the appropriate consent signals change and that permitted measurement works.
Consent denied
Verify that the relevant storage remains denied and that tags behave according to your selected Consent Mode implementation.
Google recommends using Tag Assistant to verify Consent Mode implementations.
How Consent Mode Affects GA4 Behavioral Modeling
One of the most important reasons to understand Consent Mode is its relationship with modeled measurement.
When users deny analytics storage, GA4 may not have the same observable information that it would have if those users had granted analytics consent. Behavioral modeling can help estimate some of the missing behavior when the property meets Google’s requirements.
Observed vs Modeled Data
Observed data comes from measurement that Google can directly receive and process.
Modeled data is an estimate based on observed patterns.
That distinction matters. Behavioral modeling does not magically recreate the exact identity or actions of every visitor who declined consent.
Instead, Google’s modeling systems use available signals and observed patterns to estimate behavior where eligible.
How Behavioral Modeling Works
Google describes behavioral modeling as a machine-learning approach that can estimate the behavior of users who decline analytics cookies by learning from users who consent.
The purpose is to reduce gaps in measurement while respecting the consent state.
This can be useful for understanding aggregate trends, but modeled results should not be interpreted as direct observation of every user who declined consent.
Modeling Eligibility
Behavioral modeling is not automatically available to every GA4 property.
Google applies eligibility requirements and data thresholds before modeling becomes available. Those requirements can change, so implementation teams should check Google’s current documentation rather than relying on an old tutorial.
The important takeaway is simple:
Implementing Advanced Consent Mode does not guarantee that your GA4 property will immediately receive modeled data.
Eligibility depends on Google’s requirements and the data available to the property.
What Modeled Data Cannot Tell You
Modeled data should not be treated as an exact replacement for missing consented data.
It can help estimate aggregate behavior, but it does not mean Google has obtained the same identifiable or cookie-based information from users who declined consent.
That distinction is important when interpreting GA4 reports, conversions, audiences, and attribution.
How to Verify Google Analytics Consent Mode
A Consent Mode implementation is not finished when the banner appears on the screen. It is finished when the underlying consent signals and tag behavior have been tested.
Google provides Tag Assistant instructions specifically for checking Consent Mode.
Test Consent States With Google Tag Assistant
Open your website through Tag Assistant and inspect the consent events.
Google’s verification process specifically recommends checking the earliest Consent event and confirming that the expected parameters are present, including:
- ad_storage
- ad_personalization
- ad_user_data
- analytics_storage
Then interact with your consent banner and inspect the updated Consent event to verify that the signals change as expected.
Check Consent Signals in GA4
Your implementation should produce the consent states expected by your configuration.
Pay particular attention to the four main Consent Mode signals:
analytics_storage, ad_storage, ad_user_data, and ad_personalization.
Google provides GA4 documentation for verifying and updating consent settings and recommends upgrading existing implementations to Consent Mode v2 where applicable.
Check Tag Behavior
Do not stop after checking the consent API.
Also verify whether Google tags and relevant third-party tags behave correctly in each consent state.
For example, if analytics storage is denied, investigate whether the expected analytics cookies are still being written. If advertising consent is denied, verify that advertising-related tags respect the configured restrictions.
A technically valid-looking consent banner does not prove that every tag on the page is respecting the visitor’s choice.
Common Google Analytics Consent Mode Mistakes
Treating Consent Mode as a CMP
Consent Mode does not collect consent. It communicates consent to Google.
A banner or CMP is still needed to obtain the visitor’s choice.
Blocking or Loading Tags Incorrectly
Basic and Advanced Consent Mode have different data flows.
Using instructions designed for one implementation while configuring the other can produce unexpected measurement behavior.
Missing Consent Mode v2 Signals
Older implementations may not include ad_user_data and ad_personalization.
Google’s current documentation identifies these as part of Consent Mode v2, so existing implementations should be checked rather than assuming an older configuration remains sufficient.
Testing Only the Accepted State
A consent implementation should be tested with consent both granted and denied.
The denied state is often where configuration problems become visible.
Assuming Modeling Recovers Exact Missing Data
Modeling can estimate behavior, but it does not turn denied-consent visitors into directly observed users.
Treat modeled results as modeled results.
Assuming Consent Mode Automatically Provides Legal Compliance
Consent Mode is a technical component of a broader consent and privacy system.
It cannot determine whether your organization’s overall data practices comply with every applicable law.
Google Analytics Consent Mode FAQ
The answer depends on your website, users, jurisdictions, data practices, and the Google products you use. Consent Mode is Google’s mechanism for communicating consent choices to Google tags, but whether a particular implementation is legally or operationally required depends on the circumstances. Google also has specific consent requirements for certain advertising and measurement use cases.
Not every website can be treated the same way. Whether consent is required depends on applicable privacy requirements and how your website collects and uses data. GA4’s Consent Mode provides a way for your implementation to communicate the user’s analytics consent state to Google and adjust tag behavior accordingly.
Consent Mode v2 is the updated version of Google’s Consent Mode framework that includes the ad_user_data and ad_personalization consent signals in addition to ad_storage and analytics_storage. Google introduced those additional parameters as part of the November 2023 Consent Mode update.
Basic Consent Mode blocks Google tags until the visitor interacts with the consent banner, so no data is sent before that interaction. Advanced Consent Mode loads Google tags with consent-aware defaults and can send cookieless pings when relevant consent is denied. Google says Advanced Consent Mode can support more detailed advertiser-specific modeling.
The relevant Google tags adjust their behavior according to the denied consent state. With Advanced Consent Mode, Google tags can send cookieless pings rather than storing the relevant cookies. Depending on eligibility, Google can use modeling to help estimate behavior that cannot be directly observed.
No. Consent Mode is a technical mechanism for communicating consent and adjusting Google tag behavior. It does not by itself make a website compliant with GDPR or another privacy law. Your organization still needs an appropriate privacy and consent framework for the jurisdictions and data practices that apply to it.
The answer depends on the implementation and consent state. Advanced Consent Mode can send cookieless signals when relevant consent is denied, while Basic Consent Mode blocks Google tags until the visitor interacts with the banner. The resulting measurement is therefore different from normal cookie-based GA4 measurement.
What to Check Before You Publish Your Consent Setup
Before publishing a Google Analytics Consent Mode implementation, verify the entire chain rather than just the consent banner.
Check that:
- Your consent banner or CMP correctly captures user choices.
- The relevant Consent Mode signals are configured.
- analytics_storage is mapped correctly.
- ad_storage is mapped correctly.
- ad_user_data is mapped correctly.
- ad_personalization is mapped correctly.
- Your selected Basic or Advanced implementation behaves as intended.
- Google tags respect denied consent.
- Third-party tags have appropriate consent controls.
- Granted and denied states have both been tested.
- Tag Assistant shows the expected consent events.
- GA4 receives the intended consent signals.
- Your privacy and legal requirements have been reviewed separately from the technical implementation.
Google’s own verification workflow specifically recommends checking the default and updated consent events and confirming the four primary consent parameters.
The most useful way to think about Google Analytics Consent Mode is not as another GA4 setting. It is the connection between a visitor’s privacy choice and the behavior of Google’s measurement and advertising tags.
Get that connection right, and your analytics setup can respond to consent states in a structured way instead of treating every visitor as though they had made the same choice.
For businesses that use GA4 alongside Google Ads and other marketing measurement systems, that consent-aware architecture becomes increasingly important as privacy requirements and Google’s measurement controls evolve.
For broader measurement topics, you can also explore Dynamic Number Insertion and Google Ads Call Tracking to understand how other attribution systems connect marketing activity with conversions.
