Mirror CookieShift consent to Microsoft Advertising UET when the UET tag is installed.
CookieShift pushes Microsoft UET Consent Mode signals when window.uetq is present on the page. No separate dashboard toggle is required.
Overview
Microsoft Advertising uses a UET (Universal Event Tracking) queue (uetq) on your site. When visitors change consent, CookieShift calls uetq.push('consent', 'update', …) with ad_storage, ad_personalization, and analytics_storage mapped from your banner categories.
Why it matters
UET tags can fire before consent without proper ordering. Loading CookieShift before UET ensures consent defaults apply before Microsoft records events in regulated regions.
Setup
- Install cmp.js early in
<head>(see Installation). - Add your Microsoft UET base tag after cmp.js.
- Open Consent Setup → Microsoft UET and follow the validation checklist.
- Test in a private window: reject marketing, then accept — confirm consent updates in the browser console or network tab.
Examples
| Visitor choice | UET signal |
|---|---|
| Reject marketing | ad_storage and ad_personalization denied |
| Accept analytics only | analytics_storage granted, ads denied |
| Accept all | All three granted |
Troubleshooting
- UET fires before consent — Move cmp.js above the UET snippet; clear cache.
- No consent update — Confirm
window.uetqexists; ad blockers may block UET. - Mismatch with Google — Google Consent Mode and UET are independent; configure both under Consent Setup.
Best practices
- Keep script order documented for developers and agencies.
- Pair with Google Consent Mode v2 when running Google and Microsoft ads together.
- Re-test after every banner or category change.