
If most of your sales close over the phone, in person or weeks later through a sales process, Google Ads can't see them unless you send that data back. The default approach today is enhanced conversions for leads, set up through the Google tag or Google Ads Data Manager, with the GCLID captured alongside it whenever you can. This guide covers how matching works, what to set up first, which upload route fits your systems and how to fix the errors you will run into.
An offline conversion is any sale or qualified action that happens away from your website after someone clicks a Google ad. A shopper clicks a search ad, calls your showroom three days later and buys a truck. A prospect fills out a form, works with your sales team for six weeks and signs a contract. Neither shows up in Google Ads unless you report it.
That gap matters because Smart Bidding learns from conversion data. If your account only sees form fills and never learns which ones turned into customers, it optimizes for lead volume instead of revenue. You end up paying for leads that never close while the campaigns producing fewer but better leads get starved of budget.
Common examples:
There are two methods. The first is the GCLID, a click identifier Google adds to your landing page URL. If you capture and store it, you can upload it later with the sale for an exact match. The second is enhanced conversions for leads, where email addresses or phone numbers are hashed and matched against signed in Google users.
The hashed method exists because GCLIDs get lost. A lead arrives through an odd browser or a CRM field never gets filled in. Hashed matching catches those cases and holds up better across devices and long sales cycles. Google recommends sending both when you can: the GCLID gives you certainty and the hashed data gives you coverage.
In practice the flow looks like this:
The fields that matter most in each upload are the GCLID, the conversion action name, the conversion time (when the sale happened, not when you uploaded it), the conversion value, a unique order ID for deduplication, and hashed email or phone.
Formatting is strict. Hashed values must use SHA-256, and phone numbers must be in E.164 format before hashing: a plus sign, the country code and no spaces, dashes or brackets. Upload "(416) 555-0123" instead of "+14165550123" and nothing will match. Hashing is exact, so one badly formatted field can quietly sink the match rate for a whole batch.
That last point breaks more setups than anything technical. A GCLID captured on the lead record but wiped when the lead converts to an opportunity or deal is the most common silent failure. Before automating anything, create a test lead from your own ad, walk it through every CRM stage by hand and check the field is still there at closed won.
The simplest option when leads come through a web form. The tag can detect form submissions and collect the email or phone number for hashing. Automatic collection works when your forms use standard field names. If it misses fields, point it at specific CSS selectors. If your form data is assembled by JavaScript rather than a normal HTML form, pass the values in through code.
Data Manager is Google's central place for connecting CRMs and data sources to Ads. You set up the connection once and it handles the recurring transfer, including flagging rows that fall outside the allowed time window. Google has been moving offline imports onto Data Manager, so if you still rely on spreadsheet uploads, this is the route to move to.
For businesses with developers who want conversions sent directly from internal systems in near real time. Each upload includes the GCLID, conversion action, conversion time, value, hashed user identifiers and order ID.
Zapier, HubSpot and similar tools can push closed deals to Google Ads without custom code. They work well for simple handoffs but often struggle when a GCLID has to survive several pipeline stages. Test against your real pipeline before trusting the numbers. Our guide to connecting your CRM to Google Ads goes deeper on this.
Don't switch bidding to the new action the same week you launch it. A messy first week of uploads can send Smart Bidding chasing bad data for weeks after you fix the problem.
Small daily uploads beat one large monthly upload, because Smart Bidding needs a steady signal.

Uploaded conversions usually take a few hours to appear. When validating against your CRM, use the "All conv. (by conv. time)" column, which reflects when the sale happened rather than when you uploaded it.
The enhanced conversions diagnostics report and the result file from each upload show exactly which rows failed and why. Read those before assuming the whole pipeline is broken. Often it is a handful of malformed phone numbers out of thousands of records.
The technical setup gets the attention, but it is rarely what breaks. The usual failures are operational: a sales team that doesn't know a hidden field exists, a CRM workflow that overwrites data when a deal changes stage, or a temporary spreadsheet export that never got automated. If you fix one thing first, make sure the GCLID and contact details survive your whole pipeline. A perfect tag feeding a CRM that drops the GCLID at stage two gives you the same result as no tracking at all.
Tech Business Development handles the full pipeline: tag or Data Manager setup, CRM field mapping and the automation that keeps identifiers intact through long sales cycles. See our services and pricing, or read our guide to Google Ads conversion tracking for the online side of the setup.
Sales or qualified actions that happen away from your website after an ad click, such as a phone sale, an in person purchase or a closed CRM deal. Importing them lets Smart Bidding optimize for revenue instead of clicks or form fills.
GCLID imports match only on the click identifier, which fails whenever it gets lost. Enhanced conversions for leads adds hashed email or phone as a second way to match, which catches many of those lost conversions.
Usually a few hours after processing. Bidding improvements take longer, typically a few weeks of steady uploads.