How Microsoft Ads conversion tracking works

What the UET tag actually is#

Universal Event Tracking is Microsoft Advertising's single snippet of JavaScript, and the entire measurement stack hangs off it. Microsoft's own framing is worth quoting: UET is a prerequisite for conversion tracking, remarketing in paid search, and automated bidding. No tag, no numbers, no bidding brain.

You create the tag once in the platform, then paste it into the head or body of every page. As pages load, the tag fires requests to bat.bing.com, and those requests are how Microsoft knows someone visited your site. Microsoft documents the full mechanics in its Universal Event Tracking technical guide, including the single-page application behaviour: modern tags ship with enableAutoSpaTracking on by default, which is what keeps tracking alive on sites where nothing ever actually reloads.

Conversion goals: what counts and what does not#

The UET tag logs actions. Conversion goals decide which actions deserve the name conversion, and Microsoft splits the choice across a fixed list of goal types: destination URL, event, duration, pages viewed per visit and product for websites, plus mobile app installs, store visits and in-store transactions for the offline world.

Not every action deserves the name. A newsletter signup and a completed checkout are both events the tag can see, but treating them as equals quietly poisons every automated bid strategy downstream. The discipline is choosing a subset, and Microsoft's own guidance is blunt about it: not all actions are created equal.

Simplified versus manual setup

Microsoft now offers two routes. Simplified setup watches your UET tag, auto-detects events like purchases and checkouts, and suggests goals for you to approve. It is fast, and it does not support variable revenue. Manual setup walks through goal category, goal type, revenue and counting choices field by field, and remains the only route to variable revenue values and offline goals.

Counts, windows and revenue values#

Three settings decide what the numbers mean. Counting decides how repeat conversions from one click are treated: count every conversion, or count one per click. Lead businesses generally want one, shops want every, and getting it backwards flatters or starves the wrong column.

Windows decide how long after a click a conversion still counts. Microsoft lets you set a conversion window of up to 90 days, with a separate view-through window for conversions after an impression with no click. Long windows suit considered purchases; short windows keep the bidding brain honest on fast cycles.

Revenue decides whether value-based bidding has anything to weigh. Choose a static value per conversion, or variable revenue that your UET tag sends per transaction. Microsoft documents variable revenue as an option only for destination URL and event goals, so shops tracking product goals need the event route if they want real basket values flowing into target ROAS.

Offline conversions and the MSCLKID trail#

Plenty of folkfox work is lead generation, and lead generation converts in a CRM, not on a page. Microsoft's answer is offline conversions: you capture the Microsoft Click ID, the MSCLKID parameter appended to your ad landing page URLs, store it against the lead, and upload it back when the lead becomes a sale.

The mechanics matter because the direction is backwards from everything else: the click happened weeks ago, and the upload happens now. Microsoft matches the uploaded click ID to the original ad click and credits the conversion to that click, so automated bidding finally learns which clicks turn into revenue rather than which clicks turn into form fills.

• Capture MSCLKID on your forms via UET parameters or your own hidden field
• Store it with the lead record, never hash it, it must round-trip unchanged
• Upload conversions with the click ID, conversion time and optional revenue
• Check the upload receipt rather than assuming the file landed

For the full loop from tag to table, the Microsoft Ads Hub walks the whole platform, and our PPC service audits exactly this chain for lead businesses.

How to test Microsoft Ads conversion tracking, step by step#

Now the practical part: proving the chain works before a misfiring setup wastes a month of spend. Five checks, run in order, catch nearly every fault a fox meets in the wild.

1. Check the tag: load a page and confirm the bat.bing.com request fires, via the browser network tab or the UET Tag Helper extension
2. Check the goal: read each conversion goal's status and confirm it is marked to include in Conversions if it should steer bidding
3. Fire a test conversion: complete the tracked action yourself on the live site
4. Watch the attribution: click one of your own ads and confirm the landing URL carries MSCLKID
5. Wait out the lag: give the report a day or two before judging recent rows

The nastiest failure is the quiet one. A UET tag placed on the wrong template, or stripped by a consent banner that fires before it, errors nothing. The ads run, the impressions flow, and conversions simply never appear. That is why the test above is a routine, not an audit.

Five faults that fox even careful advertisers#

Run the test often enough and the same five faults keep turning up, account after account. None throw an error. All five quietly starve a column until someone notices the numbers look thin.

Consent deserves its own line, because Europe is where folkfox does much of its work. For visitors from the EEA, the United Kingdom and Switzerland, Microsoft requires Consent Mode or the Transparency and Consent Framework on your UET tags, and warns plainly that skipping it damages conversion attribution and remarketing segments. Wire consent in before the tag, not after.

Frequently asked questions#