How to enable Google Consent Mode V2? - Part 2

Our Part 1 article focused on what Google's Consent Mode V2 is and why you need it. Part 2 focuses on the How-To aspects of enabling Google's Consent Mode V2

Google's Consent Mode V2 is one solution that acts upon users' consent and changes how data is collected. It is designed to consider user choices regarding cookies and data collection and, therefore, keeps Google-tagged websites compliant with major privacy regulations like the General Data Protection Regulation (GDPR) and the ePrivacy Directive. 

Consent Mode V2 will enable Google tags to automatically adjust their behaviour based on whether users consent to processing data concerning ads and analytics.

How to enable Google Consent Mode V2

Remember to check your Google Tag Manager setup to ensure it is compatible with your consent management platform. 

Here's a step-by-step guide on how to enable Consent Mode V2:

CMP Compatibility: First, check if the consent management platform is compatible with Google's Consent Mode V2. 

The CMP should support sending consent signals up to the Google Tag Manager.

• Update Google Tags: Inside your Google Tag Manager account, look for tags connected to Google Analytics, Google Ads, or Floodlight. You will need to change the settings of those tags by adding the feature Consent Mode V2. 
• This will allow Google's tags to serve, dynamically amending their respective behaviours based on the choices being made by your users in giving consent.
• Set Default States: By default, set the consent status of new users to a certain status (e.g., 'denied' until the user makes a choice). This will help to comply with the privacy by default.
• Integrate CMP with GTM: Link your CMP to Google Tag Manager. Your CMP will collect user consent preferences and will directly communicate the same to GTM. GTM, in turn, will apply the collected preferences to the Google tags by modifying them.
• Testing and Verification: Employ Google Tag Assistant and developer tools to actually see whether everything is working fine, and if consent preferences are considered accordingly.

What are Basic and Advanced modes?

Google Consent Mode V2 enables two ways to handle user consent: Basic and Advanced modes. Both of them concern the issue of what extent of data collection and processing can be enabled based on users' choices.

• Basic Mode: In Basic Mode, it is supposed to collect data only on users' set preferences. It means when users do not give consent to analytics or advertising cookies, no extra modelling or recovery should be done. The data collection is minimal, generally bound to the basic functionality of the website.
• Advanced Mode: Advanced Mode introduces conversion modelling to make up for lost data due to user opt-outs. This mode deploys machine learning algorithms to estimate the behaviour of users and conversions that provide complete insights, with consideration for privacy choices.

Advanced Mode: Conversion Modelling

Advanced Mode Conversion Modeling is a feature essentially helpful to learn about the actions of users whenever there is limited consent. Google will use data from aggregated and anonymised users of those who consent against modelling conversions in non-consenting users. This fills data gaps without compromising on privacy.

For instance, even if a user interacts with an ad and does not consent to cookies, Google can still estimate whether the interaction resulted in a conversion through analysis of patterns and behaviours of other users who have provided consent. You thereby get more complete conversion data that may be critical for properly measuring the effectiveness of your ad campaigns.

Basic Mode versus Advanced Mode Comparison

• Basic Mode: Only data explicitly allowed by the user is gathered. It's highly straightforward, has the flow act in concert with consent provided from the user, without extra modelling or additional analyses of data. This mode fits businesses that need simplicity and the assurance of strong privacy conformance.
• Advanced Mode: Employs advanced machine learning techniques to fill the missing data gaps left by opted-out users. This mode will fit an enterprise that seeks a balance between privacy and performance insight, as it provides them with more precise conversion tracking and performance measurement.

Do I also need a Server-Side Tag Manager?

While not a requirement, a Server-Side Tag Manager is highly advantageous in the usage of Consent Mode V2. A Server-Side Tag Manager enables the transfer of large volumes of your tag management into your server, hence giving more control over how data collection, processing, and sharing are done. 

This comes in handy with privacy and security concerns where you filter out or manage the data before they reach third-party services.

