Articles on: Integrations

Google Tag Gateway (GTG) and consent

Google Tag Gateway & "Late Consent" — Merchant Guide


What is Google Tag Gateway (GTG)?


Google Tag Gateway for advertisers (also called first-party mode) lets your Google measurement scripts — Google Analytics 4 (GA4), Google Ads, and Google Tag Manager (GTM) — load from your own domain (for example https://your-store.com/metrics/...) instead of from Google's servers (googletagmanager.com).

Because the script now comes from your own domain, browsers and ad blockers are less likely to block it, so you recover more ad and analytics measurement.

The most common way to turn it on is the one-click setup in Google Tag Manager using Cloudflare.



Google Consent Mode works by reading your visitors' consent choices before any Google tag is allowed to run. Consentmo does this by setting the Consent Mode default state (everything denied) the moment the page loads, before your Google tags fire.

A "late consent" signal happens when a Google tag reads or fires before Consentmo has set that default state. Google's own guidance is clear: if the consent default is set out of order, consent defaults won't work.

Why it matters: Google may treat those signals as non-compliant, which can reduce your conversion measurement and remarketing eligibility — and it counts against your store in privacy audits.

Why Google Tag Gateway often causes it: with the one-click Cloudflare setup, Google's infrastructure decides when the tag loads — often before your cookie banner script runs. When that happens, the tag starts working before Consentmo can set the consent default.

How do I know if I'm affected?


Consentmo checks this for you automatically.


  1. In the Consentmo app, go to Integrations → Google Consent Mode V2.


  1. Click Check status (the Integration Checker).


  1. If Consentmo detects a late consent signal, you'll see a warning banner titled


"Possible late consent signal detected", with the steps below.

The two checks that trigger this warning are:

  • "Defaults applied correctly" fails → consent defaults were set too late (or not at all).
  • "No GA4/Ads hits before consent" fails → Google tags sent data before the visitor consented.


Step 1 — Check whether Google Tag Gateway is enabled


Before changing anything, confirm GTG is actually on (it's the most common cause).

Check in Google Tag Manager:

  1. Sign in to Google Tag Manager.


  1. Click Admin in the top navigation.


  1. Under your container settings, look for Google tag gateway. If it's configured (you'll see a

measurement path), GTG is enabled.


Or check in Cloudflare:


  1. Sign in to the Cloudflare dashboard.


  1. Select your domain → open the Google Tag Gateway page.


  1. If the toggle is on, GTG is enabled for your site.


Or check on your live store: open your storefront, open the browser's Network tab, and reload. If GA4/Ads/GTM requests are served from your own domain (not googletagmanager.com), GTG is active.



Google's recommended fix for GTG-enrolled stores is Advanced Consent Mode. With one-click GTG, you can't control when the tag loads, and Advanced Consent Mode is the only option that works regardless of load order — tags load in a restricted, cookieless state and update the moment the visitor chooses.



  1. In Consentmo, go to Integrations → Google Consent Mode V2.


  1. Make sure the integration is enabled and your GTM / GA4 / Google Ads IDs are filled in.


  1. Under Consent mode type, select Advanced (recommended).


  1. Save your changes.

2b. Enable Data Transmission Controls in Google Tag Manager


  1. Sign in to Google Tag Manager.


  1. Go to Admin → Container Settings (or Consent Settings).


  1. Enable Data Transmission Controls.



  1. Still in Google Tag Manager, configure Global Consent Defaults so that ad and analytics

storage are denied by default in the regions where you require consent (e.g. EEA/UK).


  1. Set these according to your own regional compliance requirements.

Official Google reference: Set up Consent Mode — https://developers.google.com/tag-platform/security/guides/consent and About Advanced Consent Mode — https://developers.google.com/tag-platform/security/concepts/consent-mode


Step 3 — Verify the fix worked


  1. Save all changes in Consentmo and Google Tag Manager, then publish your GTM container.


  1. Return to Consentmo → Integrations → Google Consent Mode V2.


  1. Click Check status again.


  1. The "Defaults applied correctly" and "No GA4/Ads hits before consent" checks should now

pass, and the late consent warning should disappear.

If the warning persists, double-check that GTM was published (not just saved) and try one of the alternative fixes below.


Alternative fixes

If Advanced Consent Mode isn't an option for your setup, you can instead:


  • Route all Google tags through a GTM container. When every Google tag is managed by GTM, GTM applies the consent defaults before any tag fires.
  • Use a manual Google Tag Gateway deployment instead of the one-click Cloudflare CDN injection. A manual deployment lets you control script order, so you can ensure Consentmo's banner loads and sets consent defaults before the Google tag script. Google's setup reference: https://developers.google.com/tag-platform/tag-manager/gateway/setup-guide


FAQ


Do I have to turn off Google Tag Gateway?

No. GTG is good for measurement recovery. You just need consent handled correctly — Advanced Consent Mode (Step 2) does this without disabling GTG.


Is Advanced Consent Mode less private?

No. Tags load in a restricted, cookieless state and only collect full data after the visitor grants consent. Until then, Google receives privacy-safe signals only.


I don't use Google Tag Gateway — why am I seeing this warning?

Late consent can also come from other tags loading before the banner, an asynchronous theme script, or a Google tag added directly in your theme. Make sure Consentmo manages your Google tags (don't also add them manually in the theme), then re-run the checker.


Where do I change the consent mode type?

Consentmo → Integrations → Google Consent Mode V2 → Consent mode type → Advanced.


Still stuck?

Contact Consentmo support with your store URL and a screenshot of the Integration Checker result, and we'll help you confirm the setup.

Updated on: 19/06/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!