Microsoft Consent Mode (UET)
Enabling Microsoft Consent Mode in Gravito CMP (New)
Gravito CMP (New) supports two ways to enable Microsoft's Universal Consent Mode:
1. Using Configurator
- Login to the Gravito Admin Portal.
- Click on the CMP tab.
- Select the Gravito CMP (New) Configurator from the option.
- On the CMP Config listing page, click the New Configuration button to create a new CMP config.
-
Give config an appropriate name and choose Standard CMP as Framework. After that, click Get Started to proceed.
-
Now navigate to Standard CMP tab and Consent Categories sub-tab for UET related setup.
- You can enable UET by checking the checkbox labeled Microsoft's Universal Event Tracking (UET).
- After enabling UET, an additional field will appear for configuration.
Consent Mapping:
You’ll now see dropdowns to map category for : ad_storage
Select the relevant consent category from the dropdown list.
Note: This mapping is for the ad_storage
signal only is common across both GCMv2 & UET.
Once mapping is complete, click Save Progress at the top-right. Now you have successfully enabled Microsoft UET Consent Mode in your CMP configuration.
You may continue filling out the other CMP configuration steps, or jump directly to the Deployment tab.
2. Without Configurator
-
Enable UET Mode:
Add theuseUET
flag under thegravito.config.cmp.standard.core
section of your configuration and set its value totrue
.window.gravito = { config: { cmp: { standard: { core: { useUET: true, // ... other configurations } } } } };
-
Add
adsConsentId
You must also define the
adsConsentId
property in your configuration. This is required to map consent values for Microsoft UET. There are two cases:-
If Google Consent Mode is already configured:
The
adsConsentId
property will already be available in your config. -
If not configured:
Add the
adsConsentId
property under thegravito.config.cmp.standard.core
section of your config manually.
-
-
Define
adsConsentId
Based on CMP TypeThe
adsConsentId
should be a single ID referring to the custom consent item that you have defined in the config. It is not an array of TCF purpose IDs in this case.Example:
window.gravito = { config: { cmp: { standard: { core: { useUET: true, adsConsentId: "{{YOUR_CONSENT_ITEM_ID}}", // Replace with your consent item ID } } } } };
This means the consent value of the item with ID
"{{YOUR_CONSENT_ITEM_ID}}"
will be used for Microsoft UET. -
How Gravito CMP Handles UET Consent
Once the above configuration is complete:
- Microsoft UET mode is considered enabled.
- Gravito CMP adds the corresponding ads consent value (
denied
orgranted
) to the globaluetq
window object. - By default, the value is
denied
. - After consent is obtained, the CMP updates the value based on the mapping defined in
adsConsentId
.
Microsoft reads this value from the
uetq
object to determine whether tracking is allowed.Gravito CMP's follow the approach mentioned Here