Skip to content
Start free Sign in

Google Consent Mode v2

Every choice reaches Google.

Switch on Consent Mode v2 and Kukie.io sets all 7 consent signals before your Google tags run, then updates them the moment a visitor chooses. Your Google tags need no changes.

Start free (opens in a new tab) Check your Consent Mode

Included on every plan. Last reviewed on .

Google products that read the signals

  • Google Analytics 4
  • Google Ads
  • Google Tag Manager
  • Search Ads 360
  • Display & Video 360

Watch the explainer

How Consent Mode works, signal by signal.

What the seven signals tell your Google tags, the one switch that sets them, and a visitor's choice reaching Google on the same page.

2 minutes 18 seconds, narrated, with captions in the player. The sites and rules in it are examples.

Read the transcript
  1. 0:00 Google Analytics, Google Ads and Tag Manager all need to know one thing. What did this visitor agree to?
  2. 0:07 Google Consent Mode v2 is how they find out. It tells your Google tags whether a visitor has agreed to cookies, through seven consent signals.
  3. 0:16 Since March 2024, Google has asked for it for ad personalisation, remarketing audiences and conversion measurement in the EU.
  4. 0:26 With Kukie.io, it's one switch. Open the Banner Editor, go to Integrations, and turn on Google Consent Mode v2. Your Google tags need no changes.
  5. 0:37 From then on, the banner sets all seven signals to denied, before your Google tags run. Only security storage is granted, and Google waits half a second for an answer.
  6. 0:48 Then the visitor chooses, and the signals update at once, with no page reload.
  7. 0:53 Each cookie category controls its own signals. Allow analytics, and analytics storage is granted. Leave marketing off, and the three ad signals stay denied.
  8. 1:03 Every choice also lands in the data layer as a cookie consent update event, so tags that don't read Consent Mode can wait for it too.
  9. 1:12 Using Google Tag Manager? Paste your container ID, and Kukie.io loads it for you. In basic mode, it waits for consent. In advanced mode, it loads straight away with every signal denied, so Google tags can send cookieless pings.
  10. 1:28 While ads are denied, ad click data is redacted. And one switch passes ad clicks through your links instead of a cookie, so conversions can still be measured.
  11. 1:37 Google's banner text is one click away, in eight languages. It names ads personalisation and links to how Google uses data.
  12. 1:46 Then check your setup. Debug mode shows in the console that the defaults ran first. And the Consent Mode check in Compliance Tools gives you a score, signal by signal.
  13. 1:57 On WordPress, the free Kukie.io plugin has its own Google Consent Mode v2 tab. Switch it on, save, and you're done.
  14. 2:06 Google Consent Mode v2 is included on every plan, including Free. Every choice reaches Google.

What it is

What Consent Mode v2 does.

Google Consent Mode v2 tells Google services whether a visitor has agreed to cookies. It controls how Google Analytics, Google Ads and other Google tags behave for that visitor.

Since March 2024, Google has asked for Consent Mode v2 for ad personalisation, remarketing audiences and conversion measurement in the EU.

Without Consent Mode
  • No remarketing audiences from EEA visitors
  • Less conversion data in Google Ads
  • Gaps in GA4 reports for EU visitors
With Consent Mode v2
  • Conversion modelling for visitors who decline
  • Cookieless pings instead of no data at all
  • Consent signals in every region you set

Signal mapping

Each choice, signal by signal.

Each Kukie.io cookie category controls its own Google signals, so you never map them by hand. Choose a moment to see what Google receives.

wait_for_update is 500 ms, which gives the banner time to appear before Google's tags run.

Marketing
ad_storage
denied
ad_user_data
denied
ad_personalization
denied
Analytics
analytics_storage
denied
Functional
functionality_storage
denied
personalization_storage
denied
Essential
security_storage
granted

Set on page load, before Google's tags run. Google tags set no advertising or analytics cookies in this state, though they can send cookieless pings.

Two ways to run it

Basic or advanced Consent Mode.

The difference is what happens before a visitor chooses. Kukie.io supports both.

Basic mode

Google tags wait for consent.

  1. The page loadsNothing from Google runs yet.
  2. The visitor accepts analytics or marketingKukie.io sends the update.
  3. Your Tag Manager container loadsGoogle tags start with the visitor's consent.
Sent before consent
None
Conversion modelling
General modelling only

With Kukie.io: Add your container ID in the Banner Editor. Kukie.io loads it after the visitor accepts.

Advanced mode

Google tags run without cookies.

  1. The page loadsGoogle tags start with every signal denied.
  2. Cookieless pingsGoogle uses them for conversion modelling.
  3. The visitor acceptsThe signals update and tags use cookies.
Sent before consent
Cookieless pings
Conversion modelling
Modelling for your own account

With Kukie.io: Turn on Load the container before consent, or keep Google's tags in your page.

Other tags in the same container. A Meta Pixel or any other tag that is not a Google tag ignores Consent Mode. Fire it on the cookie_consent_update event Kukie.io sends, so it waits for a choice too.

Learn more about basic and advanced mode

Built in

The details Google looks for.

What Kukie.io adds around the 7 signals. Most of it needs no setup at all.

Google's banner requirements

Banner text for Google, in one click

Apply text that names ads personalisation and links to Google's page on how it uses data. It also turns on Reject all and Customise.

  • English
  • German
  • French
  • Spanish
  • Italian
  • Dutch
  • Polish
  • Portuguese
Privacy by default

Ad click data redacted

