Microsoft Ads UET Tag & Conversions Not Tracking? (2026)

Roughly 1 in 4 Microsoft Advertising accounts that report "conversions not tracking" in 2026 have a perfectly healthy UET tag and a single, findable break further down the chain — yet most advertisers reinstall the whole tag, which resets data and rarely fixes the real cause. A UET tag marked 'Inactive' is only a problem when real events should be reaching it, so the fix is never "rip it out and start over" by reflex; it is to find the one point between the base tag and the conversion goal where the signal stops.

This guide works forward from the tag through seven failure points — page coverage, traffic, consent, GTM, the tag ID, goal type and validation — so you spend your time on the cause, not the symptom. To check your account against the most common tracking leaks automatically, run our free 5-axis ad account audit.

Updated 2026-05-06 with current UET tag status behavior, Microsoft consent mode and Google Tag Manager container handling observed across US, UK and European accounts.

What is the UET tag and how do conversion goals use it?

The UET tag, short for Universal Event Tracking, is the single piece of JavaScript that Microsoft Advertising uses to see what happens on your site after a click. It is the foundation for everything below it, so understanding what it does — and what it does not do — saves hours of misdirected debugging.

The base UET tag — This is one snippet you place on every page. It loads, assigns the visitor a Microsoft Advertising identifier, and reports a page-load event. On its own it tracks remarketing and page activity, but it does not yet record a conversion.

Conversion goals — A conversion goal is a rule layered on top of the base tag. The goal watches for a specific signal — a destination URL, a custom event, time on site, or pages viewed — and only when that signal matches does Microsoft Advertising count a conversion. The tag is the sensor; the goal is the rule that decides what counts.

Why the split matters — Because the tag and the goal are separate, a healthy tag can coexist with a goal that never fires. Most "conversions not tracking" reports are really goal-definition problems sitting on top of a working tag. For the full setup walkthrough, see our Microsoft Advertising conversion tracking guide.

Why does the UET tag show 'Inactive' or 'No recent activity'?

The 'Inactive' and 'No recent activity' labels alarm advertisers more than they should. Microsoft Advertising sets these states when it has not received an event from the tag within roughly the last 24 hours, and the most frequent cause is mundane: nobody visited the tagged pages.

Low or zero traffic — A brand-new account, a paused campaign, or a low-traffic landing page simply will not feed the tag. Before touching code, confirm real visits arrived in the last day. Roughly 70 percent of 'Inactive' alerts clear on their own once traffic returns.

Fired once, then quiet — A tag that worked during setup but went silent often points to a page that lost its traffic, not a broken snippet. The status reflects the last 24 hours, so a single old event will not keep it 'Active'.

Tag not detected — This is a different message. It means Microsoft Advertising checked a specific URL and found no tag there. That is expected on untagged templates or pages behind a login or consent wall. Confirm which URL was checked before concluding the tag is missing. Our Microsoft Advertising beginner guide covers where the tag belongs.

What are the common causes of a UET tag not firing?

When traffic is healthy but the tag still will not register, the break is almost always one of five specific causes. Working through them in order resolves the large majority of genuine UET failures.

Tag not on every page — A snippet added to one template, or hand-placed on the homepage only, will miss the pages where conversions happen. The base tag belongs on every page of the site, ideally through a single site-wide include.

Consent blocking — A consent management platform that holds scripts until the visitor accepts will stop the UET tag from firing for anyone who declines. This can suppress a large share of events in regions with strict consent prompts.

GTM container misconfig — If you deploy through Google Tag Manager, an unpublished container, a wrong trigger, or a tag set to fire on the wrong event will all break delivery silently. The container can look correct in the workspace yet never be published live.

Wrong tag ID after an import — Bringing campaigns over from Google Ads does not migrate your live tag, and new goals can carry a placeholder or duplicated tag ID. Our Google Ads import guide explains what does and does not transfer.

Are your conversion goals the wrong type?

Once the base tag is firing, a goal that records zero conversions is almost always defined to watch for something your site never actually sends. Microsoft Advertising offers four goal types, and each fails in its own characteristic way.

