Skip to main content
Microsoft × CRM DealsRun this yourself

How to reconcile Microsoft Ads against your CRM's closed-won deals

This is the check we run first on every account, written out so you can run it without us. It takes about thirty minutes and needs two numbers: what Microsoft says it produced, and what your CRM's closed-won deals actually shows. The gap between them is the only honest measure of whether your tracking works — and if it comes back small, you do not need us.

Free30 minutesNo obligation

Specific to Microsoft × CRM Deals

Microsoft Ads vs closed-won deals: msclkid is usually missing

Match Microsoft Ads to closed-won deals on msclkid stored with the deal and uploaded as an offline conversion goal. Check Microsoft's current import window rather than assuming Google's 90 days. Microsoft should show fewer won deals than the CRM; if it shows none while Bing-sourced leads exist, msclkid is not being captured.

Microsoft is a better fit for B2B deals than its spend share suggests, partly because of its LinkedIn profile targeting by company and job function. The join key is msclkid, which auto-tagging appends and the UET tag consumes. Your form capture must name it explicitly and the CRM needs a property to hold it, otherwise the deal has nothing Microsoft can recognize when you upload it.

Check the offline import window and attribution settings in the account directly. They look like Google's and differ in the details, and a deal closing after the window cannot be uploaded at all. Like Google, conversion goals count on their own setting, so a lead-stage goal set to count every conversion will inflate if one prospect submits twice. Read the offline conversion upload history for matched rows, then compare by close month against the CRM.

Microsoft reporting fewer deals than the CRM attributes to Bing is normal when cycles run long. A complete absence of matched deals is breakage. The usual cause is an account imported from Google with campaigns copied and tracking not: no UET, no msclkid field on the forms, and a CRM that only ever mapped gclid.

Microsoft × CRM Deals · what breaks

Why Microsoft and your CRM's closed-won deals disagree

  1. 01

    Form fills counted instead of deals

    The most common B2B error. The platform counts an enquiry; the business earns on a signed contract, and the rate between them varies enormously by source.

  2. 02

    Outbound pipeline in the same report

    Deals a rep sourced by cold outreach land in the same pipeline as inbound ones. Without an origin field they inflate marketing's apparent performance.

  3. 03

    Several contacts from one company

    Three people from one account researching separately is one opportunity. Counting them separately makes cost per acquisition read as a third of reality.

  4. 04

    Sales cycle longer than the attribution window

    A deal that closes in month four falls outside every default window, so the campaign shows nothing while producing everything.

Microsoft × CRM Deals · the fix

What you get from this — Microsoft × CRM Deals

  • A number instead of a suspicion

  • The likely cause, narrowed

  • A basis for deciding

Microsoft × CRM Deals · architecture

What each side is actually counting — Microsoft × CRM Deals

  1. 1

    What Microsoft counts

    msclkid inside the import window, a conversion goal name matching one in the account, a timestamp and a value.

  2. 2

    How Microsoft attributes it

    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.

  3. 3

    The window it uses

    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.

  4. 4

    What your CRM's closed-won deals counts

    Opportunities marked closed-won, at their actual value, found in HubSpot → Deals, Salesforce → Opportunities, Pipedrive → Deals, filtered to won.

  5. 5

    The filter that makes them comparable

    Stage is closed-won, and the source is a paid channel rather than outbound or referral.

Microsoft × CRM Deals · events

Reading the gap — Microsoft × CRM Deals

15%+ platform higherUsually the wrong event entirely — the platform is claiming deals it did not produce. usually outbound or referral pipeline landing in the same report without an origin field.
20%+ platform lowerUsually structural — the platform is missing deals it produced. almost always the cycle outliving the window, or the identifier never reaching the crm record.

Microsoft × CRM Deals · diagnose

Diagnostic order — Microsoft × CRM Deals

  1. 01

    Confirm both numbers cover the same period and channel

  2. 02

    Form fills counted instead of deals

    The most common B2B error. The platform counts an enquiry; the business earns on a signed contract, and the rate between them varies enormously by source.

  3. 03

    Outbound pipeline in the same report

    Deals a rep sourced by cold outreach land in the same pipeline as inbound ones. Without an origin field they inflate marketing's apparent performance.

  4. 04

    Several contacts from one company

    Three people from one account researching separately is one opportunity. Counting them separately makes cost per acquisition read as a third of reality.

  5. 05

    Read the upload's match rate and Microsoft's conversion goal diagnostics

    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 × CRM Deals · prove

How to know you did it right — Microsoft × CRM Deals

Source of truth

your CRM's closed-won deals — closed-won deals for a fully closed month

    Microsoft × CRM Deals · free audit

    What we check in the free audit

    • Confirm both numbers cover the same period and channel
    • Form fills counted instead of deals
    • Outbound pipeline in the same report
    • Several contacts from one company
    • Read the upload's match rate and Microsoft's conversion goal diagnostics

    Checked against

    your CRM's closed-won deals — closed-won deals for a fully closed month

    Get my free conversion tracking audit

    Free30 minutesNo obligation

    Microsoft × CRM Deals · when not to buy

    When the answer is that you do not need us — Microsoft × CRM Deals

    • If almost all of your closed-won deals come from a channel with no click behind it, no tracking work will reach them — and knowing that is worth more than a build.
    • 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.

    Microsoft × CRM Deals · what we deliver

    The method, step by step — Microsoft × CRM Deals

    • Pull what Microsoft reports

      The upload's match rate and microsoft's conversion goal diagnostics.

    • Pull what your CRM's closed-won deals shows

      Export closed-won deals by close date for a window long enough to cover your full sales cycle. Deduplicate to one per account, and sum the value actually contracted.

    • Filter both to the same thing

      Stage is closed-won, and the source is a paid channel rather than outbound or referral.

    • Compare per record, not on totals

    FAQ

    Microsoft × CRM Deals questions, answered

    The structure is similar, but the identifier column must hold msclkid and the goal names must match goals in the Microsoft account. A Google file with gclid values will match nothing.

    Free · 30 min

    Found a gap between Microsoft and your CRM's closed-won deals?

    Free30 minutesNo obligation