How to track quote request to closed job for Microsoft Ads

Architecture

The exact event sequence

Five stages. The break is almost always between stages one and four, where the identifier has to survive a handoff from a web form into a field service system that a different team administers — and where the value spread between a small repair and a full replacement is wide enough that averaging destroys the signal. The identifier has to survive all of them.

1. Step 1

   Quote requested

   A form or a call. High volume, and most of it is comparison shopping across three or four vendors.

2. Step 2

   Estimate scheduled

   A time commitment from the customer, and the first signal that means anything.

3. Step 3

   Estimate attended

   The visit actually happened. No-show rates on cold paid traffic are meaningful and differ by campaign.

4. Step 4

   Job signed

   The money event, at the actual contract value rather than an average.

5. Step 5

   Job completed

   Final revenue, which can differ from the contract once change orders land.

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 job record in your field service or job management system after a full real journey through every step.
• Job completed confirmed arriving at Microsoft Ads, verified by the upload's match rate and Microsoft's conversion goal diagnostics.
• Your job management system's signed and completed jobs, by date, at their contract values 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.

• If you close on the first call at a flat price with no site visit, this funnel collapses into a much simpler one and you do not need the job system in the loop. Say so before anyone quotes you for it.
• 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 job completed regularly exceeds the import window, the final event can't drive bidding whatever you build. Optimize toward attended estimate, valued at your own estimate-to-close rate instead and use the later data for budget decisions rather than for bidding.
• If almost none of your job records 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.