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_storageare:
Value for ad_storage |
Description |
|---|---|
| granted | First and third-party cookies may be read and written for UET. If no default is set, UET uses granted by default. |
| denied | First-party cookies are not read nor written for UET. Third-party cookies are not written. Third-party cookies are read-only for fraud and spam purposes—not for advertising purposes. |
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.
This means that you don't have to take any steps on your part to enable this feature, it'll be enabled by default 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:
<script
id="Cookiebot"
type="text/javascript"
src="https://consent.cookiebot.com/uc.js"
data-cbid="00000000-0000-0000-0000-000000000000"
data-blockingmode="auto"
data-ms-consent-mode="disabled"
></script>
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>
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.