Send CRM outcomes back to Microsoft Ads as offline conversions
Website forms show activity, not necessarily revenue. By returning a later CRM milestone — such as a qualified lead or a created deal — to Microsoft Ads, you can teach automated bidding which clicks are worth more, while avoiding low-quality form fills from existing customers or unrelated enquiries.
Pick a milestone Microsoft Ads can actually learn from
Choose the earliest CRM event that reliably signals value and still happens often enough to learn from. Qualified status or deal creation usually fits better than a closed-won deal when sales cycles are long or monthly closures are few. Check two constraints before committing: automated strategies need roughly 50 conversions a month, and the click-to-conversion window defaults to 30 days with a 90-day maximum. If your milestone routinely falls outside that window, move it earlier.
Capture the click ID before the lead is created
Turn on auto-tagging so each ad click appends a Microsoft Click ID to the landing URL. That identifier is the link between the click and the later CRM record. A capture script on the site should store the identifier in the browser, then pass it through hidden form fields at submission. Storing it matters when a visitor lands on one page, browses to another, or returns later — a form builder that only reads the current URL would miss it in those cases. The same mechanism can also carry UTM parameters and channel information into the CRM.
Build the upload file from a filtered CRM report
Create an offline conversion goal in Microsoft Ads with a name that matches the CRM milestone, for example CRM Deal Created. Then export a CRM report filtered to that milestone and to records with a non-empty click ID. Add the fixed fields manually: conversion type, status, account ID, goal name, currency code and conversion time. Pull the click ID, deal value and event time from the CRM. Keep the value as a plain number without a currency symbol, and format the time in the local format the upload expects.
Upload, preview and verify with a real click
Upload the CSV under offline conversions, preview it for errors, fix any rejected rows, then submit. Processing can take about 6 to 8 hours, after which the goal name, counts, timestamps and values should be checked in conversion reporting. For testing, use a real search click in an incognito window — ad preview tools do not generate a genuine click ID — then submit a form, confirm the ID on the CRM contact, and upload that single test record.
Add value so bidding can weigh quality, not just volume
Where possible, include a conversion value. At closed-won, use the actual amount. Earlier in the funnel, use expected deal value or an expected value per deal: average deal size multiplied by close rate. For example, a $1,000 average deal at a 25% close rate gives an expected value of $250 per deal. Value data gives the bidding system more to learn from and can support value-based strategies. If the column is left blank, the goal's default value and currency apply instead.
Automate the spreadsheet when direct sending is unavailable
Direct automation into Microsoft Ads may not be available in every integration tool, so a practical middle step is to automate the spreadsheet instead. Trigger a new row whenever the CRM milestone occurs, mapping the click ID, event time and deal amount, with fixed values for the remaining columns. Download the sheet as CSV every week or two and upload it. That keeps the manual step small while the data capture stays automatic.
| CSV field | What to enter | Where it comes from |
|---|---|---|
| Type | Offline Conversion on every row | Fixed value |
| Status | Active on every row | Fixed value |
| Client ID | Microsoft Ads account number | Account settings |
| Name / Conversion Name | Exact offline goal name, e.g. CRM Deal Created | Conversion goal created in Microsoft Ads |
| Conversion Currency Code | Three-letter currency code, e.g. USD | Reporting currency |
| Conversion Time | Local date and time of the CRM milestone | CRM event timestamp |
| Conversion Value | Numeric amount only, no currency symbol | Deal amount or expected value |
| Microsoft Click ID | Click ID stored with the lead | CRM record |
Fixed fields can be added manually; click ID, value and time should come from the filtered CRM report.
Frequently asked questions
Why not send every form submission as a conversion?
A form submission alone can include existing customers, sales pitches and low-intent enquiries. Waiting for a qualified lead, created deal or closed deal gives the bidding system a clearer signal of value.
What volume and timing should the chosen milestone meet?
Automated bidding needs volume to learn from. The guide states at least 50 conversions per month are needed, and the conversion window is 30 days by default, extendable to 90 days. A milestone that is frequent enough and close enough to the click is therefore safer.
Do I also need to upload email and phone for Enhanced Conversions?
No. Microsoft Ads checks the MSCLKID first and only uses email or phone as a fallback. Because those fallback fields must be hashed, sending them adds complexity without improving matching when the click ID is present.
How do I keep non-Microsoft Ads leads out of the upload?
Filter the CRM report to records where the MSCLKID is not empty. Microsoft Ads would reject rows without it, but filtering first keeps upload errors from hiding genuine problems.