> 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: 
<script>
    window.ABconsentCMP = window.ABconsentCMP || {};
    window.ABconsentCMP.gtmDataLayerName = "NOM_DU_DATALAYER_PERSONNALISÉ";
</script>
--- # 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/incorrect-data-layer-name.md?ask=&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.