Understanding how the Usercentrics CMP and GCM operate

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, the services are included along with their corresponding consent types to ensure the consent mode type is "granted" or "denied" based on the user’s choices.

Based on our Predefined Data Processing Services (DPS) we have a direct service → GCM storage type consent state correlation, you can find this in our docs:

e.g.

Data Processing Service          |Template ID    | CoMo type 
| Google Analytics 4             | 87JYasXPF   | analytics_storage 
| Google Ads Conversion Tracking | twMyStLkn   | ad_storage        
| Google Ads Remarketing         | B1Hk_zoTX   | ad_storage       
...

Default behavior:

Consent for Google Analytics 4 - 87JYasXPF activates analytics_storage
Consent for all DPS belonging to ad_storage is activating ad_storage, ad_user_data and ad_personalization

Explore further

Differences between Advanced & Basic GCM v2