Using a Server-Side Tag Manager can also help with consent management in that it gives you more control over the data flow and how to ensure all tags are taking user-preference parameters into consideration. It adds another layer of privacy protection-a welcome aspect for GDPR compliance.

The Consent Mode Parameters

Google Consent Mode V2 uses a number of parameters for the purpose of deciding what data and how to collect depending on user consent. 

The key parameters include: ad_storage: This is a parameter that controls the storing related to advertising cookies. In case a user does not consent to ad-related data, this parameter is set to 'denied', and advertising cookies are not stored.

• ad_personalization: Regulates the use of cookies and data that personalise ads for users. When consent is refused, personalised ads are not shown, and only generic, non-targeted ads are displayed.
• ad_user_data: Manages the storage and usage of user data specifically for advertising purposes. If a user declines consent, no user-specific data is used for ads, limiting tracking and targeting capabilities.
• analytics_storage: Regulates the storage of analytic cookies. If a user refuses to consent, analytic cookies are blocked, collecting only essential data such as anonymised page views.
• functionality_storage: Regulates cookies for non-ad and non-analytics purposes that are used for the functionality of the site. This parameter helps in keeping a record of features that enhance user experience.
• security_storage: This refers to security that helps in maintaining the integrity of the website operation.

Applying these parameters, it ensures that data collection in websites remains in line with the preference of users but at least at some levels, functionality and insights into data can be preserved. 

Implementation of Default Status Imposing a default status is crucial to privacy compliance when explicit consent has neither been given nor refused. 

You can then set the default so that Consent Mode V2 either blocks all non-essential cookies or allows minimal data collection, which is necessary for basic website functionality in case of no explicit consent from the user. 

This means that the best practice will be to set a conservative default status-for example, disallowing all data collections except those needed by the website for functionality. 

This is in line with the principle of 'privacy by default', indeed a precept under many privacy regulations, including GDPR. This will make sure that no personal data is collected until active beginning of consent has been given by the user.

Activating Consent Mode V2 with a CMP (Consent Management Platform)

To activate Consent Mode V2, you must integrate it with your consent management platform (CMP). The CMP is responsible for gathering consent choices from users and passing those signals to Google Tag Manager. Once integrated:

• User Interaction: When a user visits your site, the CMP will prompt them to set their consent preferences.
• Data Sharing: The CMP then sends these preferences to Google Tag Manager.
• Tag Adjustment: Google tags will adjust their behaviour based on the preferences, only collecting data allowed by the user.

This process ensures that your website remains compliant with privacy laws while allowing Google services to gather meaningful insights based on the consent provided.

How to check if Consent Mode V2 is working properly

After implementing Consent Mode V2, you need to verify that it works correctly. Here are some methods you can use:

• Google Tag Assistant: This is a Chrome extension that helps you check if Google tags are firing correctly. Use Tag Assistant to see if the tags adjust based on user consent choices. The extension will show you which tags are active and whether they comply with consent settings.
• Browser Developer Tools: You can use the developer tools in your web browser to check network requests and ensure that the correct consent parameters (e.g., ad_user_date, analytics_storage) are being sent. Look for requests made by Google tags and verify that they align with the consent preferences users set.
• CMP Debugging Tools: Many consent management platforms offer debugging tools that allow you to check how consent signals are being passed to third-party services, including Google Tag Manager. Use these tools to confirm that consent preferences are properly captured and transmitted.

By using these verification methods, you can ensure that Consent Mode V2 is functioning correctly, providing you with valuable data insights while respecting user privacy choices.

If you're looking to streamline your data analytics implementation while ensuring compliance with data privacy regulations, Arekibo can help. Our team offers expert guidance to optimise your analytics setup, manage cookie consent effectively, and ensure your data practices align with user preferences. With tailored solutions for ad personalisation, user data management, and secure data storage, Arekibo helps you maximise insights from your data responsibly.

Contact us today to transform your data analytics with privacy and performance in mind. Let’s create a data strategy that works for you and respects your users.