Microsoft UET
Microsoft Advertising's Universal Event Tracking (UET) Consent Mode takes a single binary signal that tells Microsoft tags whether they may store advertising identifiers. OptSens sets that signal automatically.
What OptSens does on the wire
UET Consent Mode has no granular categories. It reads one value, ad_storage,
which OptSens maps from the visitor's advertising consent.
OptSens pushes the default to the window.uetq queue before any Microsoft tag
runs, then pushes an update after the visitor acts:
| Stage | Call | Value |
|---|---|---|
| Default | uetq.push('consent', 'default', ...) | ad_storage: 'denied' |
| Advertising granted | uetq.push('consent', 'update', ...) | ad_storage: 'granted' |
| Advertising denied | uetq.push('consent', 'update', ...) | ad_storage: 'denied' |
How to enable it
Microsoft UET requires a Plus plan or higher.
- Open the dashboard and select your domain.
- Go to Frameworks.
- Toggle Microsoft UET.
- Save.
If you run Microsoft Ads campaigns that reach European visitors, enable this toggle. OptSens always pushes the denied default before any tag runs, and only the toggle delivers the granted update after consent. With Microsoft tags on the page and the toggle off, those tags stay denied.
How to verify it
Open your site and inspect the queue in the browser console:
console.log(window.uetq);
The entries appear as consecutive items: 'consent', 'default',
{ad_storage: 'denied'} at load, then 'consent', 'update' and the
granted or denied object after you accept or reject advertising in the
banner.
Check before the Microsoft tag loads. Once bat.js runs, it consumes the
queue and replaces window.uetq with its own object. On a live Microsoft
Ads site, Microsoft's UET Tag Helper browser extension shows the received
consent state.