# Missing \`update\` signal
#### Description
The `update` signal in Google Consent Mode is **not being sent**. This signal is required to communicate the user’s **final consent decision** (accept, reject, or customize). Without it, Google assumes no decision was made and may disable features by default.
#### Possible causes
* The script that calls `gtag('consent', 'update', {...})`:
* is **loaded too late** in the page;
* is **using the `defer` attribute**, which delays execution;
* is **altered or cached** by an optimization system such as **Rocket Loader** (Cloudflare), a CDN, or a performance plugin.
* The script is **loaded after Google Tag Manager**, which may prevent the signal from reaching Google tags in time.
#### What to check
**Recommended checks:**
* Ensure that the script containing `gtag('consent', 'update', {...})` is:
* **loaded without `defer` or `async` attributes**;
* **placed at the top of the ``**, **before any other script**, especially **before the Google Tag Manager container**;
* **not altered or delayed** by optimization tools (CDNs, Rocket Loader, etc.).
* Use browser developer tools or Google Tag Assistant to confirm that the `update` signal is correctly triggered.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://cmp.docs.sirdata.net/en/consent-transmission-standards/google-consent-mode/fix-implementation-errors/missing-update-signal.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.