How to track checkout to purchase for Microsoft Ads
Everything between checkout starting and the order existing is where ecommerce tracking actually fails, and it fails differently depending on how your checkout is built. A hosted payment page is a different domain. A wallet payment can complete without the customer ever seeing the confirmation. Both produce orders in your store that no platform ever hears about. On Microsoft Ads the specifics that matter are the click identifier (msclkid), the import mechanism (Microsoft's offline conversion import), and conversion goals deduplicate on their own counting settings, as in Google Ads, rather than through a shared event ID. The chain only works end to end if the identifier is captured on landing and stored on the order record in your store — no cookie survives the gap between checkout started and purchase sent with the order id.
Free30 minutesNo obligation
Specific to Microsoft × Checkout → purchase
Microsoft Ads: rebuild the copied thank-you page purchase goal
On Microsoft Ads, replace any destination URL purchase goal with an event goal fed from the order webhook through offline conversion import, keyed to the msclkid saved on the order at checkout start and carrying revenue. Keep a separate begin-checkout event goal excluded from bidding to diagnose drop-off between checkout and payment.
Microsoft Ads accounts imported from Google usually carry a purchase goal defined by the confirmation page URL. That goal type is the weakest possible fit for checkout-to-purchase: wallet and hosted-payment orders that skip the page are never counted, and anyone who reloads or bookmarks the page counts again. Rebuild it as an event goal sent once per order from the order record.
Microsoft's audience pays by card on desktop more often than mobile-first platforms, so hosted payment pages and redirect gateways matter more than wallets here. The hop to the payment domain is where msclkid falls out of the session. Save it onto the order at checkout start, and send the purchase through offline import against it, so the outcome is matched even when the shopper returns to a different page than expected.
Check whether the account has a UET begin-checkout event at all. Many imported accounts track only the purchase, which makes it impossible to tell whether Microsoft traffic abandons at checkout or the tag simply misses orders. Microsoft also supports enhanced conversions with hashed customer data; confirm current requirements in Microsoft's documentation before relying on it for orders without msclkid.
Microsoft · Checkout → purchase · what breaks
Where this funnel usually breaks — Microsoft · Checkout → purchase
- 01
Wallet payments skip the confirmation page
Shop Pay and PayPal can be abandoned after the money moves. The order is real; the page view never happened.
- 02
A hosted payment page on another domain
Session splits, the click identifier doesn't cross, and the purchase gets credited to your own site as a referral.
- 03
Every payment method assumed to behave the same
Card, wallet and redirect gateways each return differently, and the untested one is where the missing conversions are.
Microsoft · Checkout → purchase · the fix
What working looks like — Microsoft · Checkout → purchase
Purchase sent with the order ID attributed to the click
Weeks later if necessary, because the identifier lives on the order record in your store rather than in a cookie.
Microsoft bidding fed the real outcome
Via offline conversion import, so it optimizes toward completed orders rather than toward checkout starts.
A reconciliation that closes
Your store's order records, web orders only matched per record against what Microsoft Ads reports, over a fully closed window.
Microsoft · Checkout → purchase · architecture
The exact event sequence — Microsoft · Checkout → purchase
Stage three is the one you often can't instrument, which is precisely why stage four has to be the source.
- 1
Checkout started
Browser-side, with value. The last point you reliably control the page.
- 2
Payment info submitted
Worth splitting out — it turns one opaque step into a diagnosable one.
- 3
Payment authorised
Often on someone else's domain, and frequently invisible to your tags entirely.
- 4
Order created
From the order webhook. This is the only step that sees every order regardless of how payment happened.
- 5
Purchase sent with the order ID
Deduplicated on that ID, with refunds wired to reverse.
Microsoft · Checkout → purchase · diagnose
What's specific to Microsoft Ads
- 01
Click identifier: msclkid
Microsoft's click identifier, appended when auto-tagging is enabled. It depends on the UET tag being present on the site — without UET, msclkid arrives in the URL and there's nothing consuming it, which is a common half-configured state on accounts imported from Google.
- 02
Import mechanism: offline conversion import
Uploaded against msclkid, closely mirroring Google's approach. Because so many Microsoft accounts are imported wholesale from Google Ads, people assume full parity — verify the current column format and requirements in Microsoft's documentation rather than reusing your Google template unchanged.
- 03
Deduplication
The same counting question applies: one conversion per click for lead-type goals, every conversion for ecommerce. Accounts imported from Google frequently carry over the goal structure and not the counting review, so it's worth reading every goal rather than assuming the import got it right.
- 04
Window and timing
Check Microsoft's current offline import window and attribution settings directly. They resemble Google's closely enough to be assumed and differ enough to matter.
- 05
The Microsoft gotcha
Almost every Microsoft account we open was imported from Google Ads, and the import copies campaign structure without copying the tracking. The result is a live account spending money with UET missing, msclkid unconsumed, or conversion goals pointing at pages that don't exist on the site any more.
Microsoft · Checkout → purchase · prove
How to prove the chain works — Microsoft · Checkout → purchase
Source of truth
your store's order records, web orders only
- The same identifier confirmed on the order record in your store after a full real journey through every step.
- Purchase sent with the order ID confirmed arriving at Microsoft Ads, verified by the upload's match rate and Microsoft's conversion goal diagnostics.
- Your store's order records, web orders only reconciled against Microsoft Ads per record over a fully closed window.
Microsoft · Checkout → purchase · free audit
What we check in the free audit
- Click identifier: msclkid
- Import mechanism: offline conversion import
- Deduplication
- Window and timing
- The Microsoft gotcha
Checked against
your store's order records, web orders only
Free30 minutesNo obligation
Microsoft · Checkout → purchase · when not to buy
When this doesn't apply to you — Microsoft · Checkout → purchase
- If your checkout is entirely on your own domain with no wallet options and a confirmation page every customer reaches, the browser-side event may genuinely be sufficient — reconcile a closed week and find out before building anything.
- If your Microsoft account is a straight import you've never separately configured, fix the account structure and UET installation first — offline import on top of an unconfigured account produces data nobody will trust.
- If your cycle from click to purchase sent with the order id regularly exceeds the import window, the final event can't drive bidding whatever you build. Optimize toward payment info submitted instead and use the later data for budget decisions rather than for bidding.
- If almost none of your orders carry a click identifier today, that's the whole project.
Microsoft · Checkout → purchase · what we deliver
The implementation, on Microsoft Ads
Capture msclkid on landing
Auto-tagging appends msclkid, and the UET tag has to be present to make use of it. Add msclkid explicitly to your capture list alongside the Google parameters — code written for gclid alone won't pick it up.
Persist it to the order record in your store
Set a first-party cookie server-side before the hop, and pass the identifier into the payment domain where the provider supports it — where it doesn't, the order record is the only path.
Send purchase sent with the order id from the record
The order webhook fires once per order, independent of which payment path the customer took or whether they ever saw a confirmation page. Dispatched to Microsoft Ads through Microsoft's offline conversion import.
Deduplicate and reverse
Conversion goals deduplicate on their own counting settings, as in google ads, rather than through a shared event id. Refunds reverse from the refund webhook; failed and cancelled orders should never have counted in the first place.
FAQ
Microsoft · Checkout → purchase questions, answered
A destination URL goal counts every view of the confirmation page, including reloads. Switch to an event goal sent once per order.
Yes, the offline import matches on msclkid, so save it onto the order at checkout start. Check Microsoft's current enhanced conversions options for orders without one.
Because checkout starts are plentiful and the completion rate varies hugely by channel and device. Optimizing on starts buys traffic that begins checkouts and abandons them.
It doesn't, as a cookie — the gap is too long. It has to be written onto the order record in your store at the point of checkout started, where it lives as a field rather than as browser storage.
msclkid inside the import window, a conversion goal name matching one in the account, a timestamp and a value. Confirm current requirements in Microsoft's documentation.
Two to four days for the implementation, plus a closed reconciliation window before we'd call it verified. Capture and persistence are the fiddly parts; the import itself is usually an afternoon.
Yes, and the reference pages on this site cover the mechanics. The part that's genuinely tedious rather than clever is keeping msclkid alive through multi-step forms and the hop to a hosted payment domain, which fails silently at every stage.
More on Microsoft · Checkout → purchase
- Microsoft · Add to cart → purchaseHow to track add to cart to purchase for Microsoft Ads
- Google Ads · Checkout → purchaseHow to track checkout to purchase for Google Ads
- Meta · Checkout → purchaseHow to track checkout to purchase for Meta Ads
RELATED GUIDES
Funnels next to checkout to purchase, and the checks that close it
- Microsoft · Quiz → segmented offerHow to track quiz completion to segmented offer for Microsoft Ads
- Microsoft · App install → purchaseHow to track app install to in-app purchase for Microsoft Ads
- Microsoft × Ecommerce OrdersHow to reconcile Microsoft Ads against your store's order table
- Microsoft · FirearmsMicrosoft Ads conversion tracking for firearms retailers
- Microsoft · CannabisMicrosoft Ads conversion tracking for cannabis businesses
- Smoobu → Microsoft AdsConnecting Smoobu to Microsoft Ads
- Profitroom → Microsoft AdsConnecting Profitroom to Microsoft Ads
- Microsoft · Reactivation → repeat purchaseHow to track lapsed customer reactivation to repeat purchase for Microsoft Ads
Free · 30 min
Get checkout to purchase tracked properly on Microsoft Ads
WhatsAppFree30 minutesNo obligation
