> 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-data-layer-name.md).

# Incorrect data layer name

#### Description

At least one Google service detected on the page **is not using the default data layer name `dataLayer`**. This may cause inconsistencies when triggering tags or passing consent signals — especially if multiple data layers exist or if the CMP does not communicate with the correct global object.

#### Possible causes

* One or more Google tags (Google Ads, Google Analytics, etc.) are configured to use a **custom data layer name** (e.g., `myDataLayer`, `gtmDataLayer`, etc.).
* If the CMP is **not loaded via Google Tag Manager**, it assumes the default name is `dataLayer` unless specified otherwise.

#### What to do

**Recommended solution:**

* **Use a consistent data layer name** across the entire website (ideally `dataLayer`, unless a different name is strictly required).

**If you intentionally use a custom data layer name and your CMP is not loaded via GTM:**

* Declare the correct name **before the CMP is loaded**, using the following line:

<pre><code>&#x3C;script>
    window.ABconsentCMP = window.ABconsentCMP || {};
<strong>    window.ABconsentCMP.gtmDataLayerName = "NOM_DU_DATALAYER_PERSONNALISÉ";
</strong><strong>&#x3C;/script>
</strong></code></pre>

<figure><img src="/files/PqUbZxfmwEHHtk2gpiNs" 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-data-layer-name.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.