How to check if Google Consent Mode v2 is activated?

Google Consent Mode includes API to control the tag of cookie storage based on user consent choices. It allows to collect website analytics and use all other Google products while maintaining necessary data privacy standards.

Starting from March 2024, Google switched to Google Consent Mode version 2 to comply with the GDPR and other privacy laws. There are two consent mode implementations: Basic and Advanced. Under the basic consent mode implementation, no information from users is collected at all, not even consent status. Under the advanced implementation, Google tags are loaded before users are presented with the cookie consent banner, and Google collects cookieless data that lack personal identifiers.

If you want to continue using Google Ads for your advertising in the EEA markets, you need to use a cookie banner integrated with Google Consent Mode v2 by March 2024.

The easiest way to implement Google Consent Mode on your website is by using a CookieScript Google Tag Manager (GTM) Tag template.

1. First, create your GTM account and a website container in GTM, and install the GTM container to your website, where you could add your tags. Read the guide on how to create a GTM account and install the GTM container.

2. Second, install CookieScript. You can install the CookieScript using GTM Tag Template or as a Custom HTML Tag. Read the guide on how to install CookieScript with GTM.

3. Third, implement Google Consent Mode v2 with a CookieScript GTM Tag template by including APIs to control tag cookie storage based on user consent choices without disabling Google services. Read the guide on how to implement Google Consent Mode.

After you implemented Google Consent Mode v2, follow these steps to check if Google Consent Mode v2 is activated (and if Advanced consent mode is implemented) :

1. Check (at your CookieScript settings) if Google Consent Mode 2 is enabled. Google Consent Mode is an optional feature and should be enabled in CookieScript settings. Go to your CookieScript account > Banner settings > Behavior tab > Frameworks > Google Consent Mode v2. The checkbox must be checked.

2. Check (at your GTM account) if the cookie banner is activated.

3. Re-save your banner to make sure your banner supports Consent Mode validator (code updates were released on 2024-07-31).

4. Validate GTM installation. Go to your CookieScript dashboard > Settings > Google Consent Mode, check ENABLE GOOGLE CONSENT MODE V2, and press the Validate GTM installation tab. It checks if you use the last version of the GTM template and the GTM is installed correctly. If the GTM installation is not correct, make changes according to the list below, resave your cookie banner, and validate the GTM installation again.
   

5. Check (at your GTM account) if the trigger is set correctly. The trigger must be Consent Initialization on all pages.

6. Press the shield (at your GTM account) to check if all settings are set in the right way. The shield should be turned on. In the Tag Manager, click Admin > Container Settings. Under Additional Settings, select Enable consent overview. Consent overview is the above-mentioned shield.

7. Check (at your GTM account) if the selected categories of cookies on the GTM preview mode window correspond to your website. Read the guide on how to use a GTM preview mode.
   If some category of cookies is not present on the GTM preview mode window, create an arbitrary cookie with that category, otherwise Google Consent Mode will not work properly.

8. Check (at your GTM account) if you are using Advanced or Basic Google consent mode v2.

See the checklist for the correct implementation of Google Ads and Google Consent Mode v2:

1. Check, if Google Consent Mode is enabled in settings.
   See the guide about how to enable Google Consent Mode.

2. Press the Validate GTM installation tab.

3. CookieScript is installed in GTM using the latest template from gallery.
   See the guide about how to update the GTM template.

4. CookieScript trigger is set to Consent Initialization (AND no other tags in that trigger)

5. GA trigger is set to Initialization

6. Clear browser Cache

7. Use preview mode to see how it works.