Microsoft UET Is Not Optional, Here’s How To Fix Campaigns

If you’ve spent the last year getting Google Consent Mode right, it’s easy to assume Microsoft Ads is covered. But that’s not the case.

Microsoft enforced its own consent requirements on May 5, 2025, and advertisers who missed the deadline are now losing conversion data and remarketing reach for every user in the EEA, UK, and Switzerland who visits their site.

The impact is immediate. Without valid consent signals, Microsoft suspends conversion tracking and remarketing for those users. Unlike Google Consent Mode, Microsoft does not model conversions to fill the gap. So when a user does not consent, that data is simply gone.

If you’re running Microsoft Ads campaigns in these regions and haven’t implemented Microsoft UET consent mode, this article tells you what you need to do and why it matters now.

What Is Microsoft UET Consent Mode?

Universal Event Tracking (UET) is Microsoft Advertising’s tag-based tracking system. When placed on a website, it records user actions such as page visits, purchases, form fills, remarketing audience membership, and custom events. It’s the Microsoft equivalent of the Google Tag or GA4 setup.

UET consent mode is the layer that controls how the UET tag behaves depending on what a user has or hasn’t consented to. Without it, the tag fires regardless of user preference, which creates direct exposure to the EU’s General Data Protection Regulation (GDPR) and ePrivacy requirements for any user in the EEA, UK, or Switzerland.

In most implementations, the user’s choice is collected through a cookie consent banner on the website. UET consent mode then reads that consent signal and adjusts how the tracking tag behaves.

If the user has explicitly agreed to advertising and tracking cookies, the tag collects and processes personal data as normal. If they have not, the tag either sends no data at all (basic mode) or limits signals to anonymized, aggregated information (advanced mode).

Importantly, these requirements are based on where your users are located, not where your business is registered. Any advertiser running Microsoft Ads that receives visitors from the EEA, the UK, or Switzerland needs to account for these consent and privacy obligations.

Microsoft UET consent mode vs. Google Consent Mode

Google Consent Mode v2 and Microsoft UET consent mode are two distinct systems that serve the same regulatory purpose but operate completely independently. Implementing one provides no coverage for the other, and advertisers running both platforms need both frameworks configured separately.

Here are key differences:

The most significant structural difference is modeling. Google uses AI to estimate conversions for users who did not consent, giving advertisers at least partial visibility into performance. Microsoft does not do this. A denied consent means a data gap, with no estimation or recovery on the other side.

This distinction also shapes the stakes of compliance. With Google, a partial rollout still yields some modeled data. With Microsoft, incomplete implementation means incomplete data and nothing to compensate for what is missing.

How does Microsoft UET consent mode work?

At its core, UET consent mode works by reading a user’s consent choice and adjusting what the tag is permitted to collect. The sequence runs as follows:

1. A user visits a website running Microsoft Ads UET
2. A cookie consent banner, served by the CMP, appears before any tags fire
3. The user makes a consent choice: accept, reject, or partially accept
4. The UET tag reads the consent signal through the ad_storage parameter
5. If granted: Full tracking begins; cookies are set, and data is sent to Microsoft Ads for attribution and remarketing.
6. If denied: Anonymized “pings” are sent without setting or reading cookies. Microsoft redacts personal identifiers (PII) and does not use the data for user profiling or interest-based advertising.
7. If the user later changes their consent preferences, UET updates in real time

The ad storage parameter is the single consent signal Microsoft uses. Every UET event includes an asc (ad storage consent) value: G for granted, D for denied. This is a simpler model than Google’s four-parameter framework, which covers ad_storage, analytics_storage, ad_user_data, and ad_personalization. 

However, that simplicity comes without the behavioral modeling component found in Google’s advanced mode. Microsoft uses the signal to determine what it can and cannot collect, relying on the redacted signals for basic aggregate reporting rather than estimating lost conversions through AI.

Microsoft UET basic vs. advanced consent mode

