What Is Consent Mode v2? Privacy-Compliant Measurement
What is Consent Mode v2, what do its four consent signals do, and how do basic and advanced modes differ? A guide to GTM and gtag.js setup, testing and KVKK.
The short answer to what is Consent Mode v2 is this: Consent Mode v2 is an API that tells Google tags what consent a user has given for cookies and advertising data, so the tags can act on that decision. If the user does not consent, Google Analytics and Google Ads tags do not write cookies, send limited cookieless signals, or do not fire at all. Measurement continues while respecting the user’s choice.
In this post I explain how consent mode works, what changed with v2, how basic and advanced modes differ, and what it means for sites in Turkey. In the final sections I share setup steps for Google Tag Manager and gtag.js, a testing method and my pre-launch checklist.
How does Consent Mode v2 work?
Short answer
How does Consent Mode work?
Consent Mode sets a default state for each consent type when the page opens. When the user makes a choice in the cookie banner, that state is updated. Google Analytics and Google Ads tags read the current consent state on every request; with consent they work normally, and without it they send limited signals without cookies or do not fire.
Consent mode relies on two commands: default and update. The default command defines the state before the user has chosen anything. The update command tells the tags about the user’s decision in the banner.
There is an important distinction here. Consent Mode is not a cookie banner or a consent form itself. Google’s server-side tagging documentation says this clearly: consent mode does not provide a banner, it interacts with a consent management platform.[3] A consent management platform, or CMP (Consent Management Platform), is the software that collects and records the user’s decision.
According to Google’s documentation, the Google tag, Google Analytics, Google Ads, Floodlight and Conversion Linker tags have built-in consent checks.[1] These tags read the consent state themselves. For tags without built-in checks, an additional consent condition can be set in each tag’s advanced settings in Tag Manager.[1]
Which consent signals does Consent Mode v2 include?
Consent Mode v2 manages advertising and analytics measurement with four main parameters: ad_storage, analytics_storage, ad_user_data and ad_personalization. The first two cover storage permission in the browser, and the last two cover the use of data for advertising. Google states that it updated consent mode with these two new parameters in November 2023.[2]
| Parameter | What does it control? |
|---|---|
ad_storage | Storage of advertising cookies and device identifiers |
analytics_storage | Storage of analytics cookies, such as visit duration |
ad_user_data | Sending user data to Google for online advertising |
ad_personalization | Personalized advertising and remarketing |
This table is based on Google’s list of consent types.[1] The same list also includes functionality_storage, personalization_storage and security_storage. Functions such as language preference, content recommendations and security can be managed separately with these types.
This is exactly where v1 and v2 differ. v1 only asked about storage: can cookies be written? v2 asks two more questions that are independent of storage. Can user data be sent to Google for advertising? Can personalized ads be shown with that data?
In practice, this distinction has a clear consequence. According to Google, when ad_personalization is denied, remarketing and personalized advertising features in Google Ads receive no data.[1] So a user can allow analytics while refusing personalization, and tags must apply this fine distinction correctly.
What is the difference between basic and advanced Consent Mode?
In basic Consent Mode, Google tags do not load at all until the user interacts with the banner; in advanced mode, tags load when the page opens and send cookieless signals if consent is denied. The difference is whether any information about a non-consenting user reaches Google.
Basic Consent Mode
- Tags are blocked until the user interacts with the banner
- No data reaches Google before consent
- If consent is denied, not even the consent state is sent
- Google Ads modeling relies on a general model
- Setup and legal assessment are simpler
Advanced Consent Mode
- Tags load with default states when the page opens
- Cookieless pings are sent if consent is denied
- With consent, cookies are written and full measurement starts
- Advertiser-specific, more detailed modeling is used
- Cookieless signals need their own legal assessment
This comparison is based on Google’s own table.[1] Google writes that advanced mode offers improved modeling because it provides an advertiser-specific model instead of a general one.[1] Conversion modeling is a statistical method that estimates conversions that cannot be measured from non-consenting users, based on consented traffic and cookieless signals.
A cookieless ping is the limited signal sent in advanced mode when consent is denied. According to Google’s list, these signals include fields such as the timestamp, user agent, referrer, consent state and whether the URL contained ad-click information.[1] No cookies are written or read.
Choosing a mode is primarily a legal and organizational decision, not a technical one. Google’s own setup guide also recommends checking your company’s guidelines when picking the mode and default values.[2]
Is Consent Mode v2 mandatory for sites in Turkey?
Google’s EU user consent policy covers end users in the European Economic Area, the UK and Switzerland.[5] Under the policy, legally valid consent must be obtained from these users for the use of cookies and for personalized ads, consent records must be kept, and how to withdraw consent must be explained clearly.[5] For any site that gets traffic from these regions, Consent Mode v2 is directly on the agenda.
In Turkey, this situation is common in two sectors in particular. Health tourism sites attract prospective patients from Europe, and e-commerce sites may sell abroad. Even if the site’s server or the company’s headquarters is in Turkey, the visitor’s location determines whether the policy applies.
The situation is different for a site that only serves Turkey. Here the deciding framework is KVKK, Turkey’s data protection law, and related regulations. In this case too, reflecting cookie choices correctly in tags means the “reject” option in the banner actually carries meaning.
How do you set up Consent Mode v2?
Short answer
How do you set up Consent Mode v2?
To set up Consent Mode v2, you first choose a consent management platform that supports Consent Mode. A default state is set for each consent type while the page loads. When the user makes a choice in the banner, the state is updated, and the setup is verified with Tag Assistant.
- Choose a CMP that supports Consent Mode or prepare your own banner.
- Map banner categories to the four Google parameters.
- Set the default consent state before any command that sends measurement.
- Update the consent state when the user makes a choice.
- Define different defaults per region if needed.
- Test the default and updated states with Tag Assistant.
There are two routes for setup: Google Tag Manager and gtag.js directly. For sites that use Tag Manager and manage their own banner, Google recommends loading the banner through the Tag Manager container with a consent mode template.[2] CMP templates from the Community Template Gallery can also be used for this.
- Map the categories
Write down which Google parameter each CMP category, such as "marketing" or "analytics", corresponds to. In most setups, the marketing category controls ad_storage, ad_user_data and ad_personalization together.
- Set the default state
If you use gtag.js, run the consent default command on every page before config and event commands. In Tag Manager, a consent mode template or the setDefaultConsentState API handles this.
- Wire up the update
Make sure the consent update command runs on the same page where the user makes a choice, before any page transition. In Tag Manager templates, use the updateConsentState API.
- Define region settings
If you only show the banner in certain regions, limit the default state to those regions with the region parameter. Add a separate default command for all other regions.
- Check the server container
If you use server-side GTM, verify that the consent state travels from the web container to the server in the HTTP request. Google tags on the server behave according to this signal.
With gtag.js, the simplest default setup starts all four parameters as denied. Code based on Google’s example looks like this:[2]
// Must run BEFORE any command that sends measurement
gtag('consent', 'default', {
'ad_storage': 'denied',
'ad_user_data': 'denied',
'ad_personalization': 'denied',
'analytics_storage': 'denied',
'wait_for_update': 500
});
// When the user clicks "Accept all" in the banner
gtag('consent', 'update', {
'ad_storage': 'granted',
'ad_user_data': 'granted',
'ad_personalization': 'granted',
'analytics_storage': 'granted'
});
The wait_for_update parameter sets how many milliseconds tags wait for a consent update when the banner loads asynchronously.[2] For a region-specific default, a region array with ISO 3166-2 codes is added to the same command. According to Google, if there are two separate commands for a region and a subregion, the more specific one takes effect.[2]
Consent Mode with server-side GTM
In a server-side setup, it is enough to configure consent mode in the web container only. According to Google, the Google tag sends the user’s preferences to the server container by adding consent parameters to the HTTP request.[3] Google product tags on the server adjust the type and amount of data they send based on these parameters.[3]
This architecture solves a point that is often missed in server-side tracking setups. If the server sends data to platforms without knowing the consent state, the user’s choice stays in the browser but gets lost in measurement. I explained the server container setup step by step in the server-side GTM setup post.
How do I check that Consent Mode v2 is working?
The most reliable way to verify Consent Mode v2 is Google Tag Assistant. Tag Assistant shows whether the default consent state is set before tags fire and whether it updates correctly after the user’s choice.[4] It also lists which consent type each tag checks and whether the required consent was granted when the tag fired.[4]
The test works like this. You open your site’s address in Tag Assistant, then select the earliest Consent event in the Summary section. In the API Call section, you check that the four parameters are set.[4] Then you choose “accept” in the banner, and “reject” in a separate session, to confirm that the update works both ways.
If you use region-specific defaults, Google recommends repeating the test with different simulated locations.[4] On a health tourism site with European traffic, skipping this step can mean everything looks right in a test from Turkey while the setup fails for European visitors.
What are common Consent Mode mistakes?
The most common Consent Mode mistake is running the default consent command after measurement commands. In that case the first page view is sent without waiting for consent, and the setup fails at the very first request. Other mistakes also mostly come from ordering, mapping and scope problems.
- Missing v2 parameters: Older setups often have only
ad_storageandanalytics_storagedefined. Google recommends that existing users upgrade to v2.[2] - A visible banner, a powerless decision: The banner offers a “reject” option, but the decision never reaches the tags. For the user consent was denied; for the tags nothing changed.
- Forgetting non-Google tags: Meta Pixel or the TikTok pixel do not read Consent Mode on their own. These tags need a separate consent condition in Tag Manager.
- Updating after a page transition: Google stresses that the consent update must be processed on the page where the choice is made, before any page transition.[2]
- CRM data drifting away from consent: User data sent from the server with offline conversions or Enhanced Conversions is processed independently of the consent decision in the browser. Even with hashing, you need to make sure this data relies on the same consent.
Where should you start?
Consent Mode v2 is a consent layer that carries the user’s decision about cookies and advertising data to Google tags. With four parameters, it manages storage, advertising use of data and personalization separately. The choice between basic and advanced mode balances modeling quality against your legal approach. It is not a banner, a compliance certificate or a fix that eliminates data loss.
My recommendation is to first map CMP categories to the four Google parameters, then confirm in Tag Assistant that the default command runs before everything else. After that, non-Google tags and the server side need to be tied to the same consent decision. You can read how I build measurement infrastructure together with ad management on the performance marketing page, and my background on the about page.
Key terms
- Consent Mode v2
- Consent Mode v2 is a consent API that passes a user's cookie and advertising data choices to Google tags and determines whether those tags may write cookies. It is also known as Google consent mode and includes the ad_user_data and ad_personalization parameters.
- CMP
- A CMP (Consent Management Platform) is software that shows the cookie banner on a site, collects the user's consent choices and stores them. A CMP that supports Consent Mode passes the user's decision to Google tags automatically.
- Cookieless ping
- A cookieless ping is the limited measurement signal that Google tags send in advanced Consent Mode when a user denies consent, without reading or writing cookies. It carries information such as consent state, timestamp and whether an ad click occurred, and it is used in conversion modeling.
- Conversion modeling
- Conversion modeling is a statistical method in which Google Ads and Google Analytics estimate conversions that cannot be measured directly from users who denied consent, based on consented traffic and cookieless signals. Advanced Consent Mode uses an advertiser-specific model.
Frequently asked questions
What is Consent Mode v2?
Consent Mode v2 is an API that tells Google tags what a user has chosen for cookies and advertising data, so the tags can behave accordingly. The November 2023 update added the ad_user_data and ad_personalization parameters. It is not a cookie banner itself; it works together with a consent management platform.
Does setting up Consent Mode v2 make a site KVKK compliant?
No. Consent Mode only carries the user's decision to Google tags. Obligations such as the privacy notice, explicit consent, consent records and a way to withdraw consent must each be met separately. For a legal assessment, get advice from a KVKK specialist.
Do I need Consent Mode v2 if I only advertise in Turkey?
Google's EU user consent policy covers users in the European Economic Area, the UK and Switzerland. If you get traffic from these regions, Consent Mode v2 is directly relevant to you. For a site that only serves Turkey, reflecting cookie choices correctly in your tags is still the practical way to build measurement that is consistent with KVKK.
What is the difference between basic and advanced Consent Mode?
In basic mode, Google tags do not load at all until the user interacts with the banner, and no data reaches Google without consent. In advanced mode, tags load when the page opens and send cookieless signals if consent is denied. According to Google, advanced mode provides advertiser-specific, more detailed conversion modeling.
How do I check that Consent Mode v2 is working?
Open your site with Google Tag Assistant and select the first Consent event in the Summary section. Check that the default values for the four parameters are set before any tags fire, and that they update after you make a choice in the banner. If you use region-specific defaults, repeat the test with different locations.
Sources
The full topic: Tracking guide ↗ · Analytics guide ↗