You can verify if consent mode v2 is enabled by using Google Tag Assistant to inspect the consent API calls on your site. You must confirm that the default consent is set to denied for all four signals before any tags fire. Then you check that the update command changes these signals to granted when a user accepts the cookie banner. This process ensures Google receives the correct data signals for modeling and reporting.
How to check if consent mode v2 is enabled
The quickest way to see if the mechanism is active is to look at the JavaScript being executed on the page. You do not need to log into any dashboard for this first step. You only need a browser and your site's URL. This check tells you if the code is present and if it is running in the correct order.
Step 1: Inspect the browser console
Open your website in a private browsing window. This is important because private windows do not carry over cookies from previous sessions. You want to see the fresh state of the page. Press F12 or right-click and select Inspect to open the developer tools. Click on the Console tab.
Type the following command and press Enter:
dataLayer
If you see an object with a gtm.consent property, consent mode is likely active. If the console is empty or returns undefined, the implementation might be missing or broken. You can also look for the specific default command. Search the console history for gtag('consent', 'default'. If you see this, the system is trying to set the initial state.
A practical way to automate this initial check is to use a consent mode checker which scans your container ID and reports whether the default signals are present without you having to manually inspect the console.
Step 2: Use Google Tag Assistant
Google Tag Assistant is the recommended tool for verifying implementations. It sits between you and the page, listening to all the tags that fire.
- Go to Google Tag Assistant.
- Enter your website URL.
- Click Start. A new tab opens with your site.
- Interact with the cookie banner. Click Accept All.
- Look at the Tag Assistant panel on the left.
In the Summary section, find the Consent event. Click on it. You will see an API Call section. Look for the parameters:
ad_storagead_personalizationad_user_dataanalytics_storage
For Consent Mode v2, all four must be present. If you only see ad_storage and analytics_storage, you are running v1, not v2. This is a critical distinction. v1 is no longer sufficient for EEA and UK traffic compliance. You need the two additional signals to keep your audience and conversion data intact.
Step 3: Verify the default state
The default state is the state of consent before the user makes a choice. For visitors in regions where consent is required, this must be denied.
In Tag Assistant, look at the earliest Consent event in the list. Check the API Call section again. The values for all four signals should be denied. If they are granted, your implementation is wrong. This means Google tags are firing as if the user had already consented. This violates privacy laws and can lead to data exclusion in your reports.
If you see denied in the default state, you are on the right track. Now you need to verify that the update works.
Step 4: Verify the update state
After you click Accept All on the cookie banner, a new Consent event should fire in Tag Assistant. This is the update event.
Select this most recent Consent event. Look at the API Call section. The values for the four signals should now be granted. If you clicked Reject, they should remain denied. If you clicked a custom selection, they should match that selection.
If the update event does not appear, your Consent Management Platform (CMP) is not communicating with Google tags. This is a common failure point. The banner might look fine, but the JavaScript bridge between the banner and the tags is broken.
What to look for in the dataLayer
The dataLayer is the bridge between your website and your tags. It stores the consent state so that all tags can read it. You can inspect it directly in the browser console.
Open the console on your site. Type dataLayer and press Enter. Look for an object named gtm. Inside it, look for a property named consent. It should look like this:
{
"gtm": {
"consent": {
"default": {
"ad_storage": "denied",
"ad_personalization": "denied",
"ad_user_data": "denied",
"analytics_storage": "denied"
}
}
}
}
If you see this structure, the default consent is set. If you see granted instead of denied, your default is wrong. If you do not see the consent property at all, consent mode is not enabled.
After you click Accept on the banner, the dataLayer should update. The default object should be replaced or joined by an update object with granted values. If the dataLayer does not change after your interaction, the update command is not firing.
Check the network requests
Sometimes the dataLayer looks correct, but the tags are not receiving the signal. You can verify this by looking at the network requests.
In the browser developer tools, switch to the Network tab. Reload the page. Look for requests to Google servers, such as google-analytics.com or googletagmanager.com.
Look at the query parameters in the request URL. You should see parameters like gcs and gcd.
gcsstands for Google Consent State.gcdstands for Google Consent Data.
These parameters encode the consent state. If the consent is denied, the parameters will reflect that. If the consent is granted, they will reflect that. If these parameters are missing, Google is not receiving the consent signal. This means your tags are firing without consent, which is a compliance issue.
You can also check the cookies. Look for the _ga and _gid cookies. If consent is denied, these cookies should not be set. If consent is granted, they should be set. If you see these cookies before the user has made a choice, your default consent is not working.
Verify in Google Ads and GA4
After you have verified the technical implementation, you should check the status in your dashboards.
Google Ads
Go to your Google Ads account. Navigate to Tools and Settings, then Measurement. Look for the Consent Mode status. It should show that Consent Mode is enabled. Note that it can take up to 48 hours for the status to appear after you fix your implementation. In some cases, it can take up to two weeks. If you have verified the setup in Tag Assistant, you can trust that it is working even if the dashboard is slow to update.
GA4
Go to your GA4 property. Navigate to Admin, then Data Collection. Look for the Consent Mode status. It should show that Consent Mode v2 is enabled. If it shows v1 or not enabled, your implementation is missing one of the four signals.
Common failures and how to fix them
Missing signals
If you only see two signals in Tag Assistant, you are running v1. You need to add the ad_user_data and ad_personalization signals to your default and update commands. This is usually done in your CMP settings or in your GTM container.
Wrong default state
If the default state is granted, change it to denied in your CMP or GTM. This is critical for compliance. If the default is denied but the tags are still firing, check the tag configuration. Make sure your tags are set to respect the consent state. In GTM, this is done by enabling the consent mode trigger.
Update not firing
If the update event does not fire after the user clicks the banner, your CMP is not sending the update command. Check your CMP documentation to ensure it is configured to send gtag('consent', 'update', {...}). Some CMPs require you to manually add this code.
Tags firing before default
If tags fire before the default consent is set, they run as if consent were granted. This is a common issue. Ensure that the default consent command runs before any Google tags. In GTM, you can achieve this by using a Custom HTML tag with the default command and setting it to load on All Pages. Then, set your Google tags to trigger only after the default consent is set.
When to seek help
If you have followed these steps and your implementation still does not work, it may be time to seek help. Consent Mode v2 is complex, and small errors can have big consequences. A broken implementation can lead to data loss, compliance issues, and wasted ad spend.
If you are struggling with the setup, consider working with a specialist who can audit your implementation and fix the issues. You can learn more about how we handle these complex tracking setups in our guide to server-side tracking. This approach often simplifies the consent management process and ensures that your data is accurate and compliant.
For more on how to set up your tracking correctly, read our article on setting up Google Analytics 4. It covers the basics of tag configuration and how to avoid common mistakes.
If you are looking for a full audit of your current tracking setup, you can contact us to discuss your specific needs. We can help you identify gaps in your implementation and provide a plan to fix them.
Summary
Checking if consent mode v2 is enabled is a multi-step process. You start by inspecting the browser console and dataLayer to see if the code is present. You then use Google Tag Assistant to verify that the default and update commands are firing with the correct signals. You check the network requests to ensure the signals are being sent to Google. Finally, you verify the status in your Google Ads and GA4 dashboards.
If any of these steps fail, your implementation is not working correctly. You need to fix the issue before you can trust your data. A broken consent mode setup can lead to data exclusion, compliance issues, and wasted ad spend. Take the time to verify your setup thoroughly. It is worth the effort to ensure that your tracking is accurate and compliant.
Remember, consent mode v2 is not optional for EEA and UK traffic. It is a requirement. Make sure your implementation is correct and up to date. If you are unsure, seek help from a specialist. Your data and your compliance depend on it.