How to track referral to closed sale for Microsoft Ads

Architecture

The exact event sequence

Five stages. The break is at stage three and it is a logic decision, not a technical failure. Two identifiers arrive and something has to choose. The identifier has to survive all of them.

1. Step 1

   Referral link shared

   Person to person. No campaign produced this.

2. Step 2

   Referred visitor arrives

   With a referral parameter, onto a browser that may already hold a paid identifier from last week.

3. Step 3

   Precedence decided

   The moment that determines who gets credit, and the moment almost nobody has consciously configured.

4. Step 4

   Sale closed

   Attributed to whichever identifier survived.

5. Step 5

   Reward issued

   Which frequently produces a second purchase that must not inherit the first sale's attribution.

Diagnostic sequence

What's specific to Microsoft Ads

The funnel logic above is the same wherever you advertise. These are the parts that change because it's Microsoft Ads.

1. 1

   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.

2. 2

   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.

3. 3

   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.

4. 4

   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.

5. 5

   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.

Source-of-truth validation

How to prove the chain works

One real journey, followed all the way, then a reconciliation. Neither on its own is enough.

• A live Microsoft ad clicked, and the identifier confirmed present on the landing URL.
• The same identifier confirmed on the closed sale, with its true origin recorded after a full real journey through every step.
• Reward issued confirmed arriving at Microsoft Ads, verified by the upload's match rate and Microsoft's conversion goal diagnostics.
• Your order or crm record, with referral and paid sources held apart reconciled against Microsoft Ads per record over a fully closed window.
• The same reconciliation repeated 30 days later.

Straight talk

When this doesn't apply to you

Worth checking before you build anything, because two of these are common and both mean the work isn't worth doing.

• With no referral program there is no conflict, and this is an ordinary purchase funnel.
• 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 reward issued regularly exceeds the import window, the final event can't drive bidding whatever you build. Optimize toward sales with both source parameters retained for later analysis instead and use the later data for budget decisions rather than for bidding.
• If almost none of your closed sales by origin carry a click identifier today, that's the whole project. Fix capture first — the import is the easy half and no tooling rescues a record with nothing to reference.