{"id":9096,"date":"2024-01-08T09:20:33","date_gmt":"2024-01-08T08:20:33","guid":{"rendered":"https:\/\/www.myagileprivacy.com\/supporting-consent-mode-v2-what-it-is-and-how-to-implement-it-gdpr-compliant-with-my-agile-privacy\/"},"modified":"2026-03-31T21:18:03","modified_gmt":"2026-03-31T19:18:03","slug":"supporting-consent-mode-v2-what-it-is-and-how-to-implement-it-gdpr-compliant-with-my-agile-privacy","status":"publish","type":"post","link":"https:\/\/www.myagileprivacy.com\/en\/supporting-consent-mode-v2-what-it-is-and-how-to-implement-it-gdpr-compliant-with-my-agile-privacy\/","title":{"rendered":"Supporting Consent Mode v2 - what it is and how to implement it GDPR compliant with My Agile Privacy\u00ae"},"content":{"rendered":"

What is Consent Mode v2 and Why is it Required?<\/h2>\n

Google\u2019s Consent Mode v2 represents a major step forward in digital privacy and user data governance. Introduced in late 2023 and mandatory from March 2024, it\u2019s both a technological evolution and a direct response to new regulatory mandates from the European Union.
\nThe move to Consent Mode v2, required by the end of March 2024, comes largely from laws like the Digital Markets Act (DMA). This legislation compels Google to enhance protections for user consent, ensuring transparent and lawful data collection in line with evolving privacy standards.
\nImportantly, Consent Mode itself doesn\u2019t directly satisfy a regulatory obligation for website owners\u2014but if you rely on Google\u2019s advertising or analytics, not adopting Consent Mode v2 can mean falling behind in privacy compliance and losing effectiveness in your campaigns. That\u2019s why it\u2019s now essential for anyone using Google Ads or Google AdSense.<\/p>\n

How Does Consent Mode v2 Work?<\/h2>\n

Consent Mode v2 brings more precise, compliant consent management than its predecessor, based on four main parameters (two more than before), each controlling how different types of user data are collected and used:<\/p>\n

    \n
  1. analytics_storage<\/em><\/strong>: Manages consent for analytics data collection\u2014letting you determine whether user interaction data is used for traffic and behavior analytics.<\/li>\n
  2. ad_storage<\/em><\/strong>: Controls consent for ad data storage\u2014crucial for using user info for ad targeting.<\/li>\n
  3. ad_user_data<\/em><\/strong>: Sets whether user data can be sent to Google for advertising, managing the granularity of data shared for ad personalization.<\/li>\n
  4. ad_personalization<\/em><\/strong>: Regulates whether users get personalized ads (like remarketing), so users can opt in or out of interest-based advertising.<\/li>\n<\/ol>\n

    Unlike other consent management platforms that use broad cookie categories, My Agile Privacy\u00ae<\/sup> offers granular consent for each parameter, meeting both regulatory requirements and giving users clear, precise information about cookies and their purposes.
    \nBy enabling users to give targeted consent, My Agile Privacy\u00ae<\/sup> increases transparency and improves compliance in your data collection.<\/p>\n

    Basic vs. Advanced Versions:<\/h3>\n

    Consent Mode v2 can be implemented in two ways: basic and advanced.
    \nThe basic version covers the essentials, focusing on main consent parameters. The advanced version adds extra options and customization, supporting refined consent control and more detailed data sharing with Google.
    \nMy Agile Privacy\u00ae<\/sup> supports both approaches. If your Google Analytics cookie is subject to consent and blocks data before consent, you\u2019ll get the basic version. If the cookie is always active, My Agile Privacy\u00ae<\/sup> enables the advanced version, sending default values until the user makes a choice. Details are in later sections of this article.<\/p>\n

    How to Enable Consent Mode with My Agile Privacy\u00ae<\/sup><\/h2>\n

    Enabling Consent Mode v2 with My Agile Privacy\u00ae<\/sup> is simple\u2014but you must have Google Analytics cookies installed and detected on your site.
    \nYou can set this up either \u201cnatively\u201d or via Google Tag Manager (GTM) with a tag template.
    \nIn your WordPress admin, go to My Agile Privacy\u00ae<\/sup> > \u201cConsent\u201d tab.
    \nYou\u2019ll find a Consent Mode v2 section for deployment options: native with GA4 or via GTM.<\/p>\n

    Native Consent Mode v2 (with Google Analytics)<\/h3>\n

    Choose \u201cvia My Agile Privacy\u00ae<\/sup>\u201d from the \"implementation type\" menu.
    \n\"\"
    \nYou\u2019ll see the four parameters listed, each with consent and data options. The default for all four is \"denied.\"
    \nUnless your DPO or consultant advises otherwise, you don\u2019t need to change the defaults.<\/p>\n

    Consent Mode v2 via Google Tag Manager<\/h3>\n

    Choose \"Google Tag Manager\" as your implementation type and save.
    \nConfigure everything else in your GTM panel:
    \n1. Add the My Agile Privacy\u00ae<\/sup> tag from the template gallery.<\/strong>
    \n\"New Tag\" \u2192 Tag configuration \u2192 Discover more in Community Template Gallery.
    \n\"\"
    \nSearch and select \"My Agile Privacy\u00ae<\/sup> CMP.\"
    \n2. Configure the Tag<\/strong>
    \nAdjust parameters as needed; use \u201cURL passthrough\u201d if you want consent data to persist through navigation.
    \nSet parameter defaults (\u201cdenied\u201d is recommended for compliance) via \u201cAdd region\u201d\u2014leave it blank for global settings.
    \n\"\"
    \n\"\"
    \n3. Add a Trigger<\/strong>
    \nSet the trigger to \"Consent initialization - All Pages\" so the tag runs globally.
    \n\"\"
    \nRemember to save. Setup is now complete in both native and GTM implementations.<\/p>\n

    Using My Agile Pixel<\/h2>\n

    If you use My Agile Pixel<\/a>, you\u2019re sending tracking data server-side\u2014bypassing blockers and giving you detailed control over which parameters go to Google\u2019s servers.
    \nJust upgrade My Agile Pixel to version 3.0.0 and enable advanced GA features in your Analytics panel. You\u2019ll then be able to transmit server-side data for both Google Analytics and conversion tracking, all GDPR-compliant with Consent Mode v2.<\/p>\n

    How to Test Your Consent Mode Implementation<\/h2>\n

    After enabling Consent Mode v2, verify it works with Google Chrome extensions like GA Debug and Tag Assistant.
    \nWhen the GA cookie is detected, you\u2019ll be able to use the \u201cCustomize\u201d button on your cookie banner to see all four consent parameters.
    \n\"\"
    \nThe Google Analytics cookie will now display consent options for each parameter described above.<\/p>\n

    Extra consents may show up within the Tag Manager or My Agile Pixel\u2014Google Analytics cookie, depending on your setup.<\/p>\n

    Consent Mode V2 Inspector (recommended)<\/h3>\n

    The fastest and most complete way to verify Consent Mode is Consent Mode V2 Inspector<\/a><\/strong>, the free Google Chrome extension developed by My Agile Privacy\u00ae.<\/p>\n

    \"\"<\/a><\/p>\n

    Unlike other tools, it monitors three systems simultaneously in real time within a single interface:
    \nGoogle Consent Mode v2<\/strong> (with all 4 parameters: analytics_storage<\/code>, ad_storage<\/code>, ad_user_data<\/code>, ad_personalization<\/code>), Microsoft UET<\/strong> and Microsoft Clarity<\/strong>.
    \nSignals update in real time with every change the user makes to their preferences in the cookie banner.<\/p>\n

    The extension collects no data whatsoever: all monitoring happens locally in the browser.<\/p>\n

    Install Consent Mode V2 Inspector from the Chrome Web Store \u2192<\/a><\/strong><\/p>\n

    Chrome Extension - GA Debug<\/h3>\n

    GA Debug reveals detailed GA activity and consent status. Use your browser dev console (CTRL+J<\/em> Windows, COMMAND+OPTION+J<\/em> Mac) to view info logged by GA Debug. If things are configured correctly, you\u2019ll see consent values for all parameters.
    \n\"\"
    \nConsent updates appear in the console as you give or withdraw consent.
    \n\"\"
    \n\"\"<\/p>\n

    Chrome Extension - Tag Assistant<\/h3>\n

    Tag Assistant checks Google tags, including Consent Mode v2. Go to https:\/\/tagassistant.google.com\/<\/a>, enter your domain, and verify tag events and consent details.
    \n\"\"
    \nReview the \u201cConsent\u201d tab of recent events to confirm parameter status.
    \n\"\"
    \nConsent events update as you make new choices.
    \n\"\"
    \n\"\"<\/p>\n

    GA4 Debug View (for My Agile Pixel)<\/h3>\n

    If you use My Agile Pixel, Google Analytics 4 Debug View lets you check proper operation. Debug signals show up as you grant or withdraw consent, with individual parameter changes highlighted.
    \n\"\"
    \nSee     Google\u2019s official Consent Mode v2 documentation<\/a> for more technical details.<\/p>\n

    Need Help?<\/h3>\n

    If you have questions or issues implementing Consent Mode v2 with My Agile Privacy\u00ae<\/sup>, contact our support<\/a>.
    \nOur experts are ready to assist you throughout setup, troubleshooting, and beyond.
    \nRemember, adopting Consent Mode v2 isn\u2019t just about compliance\u2014it\u2019s an opportunity to boost transparency and user trust. My Agile Privacy\u00ae<\/sup> is your partner in this new privacy landscape.<\/p>\n

    What Should You Do Next?<\/h2>\n

    Don\u2019t wait\u2014adapt your site for Google Consent Mode v2 now with My Agile Privacy\u00ae<\/sup><\/a>. The enforcement deadline is March 2024, but it\u2019s wise to act early.
    \nSwitching now ensures GDPR compliance and lets you manage user preferences with precision.
    \nNeed to adapt your site for Microsoft Consent Mode? Read our     guide to Microsoft Universal Event Tracking<\/a>.<\/em><\/p>\n

    Do you want to check in real time the configuration of Google Consent Mode v2, Microsoft, and Clarity Consent Mode? Install the free extension for Google Chrome:
    \n    Consent Mode V2 inspector for Google, Clarity and Microsoft by My Agile Privacy\u00ae<\/sup><\/a>.<\/div>\n","protected":false},"excerpt":{"rendered":"

    What is Consent Mode v2 and Why is it Required? Google\u2019s Consent Mode v2 represents a major step forward in digital privacy and user data governance. Introduced in late 2023 and mandatory from March 2024, it\u2019s both a technological evolution and a direct response to new regulatory mandates from the European Union. The move to […]<\/p>\n","protected":false},"author":1,"featured_media":9706,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[82,81,83,76,84],"tags":[],"class_list":["post-9096","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ecommerce-websites","category-news-websites","category-showcase-websites","category-software-updates","category-web-agency"],"acf":{"visibilita_box_autore":false,"autore_associato":null,"elenco_faq_articolo":[{"domanda":"What is Google's Consent Mode v2 and why was it introduced?","risposta":"Consent Mode v2 is a Google tool for more advanced and granular management of user consent. It was introduced at the end of 2023 and made mandatory from March 2024, primarily in response to the Digital Markets Act (DMA), the European regulation that pushed Google to strengthen consent measures to ensure legality and transparency in data collection."},{"domanda":"What are the 4 parameters that Consent Mode v2 is based on?","risposta":"Consent Mode v2 is based on four parameters: analytics_storage (consent for analytics data collection), ad_storage (consent for the use of data for advertising and targeting purposes), ad_user_data (allows or disallows the sending of user data to Google for advertising) and ad_personalization (governs the enabling of personalised ads and remarketing)."},{"domanda":"Is Consent Mode v2 mandatory for all websites?","risposta":"No, Consent Mode v2 is not a direct requirement for all websites. However, if you use Google Ads or AdSense it is essential for compliance and campaign effectiveness. Without v2 you risk having sparse reports and less effective campaigns."},{"domanda":"What is the difference between the basic and advanced versions of Consent Mode v2?","risposta":"The basic version covers the essentials and focuses on the main consent parameters. The advanced version offers more options and customisation, even more detailed management and a more complete flow of information to Google. If Analytics requires consent to transmit data, the basic version is used; if Analytics is 'always on', the advanced version is used, which transmits default values until the user makes a conscious choice."},{"domanda":"How can Consent Mode v2 be implemented through My Agile Privacy\u00ae?","risposta":"My Agile Privacy\u00ae supports two types of implementation: native or via Google Tag Manager (GTM). For native implementation, select 'via My Agile Privacy\u00ae' from the panel in the 'Consent' section and configure the 4 parameters (default: 'denied'). Via GTM, select 'Google Tag Manager', add the tag from the Community Template Gallery, configure the parameters and add the 'Consent initialization - All Pages' trigger."},{"domanda":"How can you verify that Consent Mode v2 is configured correctly?","risposta":"You can verify it using various tools: the free Chrome extension 'Consent Mode V2 Inspector' developed by My Agile Privacy\u00ae (recommended, monitors Google Consent Mode v2, Microsoft UET and Microsoft Clarity in real time), GA Debug (displays consent details in the console), Tag Assistant (verifies that Google tags are active) or the Debug View in Google Analytics 4 if you use My Agile Pixel."},{"domanda":"What is My Agile Pixel and how does it integrate with Consent Mode v2?","risposta":"My Agile Pixel is a tool that allows data to be sent server-side, bypassing ad blockers and determining which parameters to send to Google. By updating it to version 3.0.0 and enabling the advanced features in the admin, full compliance with both GDPR and Consent Mode 2.0 is achieved. With My Agile Pixel it is also possible to use the GA4 Debug View to see consent changes in real time."}],"url_esterno":""},"_links":{"self":[{"href":"https:\/\/www.myagileprivacy.com\/en\/wp-json\/wp\/v2\/posts\/9096","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.myagileprivacy.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.myagileprivacy.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.myagileprivacy.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.myagileprivacy.com\/en\/wp-json\/wp\/v2\/comments?post=9096"}],"version-history":[{"count":19,"href":"https:\/\/www.myagileprivacy.com\/en\/wp-json\/wp\/v2\/posts\/9096\/revisions"}],"predecessor-version":[{"id":15706,"href":"https:\/\/www.myagileprivacy.com\/en\/wp-json\/wp\/v2\/posts\/9096\/revisions\/15706"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.myagileprivacy.com\/en\/wp-json\/wp\/v2\/media\/9706"}],"wp:attachment":[{"href":"https:\/\/www.myagileprivacy.com\/en\/wp-json\/wp\/v2\/media?parent=9096"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.myagileprivacy.com\/en\/wp-json\/wp\/v2\/categories?post=9096"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.myagileprivacy.com\/en\/wp-json\/wp\/v2\/tags?post=9096"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}