# Via the Sirdata CMP

## 1) Activation of Advanced Google Consent Mode

The first and simplest way to activate Google's Advanced Consent Mode is to log in to your[ Sirdata CMP account](https://cmp.sirdata.io/) and go to the [configuration section.](https://cmp.sirdata.io/cmp)

Click on the edit icon of your CMP, or the one installed on the relevant site if you have multiple (button ![](https://1869615683-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MUspPnkTFMlMDdGxvAb-1972196547%2Fuploads%2FD0l6awKQ1SscG0HzzqRY%2Fimage.png?alt=media\&token=eae27599-bba9-43fc-bdac-74808393a877)located on the right in your configuration table), then select "**Edit Add-ons**" : 

<figure><img src="https://1869615683-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MUspPnkTFMlMDdGxvAb-1972196547%2Fuploads%2Fq9IB6DFtXvjHMRVBSJrv%2Fimage.png?alt=media&#x26;token=747dd6a6-1ac6-4d21-83e0-1965cfad0d27" alt=""><figcaption></figcaption></figure>

Move the slider for the "**Activation of Google Consent Mode**" option to the right :&#x20;

<figure><img src="https://1869615683-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MUspPnkTFMlMDdGxvAb-1972196547%2Fuploads%2FUe9lyqstbYshgGsdmgUn%2Fimage.png?alt=media&#x26;token=0a1169b1-bfad-482e-8a1b-b53133211d4a" alt=""><figcaption></figcaption></figure>

Then click on ![](https://1869615683-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MUspPnkTFMlMDdGxvAb-1972196547%2Fuploads%2FJqGsOFadiVkShDgidxpx%2Fimage.png?alt=media\&token=40ecef29-a9c4-47cc-90da-74a2993e5588) at the top right and it's done.

## 2) Configuration of Google Consent Mode

The integration of Consent Mode via this option is a universal integration in which the default signals are:

* *ad\_storage='denied'*
* *analytics\_storage='denied'*
* *functionality\_storage='denied'*
* *personalization\_storage='denied'*
* *security\_storage='denied'*

After the user's consent, an update signal '*granted*' is sent for the concerned signals.

In case of withdrawal of consent, an update signal '*denied*' is sent for the concerned signals.

In all cases, the tags will wait for a choice signal sent by the CMP for 1 second before triggering any potential cookie-based or cookieless pings (command '*wait\_for\_update: 1000*').

{% 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 %}

{% hint style="info" %}
If you wish to manage this default behavior and/or the update behavior differently, refer to the "[Activation via Google Tag Manager](https://cmp.docs.sirdata.net/en/consent-transmission-standards/google-consent-mode/activation-via-google-tag-manager)" section.
{% endhint %}