DocsBlogIntegrationsSign InSign Up
Integrations

Google: Consent Mode V2 (GCM) Scanning User Guide

Guide on using Concord’s Google Consent Mode V2 scanning feature to validate your website’s compliance with Google Consent Mode V2 requirements.

This guide explains how to use Concord's Google Consent Mode V2 (GCM) scanning feature to validate your website's compliance with Google's Consent Mode V2 requirements. Google Consent Mode V2 scanning checks every domain in a project automatically each week, and you can also scan a specific domain or any URL on demand.

Google Consent Mode V2 scanning validates your website's Consent Mode implementation by analyzing:

  • Consent Mode Implementation: Checks if Google Consent Mode V2 is properly configured on your pages
    • Configuration Issues: Identifies missing or incorrect Consent Mode signals
  • Default Consent States: Validates required ad_storage, analytics_storage, ad_user_data, and ad_personalization settings
    • Signal Updates: Verifies consent signals update properly after user interaction

The scanner detects four main categories of consent mode issues:

  • Consent tab empty: No consent mode implementation or blocked Google tags
  • Default consent set too late: Consent defaults set after Google tags load
  • Default consent not set: Missing default values for required parameters
  • Consent doesn't update: No consent updates after user interaction

Google Consent Mode scans run from Actions.

Weekly Scans of All Project Domains

Every project has a managed Google Consent Mode Scan that covers all of its domains and runs every week on its own, at no cost. Find it under Actions → Your Actions. To get fresh results between weekly runs, run it now; an on-demand run uses 500 Actions for each project domain.

Scanning a Specific Domain or a Custom URL

  1. Go to Actions → Browse Catalog and choose Google Consent Mode Scan.
  2. Choose the Specific Domain tab to scan one of your domains or subdomains, or the Custom URL tab to scan any page by entering its URL, including https://.
  3. Run the scan, or save it to your actions to run again later.

A manual scan uses 500 Actions per domain. See Actions and Data Credits.

Viewing Results

Each run appears in the Activity list under Actions. Expand a run to see the domains scanned and the result for each. If a scan couldn't reach a site, the result says Couldn't Scan, and Concord tries again on the next scan.

Email Alerts

When a scheduled scan finds issues, Concord sends a configuration issue notification in the app and by email. You'll only hear about the same issues again if they change on a later scan. Scans you run manually notify you in the app only. Manage which notifications you get by email under My Profile → Notification Settings.

The Google Consent Mode V2 scan will return one of the following results:

Success Status Messages:

  • Google Consent Mode implemented correctly: Site has proper consent mode implementation
  • No Google Tag Manager detected on site: No GTM found. This is considered a success message as it is assumed that GTM is not expected on that site

Warning Status Messages:

  • Google Tag Manager found but google_tag_data not available: GTM present but data unavailable (possible bot detection)
  • Consent doesn't update: Consent mode found but doesn't update after user interaction
  • Google Consent Mode status unclear - please review implementation: Implementation status uncertain

Error Status Messages:

  • Google Consent Mode is not implemented: No consent mode implementation found
  • Default consent set too late: Default consent configured after Google tags loaded
  • Default consent not set: Only implicit consent used, no default consent values

If a scan reports Default consent set too late, the result links to How to fix late consent (Google tag gateway guide), which explains how to check whether the tag is served through the Google tag gateway and what to do next.

For more information on how to troubleshoot Google Consent Mode errors, see Google’s support document here: https://support.google.com/tagmanager/answer/14522438?hl=en&ref_topic=14226291&sjid=3529498632806005727-NA

Support

If you have questions about Google Consent Mode V2 scanning or need help interpreting scan results, contact google@concord.tech or support@concord.tech.

Our support team can help with:

  • Troubleshooting consent mode implementation problems
  • Understanding scan results and status messages

Conditionally Load Third-Party Tags in GTM

Learn how to configure Google Tag Manager (GTM) triggers so third-party tags only fire after visitors grant consent via Concord, ensuring GDPR compliance regardless of Basic or Advanced Consent Mode.

Google: Google Tag Gateway (GTG) and Consent Mode

What Google Tag Gateway (GTG) is, how first-party script serving can affect consent load order, how to verify whether a tag is enrolled in GTG, and what to do when Concord detects a late consent signal on a GTG-enabled tag, including adopting advanced consent mode (U+C).

On this page

What is Google Consent Mode V2 Scanning?Google Consent Mode V2 Issue DetectionRunning Google Consent Mode V2 ScansWeekly Scans of All Project DomainsScanning a Specific Domain or a Custom URLViewing ResultsEmail AlertsUnderstanding Google Consent Mode V2 Scan ResultsRelated ArticlesSupport