Is support planned for UET consent mode
Is support planned for UET consent mode similar to Google consent mode?
MS/Bing have started emailing regarding enforcing consent mode/signals on EEA + Swiss + UK customers.
Docs: https://help.ads.microsoft.com/apex/index/3/en/60119
Microsoft's email does not give a timeframe, it just says "Soon"
5 Replies
Unknown User•17mo ago
Message Not Public
Sign In & Join Server To View
Following.... Since we setup Microsoft Ads, they are bugging me for correct handling of consent.... I try to setup UET in a custom action but I don't know if it's suppose to be setup this way.
<script>
var ClarityConsentBln = zaraz.consent.get('tFYh');
var MSadsConsent = 'denied';
window.uetq = window.uetq [];
window.uetq.push('consent', 'default', {
'ad_storage': MSadsConsent
});
if(ClarityConsentBln) {
window.clarity("consent");
MSadsConsent = 'granted';
};
window.uetq = window.uetq []; window.uetq.push('consent', 'update', { 'ad_storage': MSadsConsent
}); </script>
window.uetq = window.uetq []; window.uetq.push('consent', 'update', { 'ad_storage': MSadsConsent
}); </script>
Hey, I am not positive this works, if you are still having an issue with consent mode with UET this is what I did, I am not entirely positive that MS sees consent mode as "on", although it hasn't warned me about it for a few weeks.
You can review the Cloudflare Bing UET script here: https://github.com/managed-components/bing/blob/main/src/index.ts
Our setup:
We have UET disabled until the customer has provided consent, While UET does support "advanced" consent mode, its easier to implement basic consent mode in this way for now.
We have disabled the standard MS UET tool in Cloudflare and instead enabled a Custom Managed Component.
The Custom Managed Component has the Bing UET managed component loaded into it without any modifications, script located here: https://github.com/managed-components/bing
We then add a custom field with the key "asc" and the value "G"
The only purpose for loading the Bing component as a custom component is to enable the ability to add custom fields, this functionality isnt available on the Cloudflare provided MS UET tool.
This adds the correct consent flag to the requests to bing services.
Initially we thought the parameter should be "Granted" as this is what is shown in the Bing UET helper extension when you inspect the Bing tag, however further investigation indicated that it should be "G" and "Granted" is not accepted.
As mentioned above this only works if you block UET loading until after customer has provided consent. I am not sure its possible to make it work in advanced mode without modifying the script as you would need to prevent the use of the Bing Click ID until the customer has provided consent. The Bing Click ID is handled on lines 107 to 137 in the script.
When you load the Bing UET as a custom managed component you will lose the well named parameters in the config.
However the readme tells you exactly what you should provide
ti: UET Tag ID, should be set on the main tool settings page where you also add the "asc" custom field.
ea: Event Action, set on the conversion event
ec: Event Category,, set on the conversion event
ev: Event Value, set on the conversion event
el: Event Label, set on the conversion event
gv: Revenue Value, set on the conversion event
gc: Currency, set on the conversion event
We have them configured as shown on the attached image
Wow! Thanks a lot! I will give it a try tomorrow… 👍