> 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-of-basic-google-consent-mode/via-google-tag-manager.md).
# Via Google Tag Manager
If you wish to activate Google's Basic 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, this is entirely possible.
Go to your [GTM account](https://tagmanager.google.com/), navigate to the "Templates" section, and click on "Search Gallery" in the "Tag Templates" table.
Search for "Sirdata CMP | Google Consent Mode"
Add the "Sirdata CMP | Google Consent Mode" template to the workspace.
Go to the "Tags" section, then create a new tag by selecting the new tag type "Sirdata | Google Consent Mode" which now appears in the custom tags :
In the configuration section, click on  to add a configuration:
Select your criteria or keep the default suggestion (Refer to the official [Google Consent Mode page](https://support.google.com/analytics/answer/9976101?hl=en) for more information on these criteria if needed) :
Repeat the operation if necessary, for example, if you are making configurations differentiated by country. Click here for more information on these criteria.
Then configure your advanced options and enter your partner and configuration IDs 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 the Tag Manager.
{% endhint %}
Finally, select the trigger *"Consent Initialization - All Pages"* and 
Test using the preview mode, and publish if everything works as expected.
To complete the configuration of Basic Google Consent Mode, you need to condition the Google tags (Google Analytics, Google Ads, Google Floodlight, etc.).
**a) Conditioning Google Analytics**
* Create a Custom Event trigger with "sirdataConsent" in the "Event Name" field.
* Create a data layer variable named "sirdataExtraVendors".
* Add the "sirdataExtraVendors" variable to your trigger by setting it to "contains" and the ExtraVendor ID "|8|".
* Add a second data layer variable named "sirdataPurposes" :
* Add 3 variables 'sirdataPurposes' for purposes |1|, |9|, and |10| as follows:
* To finish, add your "sirdataConsent Google Analytics" trigger to your GA4 tag :
#### b) Conditioning Google Ads
* Create a custom event trigger with "sirdataConsent" in the "Event Name" field.
* Create a first data layer variable named "sirdataVendors" :
* Add the variable "sirdataVendors" to your trigger by setting it to "contains" and the Vendor ID "|755|".
* Add a second data layer variable named "sirdataPurposes":
* Add 3 custom events 'sirdataPurposes' for purposes |1|, |3|, and |4| as follows :
To finish, add your "sirdataConsent Google Advertising Products" trigger to your Google Ads tag:
---
# 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/activation-of-basic-google-consent-mode/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 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.