What Google CMP Partner Status Means for Your Website
Kukie.io has been approved as a Google CMP Partner with Developer ID dOTA0OT. This ID is embedded directly in the Kukie banner script, telling Google that a certified consent management platform is handling visitor consent on your site.
Google introduced its CMP Partner Programme to certify platforms that meet specific technical requirements for consent signal transmission, IAB TCF compliance, and audit trail capability. Since January 2024, using a Google-certified CMP has been mandatory for businesses serving ads through Google advertising platforms (AdSense, Ad Manager, AdMob) in the EU, EEA, and UK.
For your site, this means consent choices made through your Kukie banner are passed directly to Google tags without any extra configuration.
How Google Consent Mode v2 Works
Google Consent Mode v2 is a protocol that communicates visitor consent choices to Google tags running on your site. It controls how Google services such as GA4, Google Ads, and Google Tag Manager behave before and after a visitor interacts with your cookie banner.
The mechanism relies on two commands. First, a consent default fires before any Google tags load. This sets every consent parameter to denied, ensuring no cookies are dropped and no data is collected until the visitor makes a choice. Second, a consent update fires the moment a visitor grants or denies consent through the banner, adjusting each parameter accordingly.
Google originally shipped Consent Mode with two parameters. Version 2, released in November 2023, added ad_user_data and ad_personalization as mandatory signals. Without these, Google Ads and GA4 stopped processing new EEA user data after the March 2024 enforcement deadline.
All Seven Consent Parameters Supported
Kukie maps your cookie categories to all seven Google Consent Mode parameters. The table below shows each parameter and its purpose.
| Parameter | Controls | Introduced |
|---|---|---|
ad_storage | Cookies used for advertising (e.g. _gcl_au, _gac) | v1 |
analytics_storage | Cookies used for analytics (e.g. _ga, _gid) | v1 |
ad_user_data | Whether user data can be sent to Google for advertising | v2 |
ad_personalization | Whether data can be used for remarketing and personalised ads | v2 |
functionality_storage | Storage for site functionality (language preferences, UI settings) | v1 |
personalization_storage | Storage for content personalisation (video recommendations) | v1 |
security_storage | Security-related storage (authentication, fraud prevention) | v1 |
The two v2 parameters - ad_user_data and ad_personalization - are what Google checks to comply with its EU User Consent Policy. If your CMP does not send these signals, GA4 and Google Ads will not process data for new EEA visitors.
GTM Integration and Consent Leak Prevention
A common compliance gap occurs when Google Tag Manager loads and fires tags before a visitor has made a consent choice. Even with Consent Mode defaults set to denied, some custom GTM configurations can leak data if the container initialises too early.
Kukie addresses this by optionally injecting the GTM container only after the consent default has been set. The sequence works like this: Kukie script loads, consent defaults fire with all parameters set to denied, GTM container loads, and then tags respect the current consent state. When a visitor grants consent, the consent update command fires and GTM tags adjust in real time.
This approach ensures zero consent leaks regardless of how tags are configured inside your GTM container.
Region-Aware Consent Defaults
Privacy regulations differ by jurisdiction. The GDPR requires opt-in consent before setting non-essential cookies, while the CCPA allows an opt-out model where data collection begins immediately but visitors can object.
Kukie uses geo-detection to automatically apply the correct consent model based on visitor location. For EU and UK visitors, all consent parameters default to denied (opt-in). For US visitors, parameters default to granted (opt-out), with a clear option to withdraw consent. Other regions can be configured individually through the dashboard.
These region-specific defaults are passed to Google Consent Mode automatically, so your conversion modelling and measurement stay accurate across different regulatory environments.
Advanced Consent Mode and Cookieless Pings
Google distinguishes between Basic and Advanced Consent Mode. Basic mode blocks all Google tags entirely until consent is granted - no data flows to Google whatsoever. Advanced mode allows Google tags to load in a restricted, cookieless state even when consent is denied.
In Advanced mode, Google tags send small cookieless pings that contain no personal data and set no cookies. These anonymous signals feed Google's machine learning models, enabling more accurate conversion modelling and behavioural modelling in GA4. The result is better data quality in your reports even when a significant portion of visitors decline cookies.
Kukie supports both modes. You choose which approach fits your compliance posture in the Banner Editor under Integrations.
No Code Changes for Existing Users
If you already have Kukie installed on your site, enabling Google Consent Mode v2 requires one step: toggle the GCM v2 switch in the Banner Editor under Integrations. The Developer ID dOTA0OT is already embedded in your banner script, identifying Kukie as the certified CMP to Google.
There is nothing to add to your site's HTML or tag configuration. The consent default and update commands are handled entirely by the Kukie script. Full setup instructions are in the Consent Mode v2 documentation.
To verify that Consent Mode is working correctly on your site, use the free Consent Mode Checker tool. It inspects your page and confirms whether consent defaults are firing before Google tags load.
Why This Matters for Compliance
Data protection authorities across Europe have intensified enforcement around cookie consent and Google services. In September 2025, CNIL fined Google EUR 325 million for dropping cookies without valid consent during account creation and displaying ads without consent between Gmail messages. CNIL found that refusing cookies for personalised advertising was more difficult than accepting them - a textbook dark pattern under Article 5(3) of the ePrivacy Directive.
Multiple DPAs - including those in Austria, France, Italy, Norway, and Sweden - have separately ruled that using Google Analytics without proper consent safeguards violates GDPR. Running a certified CMP with properly configured Consent Mode signals is a practical step toward meeting these regulatory expectations.
The Kukie banner handles the technical side: consent defaults fire before any tags, visitor choices are recorded in an audit-ready consent log, and signals are transmitted to Google in the format its services expect.
Frequently Asked Questions
Do I need Google Consent Mode v2 if I use Google Analytics or Google Ads?
Yes. Since March 2024, Google requires Consent Mode v2 for websites using Google measurement and advertising services with EEA and UK visitors. Without it, Google will not process data for new users from these regions.
What is the difference between Basic and Advanced Consent Mode?
Basic Consent Mode blocks all Google tags until consent is granted. Advanced Consent Mode allows tags to load in a restricted state, sending cookieless pings (no personal data) that improve conversion modelling accuracy. Both are supported by Kukie.
How do I enable Google Consent Mode v2 in Kukie?
Open the Banner Editor, go to Integrations, and toggle the GCM v2 switch. No code changes are needed on your website. The Developer ID is already embedded in your banner script.
What is a Google CMP Partner Developer ID?
A Developer ID is a unique identifier assigned to certified CMPs. Kukie's ID is dOTA0OT. It tells Google services that consent signals on your site come from a verified consent management platform.
Does Kukie handle consent differently for EU and US visitors?
Yes. Kukie uses geo-detection to apply opt-in consent defaults (all denied) for EU and UK visitors under GDPR, and opt-out defaults (all granted with withdrawal option) for US visitors under CCPA. These region rules are passed to Google Consent Mode automatically.
How can I verify that Consent Mode is working on my site?
Use the free Consent Mode Checker at kukie.io/consent-mode-checker. It scans your page and confirms whether consent defaults fire before Google tags load and whether all required parameters are present.
Take Control of Your Cookie Compliance
If your site runs Google Analytics, Google Ads, or Google Tag Manager, Consent Mode v2 is no longer optional for EEA and UK traffic. Kukie handles the consent signals, region detection, and tag sequencing so you can focus on your site rather than debugging gtag calls.
