> 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/missing-default-signal.md).
# Missing \`default\` signal
#### Description
Google Consent Mode is enabled, but the **`default` signal is missing**. This means that no default consent settings are being sent to Google before user interaction. As a result, Google tags have no instructions on how to behave, which **prevents Consent Mode from working as intended**.
#### Possible causes
1. The `gtag` script (or Consent Mode stub) is:
* **missing** from the page;
* improperly integrated (e.g., loaded with `async` or `defer`, or delayed);
* **blocked or altered** by optimization tools (e.g., **Rocket Loader**, CDN caching, etc.).
2. If Consent Mode is initialized via **Google Tag Manager**:
* the **“Activate Google Consent Mode”** checkbox is not selected in the CMP tag;
* the **“Default Consent Mode Settings”** section is empty.
#### What to check
**If you are not using Google Tag Manager:**
* Ensure the `gtag` (stub) script is placed **at the very top of the ``**;
* Remove any `async` or `defer` attributes from the script;
* Make sure it is not delayed or modified by third-party systems like CDNs or optimization tools.
**If you are using Google Tag Manager:**
In your **Google Tag Manager** account, first ensure that your template is up to date. Update it if necessary.
Then:
* In the “Tags” section, edit the **ABconsent (Sirdata CMP)** tag
* Check the box labeled **“Activate Google Consent Mode”**
* Add a line of default consent signals (e.g., `"denied"`)
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://cmp.docs.sirdata.net/en/consent-transmission-standards/google-consent-mode/fix-implementation-errors/missing-default-signal.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.