Microsoft UET Consent Mode: practical guide for marketers

Summary

If you run Microsoft Advertising (Bing) and you have the UET tag on your site, Microsoft’s “consent mode” lets the tag adapt to a user’s consent choices.

• It does not automatically make you compliant.
• It can reduce the risk of collecting or reading marketing identifiers before the user opts in.
• It may preserve some measurement signal (in a consent-respecting way) compared to blocking the tag entirely.

What is UET?

UET (Universal Event Tracking) is Microsoft Advertising’s site tag. It powers conversion tracking, remarketing/audience building, and campaign measurement.

If you have ever “installed the Microsoft Ads tag”, there is a good chance you installed UET.

What “consent mode” means in practice

In practice, “consent mode” usually means:

1. Your site sets a default consent state (often deny for marketing) before any user interaction.
2. When the user accepts or rejects consent in your banner, the site updates that state.
3. The UET tag reads that signal and changes its behaviour (for example, whether it can write or read certain identifiers).

The exact behaviour depends on Microsoft’s implementation and policies, but the intent is consistent: tags should behave differently when consent is denied.

What happens if you do not implement it

Marketers usually see one (or more) of these outcomes:

1) Compliance risk

If UET runs normally before consent, you may be setting or reading marketing cookies/identifiers before opt-in (depending on your setup and jurisdiction). That is the kind of behaviour regulators and internal privacy reviews tend to focus on.

2) Measurement and data quality issues

If you instead block Microsoft tags until consent, you can end up with:

• under-attributed conversions
• volatile performance numbers
• inconsistent reporting between platforms

Consent mode is often positioned as a middle path: respect the user’s choice while still allowing some level of measurement where permitted.

3) Operational complexity

Without a clear consent signal, teams often create complicated rules:

• multiple tag-manager containers
• fragile trigger logic
• inconsistent behaviour between environments

A single, consistent consent signal from your banner (via your CMP) tends to simplify this.

How to implement

This is a marketer-friendly flow that works for most sites.

Step 1: Confirm you actually have UET

Look for any of the following:

• Your agency or dev team says “Microsoft Ads tag” or “UET tag”
• You see Microsoft Advertising in your tag manager
• ConsentScout (or another scanner) shows Microsoft-related cookies or requests on first load

If you are not running Microsoft Ads, you can stop here.

Step 2: Decide your default

For most UK/EU opt-in banners, a sensible default is:

• Marketing / advertising: denied by default
• only switch to granted after explicit opt-in

Your legal and policy position may vary, but the key is to choose a default and implement it consistently.

Step 3: Use your Consent Management Platform (CMP) to send consent signals

Most mainstream Consent Management Platforms (CMPs) can pass consent states to multiple vendors (Google, Microsoft, Meta, and others). What you want is:

• Microsoft advertising/remarketing mapped to your “Marketing” category
• the consent signal updated when the user changes their choice
• a clear “deny” signal on first load if the user has not consented

If your CMP has a “Microsoft UET consent mode” or “Microsoft Advertising integration” toggle, start there.

Step 4: Validate (quick QA)

Do two simple tests in an incognito/private window:

1. Before interacting with the banner

   • You should not see marketing cookies being dropped immediately.
   • If Microsoft requests fire, they should reflect the default denied state.

2. After opting in to Marketing

   • Microsoft Advertising tracking should behave as expected for conversions and remarketing.

If your CMP has a built-in debug view, use it. If not, ask your dev team to confirm with a quick check.

Step 5: Document it

Write down:

• which CMP category maps to Microsoft Ads
• what your default is
• how to test it

Six months from now, you will be glad you did.

Where ConsentScout fits

ConsentScout’s first-load scan is a good quick check for whether non-required cookies appear before consent.

If your scan shows Microsoft/marketing cookies set on first load, that is a strong hint:

• your default consent is not being applied, or
• the tag is not wired into your CMP correctly.

Consent mode can still involve network requests in some configurations. The key question is whether non-required storage happens before consent.