Skip to main content
Microsoft · Phone call → saleUse-case guide

How to track phone call to sale for Microsoft Ads

For a lot of businesses the phone is the conversion, and a website tag can see none of it. Getting this right needs two separate things: dynamic number insertion so the call carries a source at all, and a recorded outcome so a wrong number isn't worth the same as a booked job. Almost every implementation we open has the first and not the second. 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 call record, joined to your job or CRM system — no cookie survives the gap between ad click and qualified calls sent back.

Free30 minutesNo obligation

Specific to Microsoft × Phone call → sale

Microsoft Ads calls: make the number pool read msclkid too

On Microsoft Ads, track phone call to sale by having your number pool store msclkid on the call record, with UET installed on every page, then importing the sold job as an offline conversion goal with its value. Pools configured only for gclid drop Microsoft callers into the Google or organic bucket.

Microsoft's search audience skews older and more desktop-heavy than Google's, and for call-driven businesses such as insurance, home repair, legal and senior care that often means a higher share of people who would rather phone than fill a form. That makes call-to-sale tracking worth more here, relative to spend, than the account's size suggests.

The common break is the number pool, not the import. Dynamic number insertion is usually configured when Google is the only paid channel, with source rules keyed on gclid or on Google's UTM tags. When the Microsoft account is later imported from Google, its clicks arrive with msclkid and, often, copied UTM values that still say google. The call is then credited to the wrong engine, or to nothing. Check that the pool reads msclkid, and that Microsoft campaigns have their own tracking template.

Once msclkid sits on the call record, import the sold job against it with the job value. Set the goal to count one conversion per click, and keep any call-extension or call-duration goal as a non-primary goal so bidding is not split between rings and sales. Microsoft accounts usually run on a fraction of Google's volume, so check that the sold-call goal produces enough conversions a month before switching to a value-based bid strategy.

Microsoft · Phone call → sale · what breaks

Where this funnel usually breaks — Microsoft · Phone call → sale

  1. 01

    A hard-coded number insertion can't reach

    A number in a header graphic, a footer or a sticky mobile bar can't be swapped, and those calls arrive with no source at all.

  2. 02

    Every call counted equally

    A thirty-second wrong number and a booked job teach bidding exactly the same thing.

  3. 03

    Click-to-call firing no event

    On mobile the customer taps the number. If the tel: link fires nothing, the highest-intent path is invisible.

Microsoft · Phone call → sale · the fix

What working looks like — Microsoft · Phone call → sale

  • Qualified calls sent back attributed to the click

    Weeks later if necessary, because the identifier lives on the call record, joined to your job or CRM system rather than in a cookie.

  • Microsoft bidding fed the real outcome

    Via offline conversion import, so it optimizes toward calls that turned into work rather than toward every ring.

  • A reconciliation that closes

    Call records joined to a recorded sale outcome matched per record against what Microsoft Ads reports, over a fully closed window.

Microsoft · Phone call → sale · architecture

The exact event sequence — Microsoft · Phone call → sale

Stage two is where most of the loss happens, and it's usually a phone number rendered inside an image.

  1. 1

    Ad click

    Identifier captured on landing, at the visit — not at the call, by which point the session context is gone.

  2. 2

    Number swapped

    Dynamic insertion across every template, including header images and the sticky mobile bar.

  3. 3

    Call connected

    The call platform records it against the session, which is how it carries a campaign.

  4. 4

    Outcome recorded

    Qualified, booked, sold. Duration is a proxy; the office's own disposition is the truth.

  5. 5

    Qualified calls sent back

    Only the ones that turned into work, so bidding stops buying wrong numbers.

Microsoft · Phone call → sale · diagnose

What's specific to Microsoft Ads

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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 · Phone call → sale · prove

How to prove the chain works — Microsoft · Phone call → sale

Source of truth

call records joined to a recorded sale outcome

  • The same identifier confirmed on the call record, joined to your job or CRM system after a full real journey through every step.
  • Qualified calls sent back confirmed arriving at Microsoft Ads, verified by the upload's match rate and Microsoft's conversion goal diagnostics.
  • Call records joined to a recorded sale outcome reconciled against Microsoft Ads per record over a fully closed window.

Microsoft · Phone call → sale · 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

call records joined to a recorded sale outcome

Get my free conversion tracking audit

Free30 minutesNo obligation

Microsoft · Phone call → sale · when not to buy

When this doesn't apply to you — Microsoft · Phone call → sale

  • If your calls come overwhelmingly from a Google Business Profile listing rather than from paid clicks, those aren't ad conversions and shouldn't be uploaded as any. Track them separately.
  • 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 qualified calls sent back regularly exceeds the import window, the final event can't drive bidding whatever you build. Optimize toward a qualified call by duration instead and use the later data for budget decisions rather than for bidding.
  • If almost none of your call records carry a click identifier today, that's the whole project.

Microsoft · Phone call → sale · 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 call record, joined to your job or CRM system

    Store it against the call record at the moment the number is served, so the call and the click are joined before anyone picks up.

  • Send qualified calls sent back from the record

    The call platform's webhook fires with the outcome once the office has dispositioned it, referencing the identifier captured at the visit. 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. A job later cancelled should be adjusted, particularly where you're uploading at the booked stage rather than the completed one.

FAQ

Microsoft · Phone call → sale questions, answered

Microsoft offers call reporting for call extensions in some markets; check what your account shows. Those calls skip your site, so they never carry an msclkid for offline import.

Free · 30 min

Get phone call to sale tracked properly on Microsoft Ads

Free30 minutesNo obligation