Microsoft offers two implementation modes. In basic mode, no tag activity happens until the user has made a consent decision. The tag does not fire, no cookies are set, and no data is collected until a choice is registered. This is the lower-complexity option and is appropriate for most sites or businesses with straightforward tag setups.

In advanced mode, the UET tag fires immediately on page load but only sends anonymized, aggregated signals until consent is granted. Once the user accepts, full tracking begins. This gives advertisers some continuity of signal flow without requiring a consent decision first, which can be useful for larger advertisers who need to maintain some level of data continuity across the consent interaction.

The distinction that matters most: even in advanced mode, Microsoft does not model or estimate conversions for non-consenting users. Advanced mode is a way to capture partial signals earlier in the user journey, not a mechanism for recovering missing conversion data.

How to implement Microsoft UET consent mode?

There are three paths to implementation, and the right one depends on your existing setup.

Option 1: Via a CMP (recommended)

A consent management platform (CMP) handles consent signal collection and transmission automatically. Once configured, it reads user preferences, generates the appropriate ad_storage signal, and passes it to UET without manual intervention.

1. Connect your CMP to your UET tag through the CMP’s Microsoft Ads integration
2. Configure which tag categories require advertising consent
3. Set your default consent state for users before they interact with the banner
4. Test in a consent-denied state to confirm no UET cookies fire prematurely

This approach works for both basic and advanced modes and requires no custom coding once the integration is in place.

Option 2: Via Google Tag Manager

Microsoft consent mode and Google Tag Manager (GTM) allow you to configure consent settings directly through tag configuration or a CMP-connected variable.

1. In GTM, locate your Microsoft UET tag
2. Enable “Consent Settings” within the tag configuration
3. Set ad_storage as a required consent type
4. Use a CMP that pushes consent state to the GTM data layer, or configure a custom variable to read and pass the consent signal
5. Publish and verify the updated container

Option 3: Via IAB TCF 2.2

If your site already uses the IAB Transparency and Consent Framework (TCF) 2.2, Microsoft UET can read consent signals directly from the TCF string. This is particularly relevant for publishers or sites already running a TCF-compatible CMP.

Verify that your CMP is TCF 2.2-certified and that your Microsoft UET tag is configured to listen for TCF signals rather than requiring separate signal transmission.

Testing your implementation

Once your implementation is set up, it is worth verifying that consent signals are being passed correctly before treating the configuration as complete. Errors at this stage are common, particularly around default consent states and tag firing order, and catching them early avoids ongoing data loss.

• Use the UET Tag Helper browser extension (available for Edge and Chrome) to verify that consent signals are being passed correctly with each UET event
• Check Tools > UET Tag Manager in your Microsoft Advertising account for any compliance warnings
• In a browser with cleared cookies, interact with your consent banner and decline all advertising cookies, then inspect your browser’s cookie storage to confirm that no UET cookies were set in that state

Why did Microsoft make UET consent mode mandatory?

Microsoft’s decision to enforce UET consent mode is driven by several overlapping European regulations. Each framework addresses a different part of the same issue: ensuring that user tracking in digital advertising only happens with freely given, informed consent.

The General Data Protection Regulation

The GDPR treats advertising tracking as a form of personal data processing. Under the GDPR, any processing of personal data must have a valid legal basis. In advertising, that legal basis is usually explicit user consent.

Without a way to capture and pass consent signals, Microsoft cannot legally support activities such as conversion tracking or remarketing for users in the European Union on behalf of advertisers.

The ePrivacy Directive

While the GDPR governs how personal data is processed, the ePrivacy Directive focuses on when tracking is allowed to begin. It requires websites to obtain consent before placing tracking cookies on a user’s device.

This means cookies used for advertising or analytics cannot be set until the user has actively agreed, regardless of what data those cookies collect or how the information will later be used.

Digital Markets Act

The Digital Markets Act (DMA) adds another layer of responsibility. Microsoft is classified as a gatekeeper under this regulation, which places additional obligations on large digital platforms.

Among those obligations is the requirement to ensure that businesses using the platform obtain valid user consent before tracking begins. Enforcing UET consent mode is one way Microsoft ensures advertisers comply with this requirement when using Microsoft Advertising.