While ad_storage is denied, ads_data_redaction removes ad click identifiers from Google's requests. It is always on, and changes nothing once a visitor accepts marketing.

Optional switch

Ad clicks passed through links

Until a visitor accepts marketing, the ad click identifier travels in your links instead of a cookie, so a conversion can still be measured.

For your own triggers

A dataLayer event

Every choice pushes cookie_consent_update, for tags that do not read Consent Mode.

Debug mode

A report in the console

Add ?kukie_debug=1 to a page to see the Google tags found and whether the defaults ran first.

Check any page, or every site you run

The free Consent Mode checker reports the defaults, their timing and the 7 signals for any page. In your dashboard, Compliance Tools runs the same check for each site and keeps the history.

Check your Consent Mode

Running Amazon Ads too? Kukie.io also supports the Amazon Consent Signal.

Check it

See the signals on your own site.

The order matters: the defaults have to run before your first Google tag. Three ways to see that they do.

  1. Consent Mode checker

    A free check of any page. It loads the page and reports the defaults, their timing and the 7 signals.

    Check your Consent Mode

  2. Compliance Tools

    The same check for each of your sites, in your dashboard, with the history kept and a link to the setting that fixes each finding.

  3. Debug mode

    Add ?kukie_debug=1 to any page and the browser console shows the Google tags it found, whether the defaults ran first and the current state.

    Learn more about debug mode

Setup

Set it up in three steps.

No tag changes, no new Tag Manager triggers and no developer.

Documentation

Guides to setting it up.

Step-by-step guides to Google Consent Mode v2 with Kukie.io, in the Help Centre.

Support for Consent Mode questions

Running into a Consent Mode v2 setup, timing or measurement problem? Email our Google client support first, before you contact Google. We answer within 1 business day.

google-support@kukie.io

Announcement

Partner Announcement Featured article

Kukie.io Joins Google's CMP Partner Program with Consent Mode v2 Support

Read about how Kukie integrates with Google's Consent Mode v2 framework, the technical work behind our Developer ID, and what this partnership means for sites running Google Analytics and Google Ads.

Read the announcement

Consent Mode guides

Articles on Google Consent Mode v2, Tag Manager, GA4 and consent-aware tagging.

Check your Consent Mode
More Consent Mode guides

Questions about Consent Mode

What is Google Consent Mode v2?
Google Consent Mode v2 is a framework that lets your website tell Google services, such as Analytics, Ads and Tag Manager, what each visitor chose. When a visitor accepts or rejects cookies, Consent Mode updates the consent state straight away, so Google tags either run fully or fall back to cookieless pings, which Google uses for conversion modelling. Since March 2024, Google has asked for Consent Mode v2 for ad personalisation and remarketing in the EU.
Do I need Consent Mode if I use Google Analytics?
If you use Google Analytics 4 and have visitors in the EU, the EEA or the UK, Google's platform policies ask for Consent Mode v2 before features such as audience building, remarketing and conversion modelling use that traffic. Without it, those Google Ads features cannot use EEA traffic, and GA4 may not set cookies for EU visitors when the EU consent setting is on. Consent Mode also enables advanced conversion modelling, which recovers some of the conversion data lost when visitors decline cookies.
Does Kukie.io support all 7 consent parameters?
Yes. Kukie.io sets all 7 Google Consent Mode v2 parameters: analytics_storage, ad_storage, ad_user_data, ad_personalization, functionality_storage, personalization_storage and security_storage. Each one follows a Kukie.io cookie category, so each choice becomes the matching signals.
What happens if a visitor rejects cookies?
Kukie.io sets every consent parameter except security_storage to denied. Google tags then run without cookies and send cookieless pings instead of setting tracking cookies. Google uses these pings for conversion modelling, which gives you estimated conversion data.
Can Kukie.io load my Tag Manager container before consent?
Yes. Turn on Load the container before consent under Google Tag Manager in the Banner Editor. The container then loads on every page with all signals denied, which is advanced Consent Mode. Tags in the container that are not Google tags ignore Consent Mode, so fire them on the cookie_consent_update event or add consent checks to them.
What does Pass ad clicks through links do?
It sets url_passthrough. Until a visitor accepts marketing cookies, Google tags keep the ad click identifier in the links the visitor follows on your site instead of in a cookie, so a conversion can still be measured. The links show longer addresses, which is why the switch is off until you turn it on.
Do I need a GTM container to use Consent Mode?
No. Consent Mode works with Google Tag Manager and with Google tags added directly (gtag.js). If you use Tag Manager, Kukie.io can load your container for you. If you use gtag.js directly, the Consent Mode signals reach it with no extra setup.
Is Kukie.io a certified Google CMP Partner?
Kukie.io integrates with Google Consent Mode v2 using Developer ID dOTA0OT, which identifies Kukie as the consent management platform in Google's ecosystem. This means Google services recognise Kukie as the source of consent signals on your site.

Send Google your visitors' choices.

Switch on Consent Mode v2 in a few minutes, with no tag changes and no developer. It is included on every plan, the Free plan too.

Start free (opens in a new tab) Read the guide

Disclaimer

Kukie.io provides tools to collect and record consent. It is not legal advice, and using it does not by itself make a website compliant with any law.

Listed on

Kukie.io on Trustpilot (opens in a new tab) Kukie.io on G2 (opens in a new tab) Kukie.io on SaaSHub (opens in a new tab) Kukie.io on AlternativeTo (opens in a new tab)