Are your Microsoft Ad campaigns suddenly showing zero conversions? Have you noticed remarketing audiences shrinking without explanation? The problem is likely broken or missing consent signals on your UET tag.
Since May 2025, Microsoft requires valid user consent signals for all campaigns targeting the EEA, UK, and Switzerland. Without them, conversion tracking stops, remarketing breaks, and campaign performance drops sharply.
This guide walks you through exactly how to fix Microsoft consent signals. You will learn how to diagnose the issue, configure your UET tag, connect your consent management platform, and verify that everything works correctly.
Microsoft consent signals tell the UET tag whether a visitor has agreed to ad tracking and data storage. Here is what you need to know about how they work and why they matter.
When a user lands on your site, the UET tag checks for a consent state. This state has two key parameters: ad_storage and ad_user_data. Both must be set to “granted” for full conversion tracking.
If either value is “denied” or missing, UET operates in cookieless mode. It still fires, but it cannot store cookies, build remarketing lists, or attribute conversions accurately.
The enforcement aligns with GDPR requirements across the EEA, UK, and Switzerland. Microsoft cannot process personal ad data without proof of user consent. Unlike Google, Microsoft does not model missing conversions. So when consent signals break, that data is permanently lost.
Your Ad campaigns keep running, but UET stops recording conversions. Remarketing audiences stop growing. Smart bidding strategies lose their data feed, and performance declines. Your ad spend continues, but you cannot measure results.
Before you fix anything, confirm whether consent signals are actually broken or just misconfigured. These three checks will tell you exactly where the problem is.
Install the UET Tag Helper extension for Chrome or Edge. Visit your website, click the extension icon, and look for a green tick. If the tick appears, the tag fires correctly.
Next, go to Events > Parameter details and find the Consent State (asc) parameter. Before a user accepts cookies, it should show “D” for denied. After consent, it should switch to “G” for granted.
Open your browser developer tools and navigate to the Network tab. Filter by “bat.bing” to find UET requests. Check the request URL for the “asc” parameter. If it is missing entirely, your CMP is not passing signals to UET.
Log in to Microsoft Advertising and check for notifications about consent signal compliance. Microsoft flags accounts that run EEA or UK campaigns without valid signals. If you see a warning, your setup needs attention.
Google Tag Manager is the most common setup for UET tags. Here is how to configure consent signals correctly using GTM.
Follow the steps below to update to the official template:
The official template has built-in consent mode support. It automatically reads the consent state and passes it to Microsoft.
Inside your UET tag settings, scroll to the Consent Settings section. Set ad_storage and ad_user_data as required consent checks. This ensures the tag only fires with full tracking when the user grants both permissions.
When a user clicks “Accept” on your cookie banner, a consent update event must fire. In GTM, check that your consent management platform triggers a consent update push to the data layer. Without this update, UET stays in denied mode permanently for that session.
If you do not use GTM, you can pass consent signals directly through JavaScript. This method gives you full control over when and how signals reach the UET tag.
Add the following consent initialisation before your UET tag script loads. Set both ad_storage and ad_user_data to “denied” as the default. This ensures the tag starts in privacy-safe mode before the user makes a choice.
Use the window.uetq push method with the “consent” action and “default” command type. Pass the two parameters as “denied” in a configuration object.
Once the user accepts tracking through your cookie banner, push a consent update. Change both values from “denied” to “granted” using the “update” command type. This tells UET it can now store cookies and track conversions for that visitor.
Your consent default must load before the UET tag script. The consent update must fire after the user interacts with the banner. If the order is wrong, UET either misses the default state or never receives the update. Test this flow on every page of your site.
Your consent management platform handles user choices. It must correctly relay those choices to UET. Here is how to ensure that the connection works.
Not all CMPs integrate natively with Microsoft UET. Confirm that yours supports Microsoft’s consent framework. A CMP like Seers.ai supports both Google Consent Mode v2 and Microsoft UET consent mode, which simplifies setup across multiple ad platforms.
Some CMPs block all marketing tags until consent is granted. This is a common cause of broken consent signals. UET needs to load on every page, even before consent. It should start in denied mode and switch to granted mode after user approval.
If your CMP prevents UET from loading at all, advanced consent mode cannot work. Adjust your CMP settings to allow UET to fire on page load with a default denied state.
Microsoft requires two specific consent signals: ad_storage and ad_user_data. Your CMP must map its cookie categories to these exact parameters. If your CMP uses different labels like “marketing” or “analytics,” make sure those labels translate correctly into Microsoft’s required format.
Microsoft introduced advanced consent mode in early 2026. It offers a middle ground between full tracking and completely blocked measurement. Here is what it means for your setup.
When a user denies consent, advanced consent mode still allows UET to collect cookieless, anonymised pings. These pings cannot identify individual users. But they help Microsoft model conversion behaviour at an aggregate level.
If you use the official GTM template, advanced consent mode activates automatically when cookie consent defaults are set to denied. For manual implementations, ensure your default consent push uses the correct parameters. Microsoft’s documentation confirms that no additional code changes are needed beyond standard consent mode setup.
Advanced consent mode does not fully replace granted consent. Conversion modelling fills some gaps, but remarketing still requires explicit consent. Smart bidding algorithms work better with full data. Treat advanced consent mode as a safety net, not a complete solution.
Even after setup, things can go wrong. Here are the most frequent issues and how to resolve each one quickly.
This means the consent update event is not firing. Check your CMP’s callback function or GTM trigger. The update push must happen immediately after the user clicks the accept button. Test with UET Tag Helper to confirm the asc parameter changes from D to G.
container or manual script is present in the page source. Check for JavaScript errors in the console that might block execution. Ensure the tag fires on all pages, not just specific ones.
Allow 24 to 48 hours for Microsoft to process changes. If conversions remain missing, check that your conversion goals are correctly mapped to UET events. Also, verify that the cookie banner actually triggers the consent update and does not just close visually.
After making changes, run a complete verification. This checklist ensures every part of your consent signal setup functions as expected.
If all seven steps pass, your Microsoft consent signals are working correctly. Monitor your conversion reports weekly to catch any future issues early.
Fixing Microsoft consent signals is not optional if you run campaigns in the EEA, UK, or Switzerland. Broken signals mean lost conversions, wasted spend, and potential GDPR penalties. The fix requires setting correct default states, ensuring your CMP passes updates to UET, and verifying every step with the Tag Helper. Follow this guide once, monitor regularly, and your conversion data stays intact.
Seers handles Microsoft UET consent mode and passes the accurate consent signals by enabling the consent mode with just a single click. Your consent signals stay accurate, your Ad campaigns keep tracking, and your compliance stays up to date. Stop losing conversions to broken consent.
START FREE TODAYMicrosoft consent signals are parameters passed through the UET tag that tell Microsoft whether a website visitor has agreed to ad tracking and data storage. The two key signals are ad_storage and ad_user_data. Both must show “granted” for full conversion tracking and remarketing to function in EEA, UK, and Swiss campaigns.
If your campaigns target the EEA, UK, or Switzerland, missing or broken consent signals are the most likely cause. Since May 2025, Microsoft requires valid consent before recording conversions. Without properly configured signals, UET operates in cookieless mode and cannot attribute conversions to your campaigns, even though the tag still fires.
The consent framework is similar but not identical. Both platforms use ad_storage and ad_user_data parameters. However, Microsoft UET reads consent through its own mechanism. If your CMP supports both Google Consent Mode v2 and Microsoft UET consent mode, you can manage both from a single configuration without duplicating your setup.
Once you fix your consent signal setup, allow 24 to 48 hours for Microsoft Advertising to process and display conversion data. During this window, UET begins recording events with the corrected consent state. If conversions still do not appear after 48 hours, re-check your configuration using the UET Tag Helper extension.
With standard consent mode, Microsoft does not model conversions for denied users. That data is permanently lost. However, with the advanced consent mode introduced in 2026, Microsoft can collect anonymised cookieless pings to model aggregate conversion behaviour. This partially fills the measurement gap but does not replace full granted consent.
The asc parameter stands for Advertising Consent State. It appears in UET network requests and the UET Tag Helper extension. A value of “D” means consent is denied. A value of “G” means consent is granted. Checking this parameter is the quickest way to confirm whether your consent signals pass correctly to Microsoft.
Currently, Microsoft only enforces consent signals for campaigns targeting the EEA, UK, and Switzerland. Campaigns targeting other regions do not require consent signals for conversion tracking. However, implementing consent signals globally is recommended as privacy regulations expand and enforcement tightens in other markets.
No. Blocking UET entirely prevents consent mode from working. The tag must load on every page in a default denied state. When the user grants consent, the tag updates to granted mode. If your CMP blocks the tag before any consent decision, advanced consent mode cannot function, and you lose all measurement for non-consenting users.
Yes. You can implement consent signals manually using JavaScript. Push a default denied state before the UET tag loads, then push an update to granted after the user accepts tracking. However, managing consent without a CMP means you handle cookie scanning, banner display, preference storage, and regulatory updates entirely on your own.
Rimsha ZafarRimsha is a Senior Content Writer at Seers AI with over 5 years of experience in advanced technologies and AI-driven tools. Her expertise as a research analyst shapes clear, thoughtful insights into responsible data use, trust, and future-facing technologies.
Take our Free Cookie Audit and find out
Join 50,000+ websites using Seers.Ai to turn compliance into trust, insights, & measurable business growth.
United Kingdom
24 Holborn Viaduct
London, EC1A 2BN
Get our monthly newsletter with insightful blogs and industry news
By clicking “Subcribe” I agree Terms and Conditions
Seers Group © 2026 All Rights Reserved
Terms of use | Privacy policy | Cookie Policy | Sitemap | Do Not Sell or Share My Personal Information.
