> 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/activation-via-google-tag-manager.md).
# Activation via Google Tag Manager
If you wish to activate Google Consent Mode via Google Tag Manager (GTM), to have more control over its behavior or to load the Sirdata CMP scripts from GTM for example, that's entirely possible. Start by downloading this tag template "*Sirdata\_Google Consent Mode.tpl*" :
{% file src="/files/vyfMWLzcIzNh6xt0M6DT" %}
Then go to your [GTM account](https://tagmanager.google.com/), in the "*Templates*" section, and click on "*New*" in the "*Tag Templates*" table.
Then click on the three dots in the top right corner () and then on "*Import*".
Select the file "*Sirdata\_Google Consent Mode.tpl*" that you previously downloaded and upload it.
Then click on at the top right without changing anything, and then exit the editor using the close cross in the top left.
Go to the "*Tags*" section, and create a new one by selecting the new tag type "*Sirdata | Google Consent Mode*" which now appears in the custom tags:
In the configuration part, click on to add a configuration:
Select your criteria or keep the default suggestion:
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 if you wish to load the CMP from GTM:
{% 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!**
{% hint style="info" %}
Please visit the official [Google Consent Mode](https://support.google.com/analytics/answer/9976101?hl=en) page for more information
{% endhint %}
{% hint style="danger" %}
**WARNING**: Google Consent Mode does not cover given aspects related to the GDPR, such as the legal basis for processing personal data or potential data transfer to the United-States when they are based on the Standard Contractual Clauses of the European Union for example.
Please refer to the section dedicated to [Sirdata Analytics Helper](https://helper.docs.sirdata.net/v/english/) if your desire is to secure data transfers to Google Analytics in the United-States.
{% endhint %}
---
# 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/activation-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.
