Usercentrics and Google Consent Mode storage types
Usercentrics CMP uses service level consent and that’s “hard” to link to the
...
GCM storage types, as you may have ambiguous DPS consents.
That’s why Usercentrics currently
...
supports a strict way of, a storage type only gets granted if all of the services that are used (and linked to that type - currently a list of hardcoded predefined DPS) have consent.
The relevant list of Google DPS can be found in the Google Consent Mode tech doc.
Categories are “just “ a visual grouping bulk toggling of individual Data Processing Services (DPS) but still the above described behavior applies.
In the Admin Interface, it is necessary to include the services are included along with their corresponding consent types to ensure the consent mode type is "granted" or "denied" based on the user user’s choices.
Based on our predefined Predefined Data Processing Services (DPS) we have a direct service -consent type → GCM storage type consent state correlation, you can find this in our docs:
...
| Code Block |
|---|
Data Processing Service |TempleTemplate ID | CoMo type | Google Analytics 4 | 87JYasXPF | analytics_storage | Google Ads Conversion Tracking | twMyStLkn | ad_storage | Google Ads Remarketing | B1Hk_zoTX | ad_storage ... |
| Info |
|---|
Default behavior:
|
...
|