How offline conversion import works
The website captures a click identifier when a visitor arrives from an ad, and stores it with the enquiry — usually in a hidden form field that travels into the CRM. Weeks or months later, when the sales team marks that record as won, you send the identifier back to Google Ads together with the outcome, its date and, ideally, its value.
Google finds the click behind the identifier and records a conversion against it. From the account’s point of view the result is indistinguishable from a website conversion, except that it represents something real: a signed contract, a paid invoice, a student enrolled, a property viewing that turned into a deposit. Uploads can be done by file, on a schedule from a spreadsheet, or through a direct connection between the CRM and Google Ads.
Why it matters
Automated bidding optimises for whatever you tell it a conversion is. If the only conversion is a form submission, the system will find the campaigns that produce the most form submissions — which is not the same as the campaigns that produce customers, and is often the opposite. Cheap enquiries from broad, curious traffic beat expensive enquiries from serious buyers on every metric except the one that pays the bills.
Sending outcomes back closes that gap. It matters most where the gap is widest: long sales conversations, high-value services, and businesses where a large share of enquiries are unqualified from the start. Education consultancies, manpower agencies, property and B2B services in Nepal all fit that description, and all of them can be badly misled by enquiry counts alone.
Where it goes wrong
Capture is the first weak point. If the click identifier is not stored at the moment of enquiry, there is nothing to upload later, and no amount of CRM tidying will recover it. Redirects that strip query parameters, forms rebuilt without the hidden field, and landing pages on a separate platform all break it silently.
The second is discipline. An upload that happens when someone remembers produces jagged, unreliable data, and bidding responds badly to that. The third is timing: Google will not accept a conversion for a click that is too old, so a sales cycle longer than the permitted window needs an interim milestone — a qualified enquiry or a booked meeting — rather than only the final sale.
What to do about it
Fix the capture before anything else. Add hidden fields for every Google click parameter, confirm they arrive populated in real submissions, and check they survive whatever redirects sit between the ad and the form. Then decide which milestones you will send back and what each is worth, in plain terms both you and the sales team agree on.
Make the upload boring: a fixed schedule, an owner, and a check that the file was accepted. A direct CRM integration removes the human step entirely and is worth the setup cost for anything above a trickle of leads. Where the identifier was never captured, hashed contact details give you a second route — see enhanced conversions for leads — but treat that as a safety net rather than the plan.