Microsoft requires advertisers targeting users in the EEA, UK, and Switzerland to send user consent signals to Microsoft Advertising.
UET Consent Mode lets you adjust UET cookie access based on the consent status of your users. This enhances the privacy capabilities of UET and gives you control over whether first and third-party cookies are stored.
For the purposes of UET consent mode, first-party cookies are those created by the advertiser domain (your website), and third-party cookies are created by Microsoft Advertising (Bing.com).
How it works
Consent mode is set via a property in UET called ad_storage. The possible values for ad_storage are:
| ad_storage value | What it means | Cookie behavior |
|---|---|---|
| granted | User has given consent for advertising cookies. | Loads immediately with consent state set to denied by default before user makes a choice |
| denied | User has not given consent for advertising cookies. | First-party cookies are not read or written. Third-party cookies are not written. They may only be read for fraud and spam prevention, not for advertising purposes. |
Basic or Advanced Consent Mode
Microsoft’s official guidance describes two implementation approaches: Basic and Advanced Consent Mode
Basic Consent Mode: ensures that no tags are fired and no data collection occurs until a user explicitly grants consent.
Advanced Consent Mode: enables UET tags to load immediately, and since consent status defaults to denied, anonymized data is collected until explicit consent is granted. If consent is denied, only anonymized data is collected and later aggregated prior to modeling.
Recommendation: Microsoft Advertising recommends Advanced Consent Mode as the best practice to balance compliance and measurement.
| Attribute | Basic Consent Mode | Advanced Consent Mode |
|---|---|---|
| Tag Loading | Blocked until the user grants consent |
Loads immediately with consent state set to denied by default before user makes a choice |
| Data Collection | No data is sent before a user grants consent | If consent is denied, only anonymized data is collected and later aggregated prior to modeling |
| Consent Status | Set after user grants consent | Defaults to denied before user makes a choice, updates based on user choice |
| Data Modeling | Generic modeling | More precise modeling tailored to the advertiser |
If no default ad_storage value is set, Microsoft UET will assume granted by default, which is not compliant with privacy regulations. Therefore, an explicit default of denied must always be set before user consent is obtained.
Set up for Consent Mode
Cookiebot CMP has built-in support for UET.
Once consent information is available, it’s automatically passed to UET using the existing global window.uetq property.
The following example is for Advanced Consent Mode.
- UET tag loads right away.
- Default is set to
denied. - If the user accepts, you update to
granted.
This means that you don’t have to take any further steps on your part to enable consent updates, they will be passed automatically if the window.uetq global object exists.
If you don’t want Cookiebot CMP to pass consent data to Microsoft UET you can disable this functionality using the data-ms-consent-mode="disabled" data-attribute or the msConsentMode=disabled URL parameter.
For example:
or:
<script
id="Cookiebot"
type="text/javascript"
src="https://consent.cookiebot.com/uc.js?msConsentMode=disabled"
data-cbid="00000000-0000-0000-0000-000000000000"
data-blockingmode="auto"
></script>
For Basic Consent Mode, fire your UET tag where consent is granted
- Use the following code on each page to update the ad_storage property:
<script>
window.uetq = window.uetq || [];
window.uetq.push('consent', 'update', {
'ad_storage': 'granted'
});
</script>- If you use Consent Mode, you should continue to pass either a granted or denied value for ad_storage on every page based on your website visitors' cookie consent choices.
- For most countries, if the consent setting is not set, UET uses granted by default.
- In European Economic Area countries, along with the UK and Switzerland, Microsoft Advertising is enforcing Consent Mode. This will lead to conversion loss if the granted signal is not passed to UET when a user accepts consent. In scenarios where Consent Mode is enforced, the default value is denied.
Comments
1 comment
Thank you for this detailed guide! The step-by-step instructions on configuring Additional Consent Settings and replacing triggers are incredibly helpful, especially for ensuring compliance without losing valuable data. The explanation of the 'cookie_consent_update' custom event trigger was particularly insightful. Much appreciated!
Please sign in to leave a comment.