> 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/install/via-a-tag-manager/loading-via-google-tag-manager.md).
# Loading via Google Tag Manager
\
If you want to load the Sirdata CMP via Google Tag Manager (GTM), you must also enable Google Consent Mode via GTM to have more control over its behavior. To do this, go to your GTM account, navigate to the "Templates" section, and click on "Search Gallery" in the "Tag Templates" table.
Tag templates
Search for "Sirdata CMP | Google Consent Mode"
"Import a tag template"
Add the "Sirdata CMP | Google Consent Mode" template to the workspace.
"Add the template"
Go to the "Tags" section, then create a new one by selecting the new tag type "Sirdata CMP | Google Consent Mode" that now appears in the custom tags.
In the configuration part, click on to add a configuration:
Select your criteria or **keep the default suggestion in case of doubt**:
Repeat the operation if necessary, for example if you are making configurations differentiated by country. Click [here](https://developers.google.com/tag-platform/devguides/privacy?hl=en) for more information on these criteria.
Then configure your advanced options and enter your partner and configuration identifiers:
{% hint style="info" %}
If you do not load the Sirdata CMP from GTM, it is **mandatory** to load it from the site, and the CMP scripts must be loaded **before** Google Tag Manager.
{% endhint %}
Finally, select the trigger "*Consent Initialization - All Pages*" and .
Test via preview, and publish if everything works as expected.
**Congratulations!**
---
# 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/install/via-a-tag-manager/loading-via-google-tag-manager.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.
