> 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

## 1) Activation of the "Google Advertising Products" partner

Ensure that the Google Advertising Products partner (ID: 755) is activated in your partner list :

<figure><img src="/files/V919bVFKQCj0eTeMwgNk" alt=""><figcaption><p>Partner "Google Advertising Products" (ID: 755)</p></figcaption></figure>

## 2) Activation of the "Google Analytics" partner

Make sure that the Google Analytics partner (ID: 8) is properly activated in your partner list :

<figure><img src="/files/Lnu2Pqdwi5zE4SnHpItS" alt=""><figcaption><p>Partner "Google Analytics" (ID: 8)</p></figcaption></figure>

## 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 :

<figure><img src="/files/XF60RJgZFIuEmG4Oqm4v" alt=""><figcaption><p>Option "Google Consent Mode"</p></figcaption></figure>

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 :

<figure><img src="/files/cmQ0oqQb8K34W4yCX9FI" alt=""><figcaption><p>Tag template "Sirdata CMP | Google Consent Mode"</p></figcaption></figure>


---

# 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/mandatory-prerequisite.md?ask=<question>&goal=<endgoal>
```

`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.