> 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/mandatory-prerequisite.md). # Mandatory Prerequisite To activate a version of the Sirdata CMP compatible with Google Consent Mode, here are the prerequisites to set up: ## 1) Activation of the "Google Advertising Products" partner Ensure that the Google Advertising Products partner (ID: 755) is activated in your partner list :

Partner "Google Advertising Products" (ID: 755)

## 2) Activation of the "Google Analytics" partner Make sure that the Google Analytics partner (ID: 8) is properly activated in your partner list :

## 3) Activation of Google Consent Mode ### a) You have not disabled the Google Consent Mode option (Implementation of the CMP hardcoded or via a CMS) The Google Consent Mode option is enabled by default with the Sirdata CMP :

This option allows activating the Google Consent Mode via the Sirdata CMP when the Sirdata CMP is implemented hardcoded or through a CMS. ### b) You have disabled the Google Consent Mode option (Implementation of the CMP via Google Tag Manager) If you want to implement the Sirdata CMP via GTM, you need to disable this option and use the "Sirdata CMP | Google Consent Mode" template available in the Google Tag Manager Gallery :

Tag template "Sirdata CMP | Google Consent Mode"

--- # 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/mandatory-prerequisite.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.