Understanding How Usercentrics and Consent Mode Operate

Usercentrics and Consent Mode types

Usercentrics CMP uses service level consent and that’s “hard” to link to the consent mode types as you may have ambiguous DPS consents.
That’s why Usercentrics currently support 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.
Categories are “just “ a visual grouping bulk toogling of individual Data Processing Services but still the above 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 choices

Based on our predefined Data Processing Services (DPS) we have a direct service-consent type correlation, you can find this in our docs:

e.g.

Data Processing Service          |Temple 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.