> 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 `<head>`**;
* 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.

<figure><img src="https://1869615683-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MUspPnkTFMlMDdGxvAb-1972196547%2Fuploads%2FGOQLUHl0uwtke7ADh5F0%2Fimage.png?alt=media&amp;token=e0bdf842-1c6d-46e6-83d3-569cd5e53b1a" alt=""><figcaption></figcaption></figure>

**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.

<figure><img src="https://1869615683-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MUspPnkTFMlMDdGxvAb-1972196547%2Fuploads%2FCYejVdyuXapQmwRbIrY4%2Fimage.png?alt=media&amp;token=3de92a89-a8eb-4205-b679-3c9d0dbf0bc1" alt=""><figcaption></figcaption></figure>

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"`)

<figure><img src="https://1869615683-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MUspPnkTFMlMDdGxvAb-1972196547%2Fuploads%2FQK3twEkqAAOaI1ntJps9%2Fimage.png?alt=media&amp;token=79183ce8-aca9-45bb-aa0a-0d75152353c3" alt=""><figcaption></figcaption></figure>


---

# 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/missing-default-signal.md?ask=<question>&goal=<user_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.