How to check if Google Consent Mode v2 is enabled

To check if Google Consent Mode v2 is enabled on your website, you must verify that four specific signals are being sent to Google before any other data collection starts. These signals are ad_storage, analytics_storage, ad_user_data, and ad_personalization. If even one is missing, your site is not compliant with the v2 standard. You can confirm this setup using Google Tag Assistant, browser developer tools, or a dedicated checker.

Is Google Consent Mode v2 enabled on my website?

This is the exact question you are asking. The answer depends on whether your site sends the correct commands at the right time. Consent Mode v2 requires a "default" state that denies all four signals when the page loads. It then requires an "update" state that reflects the user's actual choice from their cookie banner. If your site only sends the basic v1 signals, it fails the v2 check.

Many site owners assume that because they have a cookie banner, they are compliant. This is a common misconception. A banner alone does not tell Google how to handle data. The JavaScript commands behind the scenes do the work. If those commands are missing, mistyped, or firing in the wrong order, your tracking data is incomplete, and your ad account may face restrictions.

Use the free checker for a quick scan

Before diving into manual steps, run a quick automated scan. This saves time and gives you a baseline. You can use this free consent mode checker to see if your site is sending the correct signals. It tells you instantly whether the default and update states are present and valid for all four v2 parameters.

This initial check is useful because it highlights obvious failures. If the checker reports that ad_user_data or ad_personalization are missing, you know immediately that your setup is outdated. These two parameters were added in 2024. If your site was configured before that date, it likely only handles the older v1 signals. The checker identifies this gap without requiring you to open developer tools.

Verify with Google Tag Assistant

The most reliable way to verify your setup is to use Google Tag Assistant. This is the tool Google recommends for troubleshooting tag implementations. It shows you exactly what data your site is sending and when.

1. Open Google Tag Assistant in your browser.
2. Enter your website URL and start a new session.
3. Wait for the page to load completely.
4. In the Tag Assistant window, click on the "Consent" tab in the summary section.
5. Look for the "On-page Default" column. All four signals (ad_storage, analytics_storage, ad_user_data, ad_personalization) must be set to "Denied".
6. Interact with your cookie banner on the website. Accept the cookies.
7. Return to Tag Assistant and look for the "On-page Update" column. All four signals must now be set to "Granted".

If you see "Denied" in the default state and "Granted" in the update state after accepting cookies, your Consent Mode v2 is working correctly. If any signal remains "Denied" after acceptance, your cookie banner is not sending the update command correctly. If any signal is missing entirely, your JavaScript is not configured for v2.

Inspect the data layer in developer tools

If Tag Assistant gives you ambiguous results, you can inspect the raw data yourself. This method gives you the deepest level of detail. It shows you the exact JavaScript commands your site is firing.

1. Open your website in Chrome or Edge.
2. Press F12 or right-click and select "Inspect" to open Developer Tools.
3. Click on the "Console" tab.
4. Type the following command and press Enter: gtag('get', 'consent', function(v) { console.log(v); });
5. Look at the output in the console.

You should see an object that looks like this:

{
  "ad_storage": "denied",
  "analytics_storage": "denied",
  "ad_user_data": "denied",
  "ad_personalization": "denied"
}

If you see this object with all four keys, your site is sending the v2 signals. If you only see ad_storage and analytics_storage, you are on v1. If the console returns undefined or an empty object, your Google Tag script is not loaded correctly, or the consent commands are not present in your code.

Next, check the order of events. In the Console tab, type dataLayer and press Enter. Expand the array. Look for the first event that contains the string "consent". It must appear before any event related to GA4 or Google Ads. If consent events appear after other tracking events, your tags are firing before consent is set. This causes data loss and compliance issues.

Check your Google Tag Manager configuration

If you use Google Tag Manager, the problem is often in the container settings. You need to ensure that your tags are configured to respect consent.

1. Log in to your Google Tag Manager account.
2. Select the correct container for your website.
3. Go to "Tags" and find your Google Analytics 4 Configuration tag.
4. Click on the tag to edit it.
5. In the "Enable Consent Mode" section, ensure that the option is set to "Yes".
6. Check that the "Consent Initialization" tag is set to fire on "All Pages" and before all other tags.

If you do not see the "Enable Consent Mode" option, your GTM version may be outdated. Update your GTM container to the latest version. Also, check your cookie banner integration. If you use a third-party CMP like Cookiebot, OneTrust, or Quantcast, ensure that the CMP is configured to send the v2 signals. Many older integrations only send v1 signals. You may need to update the CMP settings or add custom JavaScript to send the missing ad_user_data and ad_personalization parameters.

Common reasons your check fails

Even if you follow the steps above, you might still see failures. Here are the most common causes.

• Outdated JavaScript: Your site is using an old version of gtag.js that does not support v2. Update your Google Tag snippet to the latest version.
• Missing parameters: Your code only sends ad_storage and analytics_storage. You must add ad_user_data and ad_personalization to both the default and update calls.
• Wrong order: Your consent commands fire after your tracking tags. This means tags read the default state instead of the user's choice. Move the consent initialization code to the top of your <head> section.
• Typo in values: The values must be exactly "granted" or "denied". Capitalization matters. "Granted" or "DENIED" will cause errors.
• Blocked by ad blockers: Some ad blockers prevent Google tags from loading entirely. This is not a consent mode failure, but it can look like one in testing. Disable ad blockers when testing.

If you are using a platform like WordPress, Shopify, or Wix, the implementation details vary. On WordPress, you might need to edit your theme's header.php file or use a plugin that supports v2. On Shopify, you can add the code to the online store theme's theme.liquid file. On Wix, you may need to use the Wix Apps marketplace to find a consent management app that supports v2.

What to do if your setup is broken

If your checks reveal that Consent Mode v2 is not enabled or is misconfigured, do not ignore it. Google is actively monitoring compliance. Sites that fail to send the correct signals may have their measurement data restricted. This means your analytics will show incomplete data, and your ad campaigns may not receive accurate conversion signals.

The fix usually involves updating your JavaScript code. You need to ensure that the gtag('consent', 'default', {...}) call includes all four parameters set to "denied". Then, you need to ensure that the gtag('consent', 'update', {...}) call fires when the user interacts with the cookie banner, setting the parameters to "granted" or "denied" based on their choice.

If you are not comfortable editing code, you can hire a developer to make the changes. Or, you can use a consent management platform that handles the technical setup for you. When choosing a CMP, verify that it explicitly supports Consent Mode v2 and sends all four signals. Ask for documentation or a demo to confirm.

For a deeper look at how to structure your tracking stack to handle these compliance requirements, consider exploring our guide on server-side tracking. It covers how to move your consent logic to the server for better reliability.

Final verification steps

After you make any changes, repeat the verification process. Do not assume that the fix worked. Test it again.

1. Clear your browser cache and cookies.
2. Reload your website.
3. Run the free checker again to confirm the signals are present.
4. Use Google Tag Assistant to verify the default and update states.
5. Check the console in developer tools to see the raw data.

Only when all three methods confirm that the four signals are present and correctly updated can you say that Google Consent Mode v2 is enabled on your website. This process takes about ten minutes if your setup is correct. If it takes longer, you likely have a technical issue that needs developer attention.

Remember that compliance is not a one-time task. If you update your cookie banner, change your web host, or modify your site structure, you must re-verify your consent mode setup. Set a reminder to check this every six months. It ensures that your tracking remains accurate and your site stays compliant with evolving privacy standards.

If you need help with your tracking setup, you can contact us for a consultation. We specialize in building tracking systems that work correctly and stay compliant.