Setting up Consent Mode v2: basic or advanced, and checking that it works

Updated 10 min read

Consent Mode v2 passes the choice from your cookie banner on to Google, so Google Ads and GA4 adjust their tags accordingly. Since March 2024, you have to pass on that choice for visitors from the EEA, or you lose audiences, remarketing and personalized ads for them. I set it up with your cookie banner and Google Tag Manager, then check in Tag Assistant, GA4 and Google Ads that the signals actually arrive.

Why set up Consent Mode v2 properly?

  • Remarketing in the EEA Without consent signals, Google doesn't use visitors from the EEA for remarketing and personalized ads.
  • Modeled conversions In advanced mode, Google estimates conversions from visitors who decline, using a model built for your account.
  • Visitor's choice respected As long as someone hasn't agreed, the Google tags don't set cookies for advertising or analytics.
  • Tested after launch I check in Tag Assistant, GA4 and the Google Ads diagnostics that the signals arrive.
  • Meta handled separately Consent Mode only controls Google tags. The Meta pixel gets its own consent check.

Consent Mode (called 'toestemmingsmodus' in Google's Dutch help pages) is a feature that passes your visitor's consent choice on to the Google tags on your site: the Google tag, Google Analytics, Google Ads, Floodlight and the Conversion Linker. Those tags adjust their behavior accordingly. If someone doesn't give consent, they don't read or write cookies for advertising or analytics.

The consent management platform (CMP) behind your cookie banner turns that choice into four signals. The 'v2' refers to the last two, which Google added in November 2023. Before that, there were only ad_storage and analytics_storage.

  • ad_storage: cookies for advertising, such as the cookies Google Ads uses to link a click to a conversion.
  • analytics_storage: cookies for analytics, such as visit duration in Google Analytics.
  • ad_user_data: consent to send user data to Google for advertising, such as the hashed email addresses from enhanced conversions.
  • ad_personalization: consent for personalized ads, including remarketing.

Your cookie banner asks for consent, and Consent Mode v2 tells each Google tag what it may do with that choice.

In early March 2024, Google tightened enforcement of its EU User Consent Policy. If you advertise with Google tags and your site gets visitors from the European Economic Area (EEA), you have to ask for their consent and pass that choice on to Google. That applies to measurement, remarketing and personalized ads.

If the signals are missing, the first place you notice it is your audiences. Audiences you share from GA4 with Google Ads then only contain visitors from outside the EEA. Remarketing and personalized ads require the visitor's explicit consent.

If you already had Consent Mode in its old form, Google has copied the ad_storage value to ad_user_data for EEA visitors since March 2024. That doesn't happen for ad_personalization. If you want to keep audiences and personalization in the EEA, that signal has to be added explicitly.

If your banner blocks the Google tags completely until someone makes a choice, without Consent Mode, Google can't verify consent. According to Google, that can lead to data loss.

Request your free Quick Scan

Basic and advanced: what happens to your tags

You can set up Consent Mode in two ways. With basic, the Google tags only load once someone has clicked on the cookie banner. If the visitor declines, nothing goes to Google, not even the choice itself. For conversion modeling in Google Ads, Google then uses a general model.

With advanced, the tags load right away, with the default status set to denied. As long as there's no consent, they send cookieless pings. These include the timestamp, the browser, the referring page and whether ad information such as a gclid was in the URL. After consent, the tags measure fully. Google then models with a model specific to your account.

BasicAdvanced
Tags load After a choice Immediately
When declined Nothing to Google Cookieless pings
Model in Google Ads General model Per advertiser
Modeling in GA4 Not possible Above a threshold
Data without consent None Limited pings

Choosing basic or advanced

Google leaves the choice to you and refers to your own organization's guidelines. My starting point is advanced, unless your privacy policy doesn't allow a single request to Google without consent.

Advanced only pays off if there's enough traffic to model. For a local business I work with, advanced worked fine technically. The number of clicks was simply too low for modeling in Google Ads and GA4. In that case, the gain is mainly in a banner that gets more visitors to make a choice.

Advanced fits if

  • You optimize for conversions in Google Ads and get a lot of clicks from the EEA
  • You also want GA4 to model the behavior of visitors who decline
  • Whoever decides on privacy at your company is fine with cookieless pings

Basic fits if

  • Your policy doesn't allow a single request to Google before a choice is made
  • Your volume stays well below the modeling thresholds

Most problems come down to the order. The default status has to be in place before a single tag measures anything. This is how I set it up:

  1. 1

    Choosing or checking the CMP

    Google keeps a list of certified CMPs, including Cookiebot, Complianz, CookieYes, OneTrust and Didomi. They pass the visitor's choice on to Consent Mode themselves. According to Google, a CMP outside that list is allowed too. In that case, I check extra carefully that all four signals come through.

  2. 2

    Default status before all tags

    For visitors from the EEA, the four signals are set to denied by default. In Google Tag Manager, I put the CMP tag on the Consent Initialization trigger, so that status is in place before other tags fire. The default status must not be set asynchronously.

  3. 3

    Update after every choice

    When someone clicks accept or decline, the CMP sends an update. That also has to work later: a link to the cookie settings, for example in the footer, lets visitors change their choice in either direction.

  4. 4

    Consent on other tags

    Google tags have a built-in consent check. Tags from Meta, TikTok or LinkedIn, for example, get an additional consent check in Tag Manager, so they only fire after consent.

  5. 5

    Preserving click information

    With url_passthrough, the Google tag passes click and session information through your site's URLs when cookies aren't allowed. That makes the click information less likely to get lost between the landing page and the thank-you page.

Each signal has its own consequence. This is what you see in the accounts when a visitor declines:

  • Google Ads: without ad_storage, the tag doesn't read or write advertising cookies. Google partly fills in missing conversions with modeling, and names a threshold of 700 ad clicks over 7 days per domain and country combination.
  • Remarketing: without ad_personalization, your remarketing lists in Google Ads don't receive any data from that visitor.
  • Enhanced conversions: without ad_user_data, the tag doesn't send hashed customer data. So enhanced conversions only works for visitors who consented to it.
  • GA4: without analytics_storage, Google Analytics doesn't set analytics cookies. The behavior of visitors who decline is only modeled from 1,000 events per day with denied consent, for 7 days, and 1,000 users per day with consent on at least 7 of the last 28 days.

No. Google Consent Mode only controls Google tags. For the Meta pixel, you handle consent separately, and Meta explicitly places responsibility for GDPR compliance with the advertiser.

With one client, I saw what that means in practice. Visitors from Meta ads often only gave consent on a later page. By then the Meta click ID was no longer in the URL, and Meta struggled to link the leads to the ads. A banner that asks for a choice on the landing page itself limits that loss.

If you also use the Conversions API, the same visitor choice applies there. For the pixel, there are two routes:

  • Loading the pixel only after consent for marketing cookies, through a consent check in Tag Manager or your CMP. This is how I usually set it up.
  • Loading the pixel with fbq('consent', 'revoke') before the init on every page, and fbq('consent', 'grant') as soon as the visitor consents. This is how Meta itself describes it.

I always test twice: once accepting and once declining. Then I check four places:

  • Tag Assistant: the Consent tab shows the default status at the first Consent event and the status after your choice at the last one. If the tab is empty, Consent Mode isn't running.
  • The browser: after declining, there should be no new Google Analytics or Google Ads cookies, such as _ga or _gcl_au.
  • GA4: under Admin, the consent settings for each data stream show the signals for ads and for behavioral analytics, with a notice if something is missing.
  • Google Ads: for a website conversion, the Diagnostics tab shows whether Consent Mode is implemented and whether modeling is active. That status can take 48 hours to 2 weeks to appear.

A cookie banner that looks good tells you nothing about what Google receives.

The mistakes I come across most often

Consent Mode is part of every tracking check I do, including in a Google Ads account audit. These are the mistakes I come across most often:

  • The default status comes too late, for example because the CMP loads asynchronously. A tag has then already read or written cookies before a choice was known.
  • The Google tags have been given an extra block on ad_storage in Tag Manager. That turns advanced into basic in practice, and leaves Google little to model.
  • Only the old signals: ad_storage and analytics_storage are there, but ad_user_data and ad_personalization are missing. Remarketing and audiences then stop receiving visitors from the EEA.
  • Two cookie banners at once, one from the webshop platform and one from the CMP, so it's unclear which choice the tags follow.
  • A pop-up that covers the cookie banner, or no link to change the choice later.
  • For one webshop, the conversion import from GA4 was the primary conversion in Google Ads. After a new cookie banner, that import almost completely collapsed, while GA4 itself looked healthy. A dedicated Google Ads conversion tag with Consent Mode as the primary conversion fixed it.

I'm Reinier van Duijne, and I work from Haarlem as an independent specialist in advertising and the tracking behind it. Because I also work in the ad accounts, I can see right away what a consent error costs in conversions and audiences.

I start with the current state in Tag Assistant, GA4 and Google Ads. Then I adjust the CMP and Tag Manager, test accepting and declining, and check the Google Ads diagnostics again after two weeks. The cost depends on your CMP, your website platform and the number of tags. You'll get a custom quote.

Want to know how your tracking is doing first? Request the free Performance Quick Scan. I review your account with read-only access and show where conversions and audiences are leaking, including when consent is the cause.

Frequently asked questions

Is Consent Mode v2 mandatory?

In practice, yes, for advertisers with visitors from the EEA. Since March 2024, Google has required you to pass on their consent if you use Google tags for measurement, remarketing or personalized ads. Consent Mode is the standard way to do that through your tags. You ask for consent itself with your cookie banner, and Consent Mode passes the outcome on to Google.

What's the difference between Consent Mode v1 and v2?

Version 2 has two extra signals: ad_user_data for sharing user data for advertising and ad_personalization for personalized ads. Google added them in November 2023. For EEA visitors on v1, Google copies the ad_storage value to ad_user_data. That doesn't happen for ad_personalization, so you need v2 for remarketing in the EEA.

Do I need a certified CMP?

No, according to Google you can also use a CMP that isn't a partner (yet). A certified CMP, such as Cookiebot, Complianz or CookieYes, has been reviewed by Google for its Consent Mode integration. That saves custom code and testing. With another CMP, I check extra carefully that all four signals come through.

Can I set up Consent Mode without Google Tag Manager?

Yes. You can also set the default status and the updates with gtag.js in your site's code, or let your CMP do it. Tag Manager makes it easier to tie other tags, such as the Meta pixel, to consent as well. If your site already runs on Tag Manager, I set it up there.

Why don't I see modeled conversions in Google Ads?

There are three common causes. Google names a modeling threshold of 700 ad clicks over 7 days per domain and country combination. The status in the diagnostics can take 48 hours to 2 weeks to appear. And if your Google tags sit behind a hard consent block in Tag Manager, they don't send pings and there's little to model.

Does Consent Mode also apply to visitors outside the EEA?

That's up to you. With the region setting, you set the default status to denied only for specific countries or regions. A default status without a region applies to all other visitors. Which regions you choose depends on your markets and your privacy policy.

What does it cost to have Consent Mode v2 set up?

That depends on your CMP, your website platform and the number of tags that need to be tied to consent. Many CMPs work with a subscription, with prices that vary by provider. For setup and testing, I put together a custom quote after I've seen what's currently in place.

First see where your return is leaking?

Outsourcing to me means your advertising is handled from A to Z. The free Quick Scan is the first step: I go through your account with read-only access and show you your 3 biggest opportunities, in a report that is yours to keep, even if we do not work together afterwards.

Your dedicated contact: Reinier van Duijne 9+ years in performance marketing. No handover to a junior after the intro call, no changing faces.