Taken together, these regulations establish a consistent principle: advertising tracking requires prior user consent. As regulators increased scrutiny of ad platforms, companies began introducing technical systems to enforce these rules.

The shift unfolded over several stages across the industry, eventually leading to Microsoft’s enforcement timeline:

Microsoft enforcement timeline

July 2023

Microsoft launches UET consent mode

March 6, 2024

Google makes Consent Mode v2 mandatory for advertisers targeting users in the EEA, UK, and Switzerland

March 17, 2025

Microsoft notifies affected advertisers about upcoming enforcement

May 5, 2025

UET consent mode becomes mandatory, with conversion tracking and remarketing disabled for non-compliant websites

What happens if you do not implement UET consent mode Microsoft advertising?

For advertisers who missed the May 5, 2025, deadline, the consequences are already in effect.

• Conversion tracking stops: All purchases, sign-ups, and goal completions from EEA, UK, and Swiss visitors go unmeasured. Reported conversion numbers shrink, and actual performance becomes invisible.
• Remarketing lists stop updating: Without consent signals, universal event tracking consent cannot add new users from affected regions to your audiences. Over time, those lists become stale, and retargeting campaigns lose both reach and relevance.
• Automated bidding degrades: Smart bidding strategies rely on conversion signals to optimize. Without them, Microsoft’s algorithms have less to work with, and campaign performance suffers in ways that are difficult to attribute directly to the compliance gap.
• Accounts get flagged: Microsoft marks non-compliant accounts in the UET Tag Manager dashboard. Repeated violations can escalate to account-level consequences.
• GDPR liability remains yours: If UET cookies fire before consent is granted, your business remains exposed to GDPR risk regardless of Microsoft’s enforcement status. Fines under GDPR can reach €20 million or 4% of global annual turnover, whichever is higher.

Given that Microsoft does not offer conversion modeling as a fallback, when a user declines consent, that conversion signal is lost entirely. This makes non-compliance more consequential for Microsoft Ads than for Google Ads, where modeled conversions at least partially compensate for the data gap. There is no equivalent on the Microsoft side.

How Usercentrics supports Microsoft UET consent mode compliance

Implementing Microsoft UET consent mode involves more than simply adding a cookie consent banner. Websites also need to detect tracking tags correctly, transmit consent signals accurately, and ensure that consent settings remain consistent across different advertising platforms.

This becomes particularly important for organizations using both Microsoft Advertising and Google Ads. Although Microsoft UET consent mode and Google Consent Mode v2 are separate frameworks, they often need to operate in parallel on the same website.

A consent management platform, such as Usercentrics, helps centralize how those consent signals are handled. With a single configuration, the platform can manage consent transmission for both systems, reducing the need to maintain separate implementations or reconcile conflicting settings.

Usercentrics also performs automated website scanning to identify cookies and tracking technologies in use, including UET tags that may have been installed before a consent framework was implemented. This helps ensure that all relevant trackers are accounted for when configuring consent behavior.

Because Microsoft currently does not provide a modeling fallback when consent is missing, the proportion of users who grant consent can directly affect how much conversion data becomes available for campaign measurement and optimization. Features designed to improve consent rate can therefore play an important role, as long as they operate within the limits set by privacy regulations.

Finally, Usercentrics is compatible with Microsoft Clarity as well. This means the same consent management setup can support both Microsoft Advertising tracking and Clarity analytics on a single site.

Eike Paulat

VP of Product Strategy, Usercentrics GmbH

Read bio

Stay in the loop

Join our growing community of data privacy enthusiasts now. Subscribe to the Usercentrics newsletter and get the latest updates right in your inbox.

Subscribe

Email address

Subscribe

By subscribing to the Usercentrics Newsletter, you agree that your data may be used for information related to the products and services offered by Usercentrics. You can revoke your consent by using the unsubscribe link in a newsletter email or by sending your request to unsubscribe@usercentrics.com. See Privacy Policy