Google Tag Gateway troubleshooting

This page covers common issues when using CookieHub with Google Tag Gateway. For deployment guidance, see Deployment recommendations.

Possible causes:

Google Tag initialized before CookieHub established consent defaults.
Automatic Google Tag setup is enabled in GTG while CookieHub is loaded through GTM.
Consent Mode configuration is incomplete.

Recommended actions:

Verify CookieHub initialization order.
Verify GTG enrollment.
Review Advanced Consent Mode configuration.
Review Global Consent Defaults.

Google Tag is enrolled in GTG but measurement is not working

Possible causes:

Google Tag configuration is incomplete.
The GTG deployment may require additional Google Tag configuration.
Tag ID or measurement ID is not connected correctly.

Recommended actions:

Confirm the Google Tag ID used in GTG matches the tag configured in Google Analytics or Google Ads.
Verify GTG enrollment in Tag Assistant.
Confirm the Google Analytics data stream and Google Ads conversion tracking are active and receiving data.

Possible causes:

Google Tag is being automatically configured by GTG before GTM finishes loading.

Recommended actions:

Allow GTM to manage the Google Tag.
Verify consent defaults are established before measurement begins.

How do I verify GTG enrollment?

Use Google Tag Assistant to:

Verify the tag is enrolled in GTG.
Verify consent information is being received.
Review initialization and measurement diagnostics.

Refer to Google’s GTG verification documentation for detailed instructions.

Need additional help?

If you continue to experience GTG-related consent issues, contact CookieHub support and provide:

GTG implementation details
Tag Assistant screenshots
Google diagnostics information
Consent Mode configuration details

Last updated on April 28, 2026

Late consent signals Conditional HTML tags