Microsoft Ads tracking that's more than a UET tag sitting there
The most common state we find on Microsoft Ads is a UET tag installed and nothing configured beyond it — recording traffic and optimising toward nothing. Microsoft mirrors Google closely, including Enhanced Conversions and offline imports, so the same rigour applies: capture msclkid at first touch, define goals that mean something, mark exactly one coherent set as primary, and send closed revenue back where the sales cycle needs it.
Free30 minutesNo obligation
Microsoft Ads UET · what breaks
What we usually find — Microsoft Ads UET
- 01
UET tag present, no goals defined
The most common state, and it means bidding has no target.
- 02
No msclkid captured
Auto-tagging off or a redirect stripping it, so offline imports can't match.
- 03
Goals imported from analytics and never checked
Inheriting definitions that were fine elsewhere and are wrong as a bidding target.
- 04
Treated as an afterthought to Google
Managed by import with nobody watching it.
Microsoft Ads UET · the fix
What you get out of it — Microsoft Ads UET
Goals that mean something
Defined deliberately, with one coherent primary set.
msclkid captured and stored
So offline imports have something to match on.
Enhanced Conversions receiving data
Verified rather than toggled on.
A channel judged on cost per conversion
Rather than dismissed on volume.
Microsoft Ads UET · architecture
Why the numbers were wrong before you got here — Microsoft Ads UET
Worth understanding before buying anything, because it decides which tier you need — and for some readers the answer is that you don't need us yet.
- 1
The browser is the weakest link, and it is getting weaker on purpose
Every browser-side tag has to survive the page loading, the visitor staying, the script running and the request leaving. All four are now contested. The order in your database is certain; the browser event reporting it is not.
- 2
Safari caps the cookie your attribution depends on
Intelligent Tracking Prevention limits JavaScript-set cookies to seven days whatever expiry you set, so a customer who takes longer than a week to decide returns as a stranger. A cookie your own server writes in an HTTP response is not capped — the single largest practical difference between browser-side and first-party server-side.
- 3
Ad blockers remove the tag with no error
A blocked pixel does not warn anyone. The customer buys, the order lands, and no platform hears about it. First-party events from your own subdomain are not a third-party request and are not filtered the same way.
- 4
Consent is enforced by hope, not by architecture
Client-side consent means trusting each vendor script to honour a flag. A server container decides at the container: a denied destination receives nothing. That is a materially stronger position, and it also stops the over-blocking that discards data no law required losing.
- 5
Checkout can end where your tag isn't
Wallets and hosted payment pages can be abandoned after the money moves. Sending the purchase from the order record means it arrives whether or not anyone came back.
Microsoft Ads UET · diagnose
How we scope the microsoft ads build
Before quoting. Each step narrows what the work actually is, so the price reflects your account rather than an average.
- 01
Confirm auto-tagging and msclkid capture
Through every redirect.
- 02
Read the UET tag and goal diagnostics
Microsoft names when each goal last received a hit.
- 03
Check which goals count toward primary
Multiple primaries split bidding attention.
- 04
Verify revenue and currency in the payload
Numeric, explicit, consistent with other platforms.
- 05
Confirm Enhanced Conversions is receiving hashed data
Present but empty is common.
- 06
Reconcile a closed window
On a click-date basis, matched on transaction ID.
Microsoft Ads UET · prove
How the work gets proven — Microsoft Ads UET
A dashboard turning green proves a dashboard turned green. These are what we hand over instead.
Source of truth
Your store or CRM order records
- Every conversion goal receiving hits, confirmed in the diagnostics panel.
- msclkid present on converting sessions from Microsoft clicks.
- Purchase count within a few percent of backend orders for a closed window.
- Exactly one coherent primary set.
- Reconciled over a fully closed window, matched on ID rather than on totals — totals hide equal and opposite errors.
- Payload evidence captured from real transactions, saved to your own records.
- The same reconciliation repeated 30 days later, because a setup that works once and drifts is the harder failure.
Microsoft Ads UET · free audit
What we check in the free audit
- Confirm auto-tagging and msclkid capture
- Read the UET tag and goal diagnostics
- Check which goals count toward primary
- Verify revenue and currency in the payload
- Confirm Enhanced Conversions is receiving hashed data
- Reconcile a closed window
Checked against
Your store or CRM order records
Free30 minutesNo obligation
Microsoft Ads UET · when not to buy
When you shouldn't buy this — Microsoft Ads UET
We would rather say it now than three weeks into an engagement.
- You don't run Microsoft Ads. Importing Google campaigns without intending to manage them creates spend without oversight.
- Microsoft is under about 5% of paid spend and your Google setup isn't correct yet. Fix the larger channel first.
- Your audience is outside Microsoft's reach — very young, or a market where Bing share is negligible.
- You already have goals defined and reconciling. Verify it and leave it.
Microsoft Ads UET · what we deliver
What's included in the microsoft ads build
msclkid capture at first touch
First-party, surviving redirects.
Conversion goals defined and scoped
Correct counting, correct category, one primary set.
Server-side conversion path
Purchase from the order record with a transaction ID.
Enhanced Conversions wired
Hashed identity, verified as arriving.
Offline import where the cycle needs it
With match rates checked.
Reconciliation
Against your backend, on a click-date basis.
Written guarantee
95%+ tracking accuracy
Measured against Your store or CRM order records. Miss it and we keep working at no cost.
Pricing
Pick the package that fits your ad spend
Browser-side starter
$400One-time fee · lifetime ownership
The correct browser-side build, done properly and verified on a live transaction. Honest about its ceiling: it will not survive Safari's cookie cap, an ad blocker, or a checkout that ends somewhere your tag isn't. If you spend $1K+/month on paid media, start one tier up.
- Correct events, correct parameters, correct values
- Verified on a live transaction, not in preview
- Reconciled against your own order records
- Written handover you keep
1st-party server-side
Recommended$800One-time fee · most popular
The tier that changes the outcome rather than patching it. Your money events stop depending on the browser: they are sent from your order records through a first-party server container on your own subdomain, so iOS, ad blockers, consent banners and interrupted payment redirects can no longer take them away. Built in 2–4 days. You own the stack outright, with no monthly SaaS.
- First-party server container on your own subdomain
- Money events sent from your order records, not the browser
- Meta, Google, TikTok, Microsoft and LinkedIn all fed server-side
- Deduplicated on a shared event ID, verified at every destination
- First-party cookies beyond Safari's 7-day cap on JavaScript-set cookies
- 95%+ conversion accuracy and 8+ Meta EMQ, guaranteed in writing
Full 1st-party stack
$1,800One-time fee · lifetime ownership
Every paid-media channel server-side, plus the offline loop that connects closed revenue back to the click. For advertisers whose spend makes an attribution leak more expensive than the build.
- Everything in 1st-party server-side
- Pinterest, Snapchat, Reddit and LinkedIn CAPI
- CRM and offline conversion loop, so closed revenue reaches bidding
- Refunds and cancellations reversed at every destination
- Klaviyo identity stitching, BigQuery and Looker Studio
- Monitoring, so the next break surfaces in days rather than a quarter
FAQ
Microsoft Ads UET questions, answered
It depends on your audience. Volume is lower than Google, but cost per conversion is often better. Judge it on that rather than on impression share.
You can, and imported goals inherit definitions that may be wrong as a bidding target. Worth reviewing rather than trusting.
Yes, and offline imports too. It mirrors Google closely enough that the same method applies.
Smaller search share. That's a channel characteristic, not a tracking fault — judge it on cost per conversion.
Free · 30 min
Get Microsoft Ads optimising toward something
WhatsAppFree30 minutesNo obligation
