Verify your Google Consent Mode setup by using our Google Consent Mode Checker.
- Log into the Cookiebot CMP Admin
- Select Domains and Aliases
- Select the domain you want to check
- Scroll down to the Google Consent Mode Check section
- Click the Start GCM check button
Consent Mode Check - No errors detected
Consent Mode Check - At risk
The Google Consent Mode Check is a tool that allows you to verify your Google Consent Mode implementation and identify any immediate risks affecting your domain(s). The tool requires approximately 10-15 seconds to finish scanning and will provide you with a report on whether risks have been identified.
Your report will be available for 30 days and you can request a new scan at any time (e.g. if you have made any changes in your Google Consent Mode setup).
The Google Consent Mode Check reviews whether you have any immediate risks from a best-practice perspective. Some risks it identifies may not affect your specific website legally, depending on the laws that apply to your domain's market. Always have your legal team assess whether the risks are relevant for your website.
A "no risk" result from the Google Consent Mode Check does not mean 100% your Google Consent Mode setup is fully compliant. The tool draws conclusions from the browser Data Layer, but can't assess the entire backend of your Google Consent Mode or Google Tag Manager setup.
The Google Consent Mode Check does not assess the correct implementation of individual tags in Google Tag Manager. Only certain Google tags have built-in consent.
Version label
In version 2 of Consent Mode two additional parameters were introduced;
ad_user_data and ad_personalization.
will be displayed if these two parameters are set and
if they're missing.
General state
If Consent Mode is correctly configured and
all checks are passed you should see
in the upper right corner.
Conversely, if there are one or multiple checks that failed you should see
instead.
General checks
The following are the major checks, they indicate whether the basic requirements are met.
-
GCM consent states are (NOT) set as "default"
This conclusion is derived on whether or not you consent parameters have been set-up with default consent states, based on the best-practice interpretation “denied” prior a consent.
These settings are added when you've implemented Cookiebot CMP using the tag template in Google Tag Manager, implemented Consent Mode via our WordPress plugin, or if you've added the inline Consent Mode script. -
Cookiebot to GCM signaling is (NOT) active
This checks whether the signaling from the banner to the dataLayer is working as intended, and updating the data value for GCM. If this check fails, your GTM/GCM triggers may not be set up correctly. -
(No) Non-essential Google trackers set prior to consent
This checks whether any non-essential Google trackers are being set in the browser before consent. This could indicate whether your triggers or tags have been correctly configured in Google Tag Manager. If this check fails, tags/services load without consent.
Consent parameters
Here each Consent Mode parameter is listed with their recommended and actual
default states. If the actual state matches the recommended default state you
should see the
label.
Conversely, you'll see the
label if the actual state doesn't match the recommended state or if it's "not
set".
Some of these trackers might not pose a risk for your specific website, please assess whether Google tracker can be set prior consent for your website specifically. See you Cookie report for full transparency.
Google Ads users can also check the Conversions Summary in Google Ads.
Comments
1 comment
Use the Google Consent Mode Checker in Cookiebot to verify your setup. Just log in, select your domain, and click Start GCM Check. The tool scans for issues like incorrect consent states or non-essential trackers being set too early. If any risks are found, fix them via Google Tag Manager or the Cookiebot script. While the tool identifies potential problems, consult your legal team to ensure full compliance.
Please sign in to leave a comment.