All Collections
Google Consent Mode v2
How to verify your Consent Mode v2 implementation
How to verify your Consent Mode v2 implementation

In this article, you will learn how to check if your Google Consent Mode v2 implementation is setup properly

Rebecca avatar
Written by Rebecca
Updated over a week ago


How do I check if my CMv2 implementation is working?

You've completed all the steps in our guide on updating to Consent Mode v2, and you're now wondering how to check if the implementation is working as it should.

Consent Mode V2 - Tag template

If you've done your CMv2 implementation by adding our Consent Mode V2 Tag template from GTM Tag Gallery to your workspace, using the Preview mode is the best way to check if the default and update consent date is correct. This feature can be found in the top-right corner when viewing your tags.


Afterwards, enter your domain name and click "connect."

A new window will appear on the website, and we recommend clearing cookies and cache in this window to ensure you're not getting any cookies from previous browser windows/tabs.

Without interacting with the pop-up banner, go back to the GTM Tag Assistant page, check the Consent event, and look under the Consent Tab:


All the consent types should be set to "denied."

Return to the website, accept all cookies, and return to the GTM Tag Assistant page.

There should now be a new consent event in the left panel and look under the Consent tab:


The consent types should now be allowed under the "on-page update."

You can also view the "tags" tab to see if your tags are firing depending on the accepted categories, but for this, you'll need to have done the GTM Cookie Control SDK implementation.

Google also has a handy guide on how to check if your implementation is working correctly with Tag Assistant.

Consent Mode V2 - Source code

If you're using the Cookie Information WordPress Plugin and have enabled Consent Mode under Settings, the following approach still applies.

If you've implemented the source code, you can check by checking the dataLayer. To do that, please follow these steps:

1. Navigate to the website with the newly added CMv2 implementation.

2. Inspect the page, which can be done with the following short-cuts:

  • Windows – Control + Shift + C.

  • MacOS - Command + Option + C

You can also right-click anywhere on the website and click on "Inspect," which is located at the bottom of the selections.

3. Navigate to the Console tab in the top panel and type "dataLayer"

4. Look through the events and find the one with the default consent state:


This should be the view while the pop-up banner is still showing and without interacting with the banner.

All of the parameters should be set to 'denied'.

After accepting all cookies, type "dataLayer" again in the Console Tab, and it should look like this:

All of the parameters should now be set to 'granted'.

If your dataLayer looks the same as viewed above, your implementation should be set up correctly.


I've implemented it correctly, but my data needs to look better.

After finishing and verifying the implementation is working as it should, you're then experiencing that the data isn't what you expect. This is where it's challenging to provide support and assistance since our solution just updates the consent types/status in the dataLayer for GTM to use for firing tags, depending on the consent choice.

We will gladly help check the implementation according to our documentation, but how the tags behave with the provided data and react to the consent settings differs from our expertise.

Providing insights into the behaviour of Google Analytics when Google Consent Mode has been implemented is a challenging task that requires in-depth knowledge of the Google product. We recommend contacting Google's support channels to ensure the information and support you receive are accurate and up-to-date.

Did this answer your question?