Skip to Content
InstallationLate consent signals

Understanding late consent signals

A late consent signal occurs when a Google tag begins processing measurement activity before consent information has been made available.

Late consent signals are typically caused by script initialization order.

Example:

  1. Google Tag initializes.
  2. Measurement begins.
  3. Consent defaults are applied later.

In this scenario, Google may report that consent information was received too late.

How GTG can contribute

Google Tag Gateway can alter how Google Tags are loaded and initialized.

Depending on the deployment architecture, a Google Tag may become available before CookieHub or Google Tag Manager has established consent defaults.

This is most likely with one-click CDN injection. Enabling GTG through a CDN provider requires no change to the site itself, so the Google Tag is injected and initialized by the CDN rather than by the page. This often leaves the customer with no control over the load order, and the tag can begin measurement before the consent script has run.

Deployments where the customer controls the script import order, such as a manual GTG setup or Google Tags managed through Google Tag Manager, do not have this limitation.

Google may report late consent warnings through:

If a late consent signal is detected and GTG enrollment is verified, we encourage customers to adopt one or more of the following, according to their deployment and need.

Advanced Consent Mode allows Google tags to receive consent updates after initialization while respecting consent defaults.

Where the Google Tag remains enrolled in GTG, advanced consent mode is the recommended mechanism, because it stays compatible with a manual GTG deployment where the customer controls the script import order.

Global Consent Defaults provide default consent states before user interaction occurs.

Data Transmission Controls

Data Transmission Controls provide additional controls over how data is transmitted to Google services.

Deploy Google Tags through GTM

Managing Google Tags through GTM can help ensure consent defaults are applied before measurement begins.

Manual GTG deployments

Manual GTG deployments may allow greater control over script initialization order.

CookieHub automatically checks for Consent Mode deployment issues during website scans.

CookieHub Action Center can automatically detect potential late consent signal conditions and provide deployment-specific remediation guidance.

When a potential late consent signal is detected, CookieHub will:

  • Flag the issue in the Action Center.
  • Include the finding in website scan reports.
  • Provide guidance on possible remediation steps.

These diagnostics can help identify deployment issues involving Google Tag Gateway (GTG), Google Tag Manager (GTM), Consent Mode, and tag initialization order.

CookieHub recommendation

Where the Google Tag remains enrolled in GTG rather than managed through GTM, we recommend advanced consent mode, because it stays compatible with a manual GTG deployment where the customer controls the script import order.

When CookieHub is deployed through GTM, we recommend managing Google Tags through GTM rather than automatically configuring tags through GTG, particularly when a late consent signal has been detected.

This helps ensure consent defaults are available before measurement occurs.

Last updated on
Deployment recommendationsTroubleshooting