> 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/incorrect-default-signal-ad_user_data.md).

# Incorrect default signal (\`ad\_user\_data\`)

#### Description

Google Consent Mode is active, but the `default` signal sets an incorrect value for `ad_user_data`. This parameter controls users'data processing for ad personalization. If the value is anything other than `"denied"`, Google may begin tracking before consent is obtained, which **defeats the purpose of Consent Mode**.

#### Possible causes

1. If your CMP is **not integrated via Google Tag Manager**:
   * A hardcoded `gtag` command like:

     ```js
     gtag('consent', 'default', {
       ad_user_data: 'granted'
     });
     ```

     is present somewhere in your code or injected by another script.
2. If your CMP **is integrated via Google Tag Manager**:
   * The `ad_user_data` field in the **Default Consent Mode Settings** is not set to `"denied"` ;
   * Another tag in GTM may override the value with a different `gtag` call.

#### What to check

**If you are not using Google Tag Manager:**

* **Search your codebase** for any `gtag('consent', 'default', {...})` command;
* Remove or modify any line that sets `ad_user_data` to `"granted"` or another incorrect value.

**If you are using Google Tag Manager:**

* Open your CMP tag (e.g., **ABconsent – Sirdata CMP**) ;
* In the **"Default Consent Mode Settings"** section, make sure `Advertising` is set this way:

<figure><img src="/files/KQFre92Qkzx22MMuclZW" 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 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/incorrect-default-signal-ad_user_data.md?ask=<question>&goal=<endgoal>
```

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