> 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-update-signal.md).
# Late \`update\` signal
#### Description
The `update` signal in Google Consent Mode is sent **too late** — meaning **after the maximum allowed wait time** for Google tags (typically 500 ms). When this happens, tags may fire without taking the user’s choice into account, reducing the effectiveness of Consent Mode.
#### Possible causes
1. If the Consent Mode script is **hardcoded into the page**:
* The script uses the `defer` attribute, which **delays execution**;
* The script is **altered, cached, or delayed** by an optimization system such as **Rocket Loader** (Cloudflare), a CDN, or a performance plugin.
2. If Consent Mode is managed via **Google Tag Manager**:
* The **“Wait for update”** (`waitForUpdate`) setting has a **timeout that is too short**, causing tags to fire before the `update` signal is received.
#### What to check
**If you are not using Google Tag Manager:**
* Make sure the script is **not loaded with `defer`** ;
* Disable or configure any third-party system (e.g., Rocket Loader) that may delay or cache the script.
**If you are using Google Tag Manager:**
* Open the relevant tag (e.g., Analytics or Ads) ;
* Enable the **“Wait for update”** option ;
* Increase the timeout value — e.g., **800 ms or 1000 ms** — in the appropriate field.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://cmp.docs.sirdata.net/en/consent-transmission-standards/google-consent-mode/fix-implementation-errors/late-update-signal.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
