1. Purpose of this specification
This specification describes de changes and instruction to implement Google Consent Mode v2
2. Google Consent Mode description
Consent mode lets you communicate your users’ cookie or app identifier consent status to Google. Tags adjust their behaviour and respect users’ choices.
Consent mode interacts with your Consent Management Platform (CMP) or custom implementation for obtaining visitor consent, such as a cookie consent banner. Consent mode receives your users' consent choices from your cookie banner or widget and dynamically adapts the behaviour of Analytics, Ads, and third-party tags that create or read cookies.
When visitors deny consent, instead of storing cookies, tags send pings to Google.
3. Google Consent Mode v1 in SIBBO CMP
3.1 Description
SIBBO CMP has Preintegrated the Google Consent Mode scripts. Version 1 of Google Consent Mode is included in the CORE file of SIBBO CMP.
3.2 Configuration
In order to activate the Google consent mode it is necessary to include the GTA account number of the client in SIBBO CMP CORE:
tagManager: 'GT-XXXXX'
Google do not define official equivalences from TCF to Google Consent Mode.
SIBBO has establish the following default equivalences:
Version | Consent Type | Description | Values | STANDARD SET UP |
V1 | ad_storage | Enables storage (such as cookies) related to advertising. | 'granted' | 'denied' | 1,2 |
V1 | analytics_storage | Enables storage (such as cookies) related to analytics e.g. visit duration. | 'granted' | 'denied' | 1,9 |
V1 | functionality_storage | Enables storage that supports the functionality of the website or app e.g. language settings. | 'granted' | 'denied' | 1,11 |
V1 | personalization_storage | Enables storage related to personalization e.g. video recommendations | 'granted' | 'denied' | 1,5,6,8,9,10,11 |
V1 | security_storage | Enables storage related to security such as authentication functionality, fraud prevention, and other user protection. | 'granted' | 'denied' | Availability of TCString
|
3.3 Output in GTM
All Consent types are defined as ‘denied’ by default.
The CMP fires the Google consent mode script once there is a TCstring available
All Consent types except security_storage require that vendor = 755 has been accepted by the user before checking the equivalences established between TCF and Google consent mode and enable / disable each Consent Type accordingly.
Version | Consent Type | Output Values |
V1 | ad_storage | 'granted' | 'denied' |
V1 | analytics_storage | 'granted' | 'denied' |
V1 | functionality_storage | 'granted' | 'denied' |
V1 | personalization_storage | 'granted' | 'denied' |
V1 | security_storage | 'granted' | 'denied'
|
4. Google Consent Mode v2 in SIBBO CMP
4.1 Description
SIBBO CMP has Preintegrated the Google Consent Mode scripts, so they can be activated on CMP configuration. Version 2 of Google Consent Mode is included in the CORE file of SIBBO CMP, and configured in the CONFIGURATION file.
Configuration allows:
• to activate / deactivate
• reconfigure the equivalences between TCF v2,2 and Google Consent Mode v2.
• Includes v2 parameters (ad_user_data, ad_personalisation)
4.2 Configuration
4.2.1 Google consent mode activation and link to customer Analytics
In order to activate the Google consent mode it is necessary to include the GTA account number of the client in SIBBO CMP CONFIGURATION:
tagManager: 'GT-XXXXX'
TCF establish several purposes, features, special purposes and special features. On top of that it is possible to define for which vendors the consent is gathered from the user.
Google do not define official equivalences from TCF to Google Consent Mode. SIBBO has establish default equivalences, however, it is on the Publisher side to decide which equivalences define for its business case.
Here are the default equivalences:
Version | Consent Type | Description | Output Values | STANDARD SET UP |
V1, V2 | ad_storage | Enables storage (such as cookies) related to advertising. | 'granted' | 'denied' | 1,2 |
V1, V2 | analytics_storage | Enables storage (such as cookies) related to analytics e.g. visit duration. | 'granted' | 'denied' | 1,9 |
V1, V2 | functionality_storage | Enables storage that supports the functionality of the website or app e.g. language settings. | 'granted' | 'denied' | 1,11 |
V1, V2 | personalization_storage | Enables storage related to personalization e.g. video recommendations | 'granted' | 'denied' | 1,5,6,8,9,10,11 |
V1, V2 | security_storage | Enables storage related to security such as authentication functionality, fraud prevention, and other user protection. | 'granted' | 'denied' | Availability of TCString |
V2 | ad_user_data | Establishes consent to send advertising-related user data to Google. | 'granted' | 'denied' | 1,2,3,4,7,9,10 |
V2 | ad_personalization | Establish consent for personalized advertising. | 'granted' | 'denied' | 1,2,3,4,7,9,10
|
In the Sibbo Configuration It is possible to write a different equivalences (if this parameters are empty, it will take the default values established above)
securityStoragePurposes: [It is not customizable. Check if there is a consent string],
Configurable parameter (each [] should be filled with the array of purposes to consider):
functionalityStoragePurposes: [],
analyticsStoragePurposes: [],
adStoragePurposes: [],
personalizationStoragePurposes: [],
adUserDataPurposes: [],
adPersonalizationPurposes: [],
4.3 Output
All Consent types are defined as ‘denied’ by default.
The CMP fires the Google consent mode script as soon as the page is loaded. If there is no TCstring available, all Consent types will be defined as 'denied'
All Consent types except security_storage require that vendor = 755 has been accepted by the user before checking the equivalences established between TCF and Google consent mode and enable / disable each Consent Type accordingly.
Version | Consent Type | Output Values |
V1, V2 | ad_storage | 'granted' | 'denied' |
V1, V2 | analytics_storage | 'granted' | 'denied' |
V1, V2 | functionality_storage | 'granted' | 'denied' |
V1, V2 | personalization_storage | 'granted' | 'denied' |
V1, V2 | security_storage | 'granted' | 'denied' |
V2 | ad_user_data | 'granted' | 'denied' |
V2 | ad_personalization | 'granted' | 'denied' |