Destination goals — These fire when the visitor reaches a specific URL, such as a thank-you page. The classic break is a URL mismatch: a trailing slash, a query string, an http-versus-https difference, or a redesigned confirmation path that the goal was never updated to match.

Event goals — These listen for a custom event with a category, action, label or value your code pushes through the tag. If the goal expects an action your site never emits — or the developer changed the event name — the goal stays silent while the tag itself is perfectly healthy.

Duration and Pages-viewed goals — A Duration goal counts a session past a time threshold; a Pages-viewed goal counts sessions past a page count. Set either threshold too high and almost no real session qualifies, so the goal looks broken when it is merely strict. Read the exact condition, then reproduce a realistic session to confirm it can ever trigger.

How do you verify with UET Tag Helper and diagnostics?

Guessing wastes more time than testing. Two tools — the UET Tag Helper browser extension and the status diagnostics inside Microsoft Advertising — let you confirm in minutes whether the tag and goal are truly working.

UET Tag Helper — Install the extension, open a key page, and watch it report the base tag and your tag ID. Then perform the converting action and confirm the goal event fires with the category, action and value you expect. A clean firing here proves the front end is sound.

Dashboard diagnostics — In parallel, open the tag's status in Microsoft Advertising. 'Active' or 'Tag active' confirms recent events reached the server. When the helper shows a firing event and the dashboard shows 'Active', the two signals agree and your measurement is trustworthy.

Reconcile against reality — The final check is a gap test: compare Microsoft Advertising conversions against the orders or leads in your CRM or analytics. If real sales exist but the dashboard shows far fewer, the break is measurement, not performance. To compare measurement quality across platforms, see our Microsoft Advertising versus Google Ads comparison.

How does consent and Microsoft consent mode affect tracking?

Consent is the quietest killer of UET conversions because it suppresses events without any error. A visitor who never accepts cookies never runs the tag, so a clean setup can still under-report badly in consent-strict regions.

The blocking problem — If your consent management platform categorises the UET script as fully blocked until acceptance, every declining or ignoring visitor produces no event at all. In parts of Europe this can hide a substantial fraction of real conversions.

Microsoft consent mode — Microsoft offers a consent signal that lets the tag receive a granted or denied state. With it, consented events count normally and denied states are handled correctly rather than the tag simply going dark. Pass the signal so Microsoft Advertising can measure the consented audience instead of recording nothing.

Practical check — Open your banner settings and confirm the UET script is not hard-blocked, then verify the consent signal reaches the tag in both accept and decline paths. A tag that fires only after acceptance, with no consent signal, is the single most common cause of European under-counting.

Trustworthy consent handling is the foundation for honest numbers — never judge a campaign on data a consent wall has silently halved.

The end-to-end UET fix and validation

Work this table top to bottom — it is ordered by how fast each failure point is to confirm and how often it is the real cause of conversions that will not track.

Once the table points you at the failing row, validate the fix and re-measure before you trust the numbers again. You will usually find one break, not five. The mistake is editing several things at once so you cannot tell what worked, or re-judging conversions before fresh data arrives. Fix in sequence and validate each step.

Confirm the front end first — Use UET Tag Helper to prove the base tag loads with the right tag ID on every key page, then reproduce the converting action and watch the goal event fire. This single test settles most cases in one session.

Then reconcile the back end — Match the dashboard status to the helper, then run the gap test against your CRM. Two agreeing signals plus a closed gap mean the measurement is trustworthy and you can act on the numbers.

Change one thing at a time — Whether it is consent mode, a goal URL, or a tag ID, fix a single point and let it settle. The tag status can flip to 'Active' within minutes, but give conversion counts a day or two of real traffic before drawing conclusions.

Re-measure, then scale. Re-check conversions after each fix, not after all of them, so you know which lever moved the result. Size your return targets before you scale with our ROAS calculator, and to surface every tracking leak automatically, run the SteerAds free 5-axis audit.

Sources

Official sources consulted for this guide:

• help.ads.microsoft.com — about the UET tag

• help.ads.microsoft.com — about conversion tracking

• about.ads.microsoft.com — Microsoft Advertising training

• ads.microsoft.com — Microsoft Advertising

FAQ