DocsBlogIntegrationsSign InSign Up
Integrations

Google: Google Tag Gateway (GTG) & 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).

Overview

Google Tag Gateway (GTG) for advertisers lets you serve Google scripts (the Google tag or a Google Tag Manager container) from your own first-party domain, typically through a content delivery network (CDN) or a server-side endpoint. Google recommends it as a durable tagging configuration that improves measurement signal recovery.

Because GTG changes how and when Google scripts load on the page, it can interact with the order in which Concord's Consent Mode default command (and, where applicable, the IAB TCF stub) is established. This guide explains that interaction and what to do if it causes a late consent signal.

For Google's own reference, see Google tag gateway for advertisers and the GTG setup guide.

For Concord to control measurement before consent, the Consent Mode default command (and the TCF stub, if you use IAB TCF) must be present on the page before any Google tag fires. See Understanding & Configuring Google Consent Mode (GCM) V2 for how Concord establishes those defaults.

Some GTG setups, particularly one-click CDN injection offered by certain CDN providers, inject and serve Google scripts automatically and often remove your control over script load order. When Google tags load ahead of Concord's default command or TCF stub, the consent signal arrives after tags have already initialized. This is what Concord reports as a late consent signal.

GTG setups where you retain control over import order, for example, a manually configured CDN integration, or routing all Google tags through a Google Tag Manager container that you deploy via GTG, do not have this problem, because you can guarantee Concord loads first.

Verifying whether a tag is enrolled in GTG

Before changing anything, confirm whether the late-firing tag is actually served through GTG:

  • Use Google Tag Assistant to inspect how the tag loads, or follow Verify your Google tag in Tag Manager Help.
  • Review your CDN or Google Tag Manager configuration for GTG / first-party serving. Google's setup documentation is in Tag Manager Help.

Concord's in-product Consent Mode validation also surfaces this guidance directly when it detects a late consent signal.

When Concord's Google Consent Mode validation reports that default consent values were set after tags loaded and you have verified the tag is enrolled in GTG, take one of the following paths.

For GTG-enabled tags, advanced consent mode (U+C) is the recommended mechanism because it is compatible with manual GTG. In advanced consent mode, Google tags are allowed to load before consent and send a minimal, cookieless signal, then full measurement resumes once the user makes a choice, so a slightly later default command does not lose measurement.

When adopting U+C, also enable Data Transmission Controls and Global Consent Defaults according to your needs. See How to Enable Basic or Advanced Modes for Google Consent Mode V2 in Concord to switch Concord to Advanced mode, and Google's Consent Mode documentation for these settings.

Alternative: take control of load order

If you prefer to keep tags blocked before consent (basic consent mode), restore control over import order so Concord loads first:

  • Route all Google tags through a Google Tag Manager container and deploy GTM via GTG. This keeps a single, ordered entry point you control. See Google tag gateway with CDN + server-side GTM.
  • Set up GTG manually (rather than one-click CDN injection) so you control the script import order and can guarantee Concord's default command / TCF stub loads before Google tags. See the GTG setup guide.

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.

Google: Understanding & Configuring Google Consent Mode (GCM) V2

Google Consent Mode V2 allows websites to adjust how and when data is shared with Google based on user consent collected via the Concord Consent Banner & Privacy Center. This article explains what Google Consent Mode (GCM) V2 is, how it works, and steps you through how to enable GCM in your Concord organization.

On this page

OverviewHow Google Tag Gateway affects consentVerifying whether a tag is enrolled in GTGIf Concord detects a late consent signal on a GTG-enabled tagRecommended: adopt advanced consent mode (U+C)Alternative: take control of load orderRelated Articles