> For the complete documentation index, see [llms.txt](https://cmp.docs.sirdata.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cmp.docs.sirdata.net/en/consent-transmission-standards/google-consent-mode/fix-implementation-errors/late-default-signal.md). # Late \`default\` signal Google Consent Mode is enabled, but the `default` consent signal is sent **too late**, meaning **after some Google tags have already fired**. In such cases, those tags may load **before the consent state is known**, reducing the effectiveness of Consent Mode. #### Possible causes 1. **Google Tag Gateway (GTG) was enabled via the Google Ads account** — This is the **most frequent cause** of late consent signals. When GTG is enabled through a Google Ads account (rather than Google Tag Manager), Google tags can load at the infrastructure level before the CMP has a chance to set consent defaults. To fix this, disable GTG in your Google Ads account and re-enable it via Google Tag Manager using the ABConsent CMP template. See the [Google Tag Gateway documentation](/en/consent-transmission-standards/google-consent-mode/google-tag-gateway.md) for details. 2. A Google script is loaded before the CMP 3. The `gtag` script is loaded **asynchronously or deferred**, or delayed by an optimization system: * presence of `async` or `defer` attributes on the main `