Verifying Your GTG Integration via Google Tag Manager

Verify your integration in Google Tag Manager (recommended)

The Google Tag Assistant check in the previous section tells you whether GTG is serving your tags. To confirm those tags actually read your visitors' consent in the right order, the most reliable approach is to verify inside Google Tag Manager (GTM). We recommend GTM verification for any site using GTG, because it shows you the real consent state each tag sees at the moment it fires, something a surface-level page scan cannot.

Why Google Tag Manager is the most reliable check

• It shows per-tag consent state. GTM's Preview mode (Tag Assistant) reports, for every Google tag, whether each consent type was granted or denied and whether the tag was blocked or allowed to fire
• It reveals load order, not just presence. You can see the default consent state being set first, then the consent update after the visitor chooses, confirming there is no late signal.
• It reflects what your visitors actually experience. Because GTG can serve your GTM container from your own domain, verifying inside GTM tests the exact path your live traffic uses.

For Google's reference on consent in GTM, see: Tag Manager consent mode support.

Before you start

• A Google Tag Manager container deployed on the site. If your GTG setup serves the GTM container (rather than individual Google tags), this is the most reliable configuration to verify. 
• Edit or Preview access to that container. 
• Your Termly consent banner installed and Google Consent Mode enabled in the Termly dashboard.

Verify in GTM Preview mode (Tag Assistant)

1. In Google Tag Manager, open your container and click Preview. Enter your website URL and click Connect. Tag Assistant opens your site in a debug window.

2. Before interacting with the banner, open the Consent tab and check the default consent state. The Google consent types, ad_storage, analytics_storage, ad_user_data, ad_personalization, should read denied (or your configured regional default) before any tag fires. 

3. On the initial container load event, open the Tags tab. Your Google tags should appear under Tags Not Fired (held by a consent check), or, if you use Advanced Consent Mode (U+C), fire in a cookieless state. No tag should fire with consent granted before the visitor chooses. 

4. Accept consent on the banner. A consent update event should appear in the event timeline. Confirm the relevant consent types switch to granted and the corresponding Google tags now fire. 

5. Back in the Consent tab, confirm each Google tag passes its Built-In Consent Checks and any Additional Consent Checks you have configured, GTM flags any tag whose required consent was not granted. 

6. Confirm the full sequence: default (denied) → tags held or cookieless → consent update → tags fire. If a tag reads consent before the default is set, that is the late signal this article addresses, return to the What to do next section.

Cross-check with other Google properties 

Google Tag Manager is the primary check. For additional confidence, confirm the same behaviour through Google's other tools: 

• GA4 DebugView (Admin → DebugView): confirm events only carry full data after consent, and that the consent state is reported correctly. 
• Google Tag Assistant (standalone): confirm the gateway-served tag loads from your own domain and that consent signals are present. 
• Google Ads consent diagnostics: for advertisers, check the Consent Mode status in your Ads account to confirm signals are being received. 

What a healthy result looks like

If verification fails 

If GTM shows a tag firing before the default consent state is set, or an Additional Consent Check failing, your site still has a late consent signal. Follow the path in the What to do next section that matches your setup, then re-run the GCM Checker from your Termly dashboard to confirm the signal is resolved. 

For a full walkthrough of Termly's automated check, see: How to validate Termly's Integration with Google Tag Manager.