Blog
AdSpend and Insights

Google Ads Offline Conversions: How to Track Sales That Close Off Your Website

How to send phone sales, in person purchases and closed CRM deals back to Google Ads so Smart Bidding optimizes for revenue instead of form fills.
Shayan Shirvani
September 18, 2026

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.

What offline conversions are and why they matter

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:

  • Phone sales from a tracked number
  • In person purchases at a clinic, dealership or counter
  • CRM deals marked closed won weeks after the first enquiry
  • Quote requests that turn into signed contracts

How Google matches an offline sale to an ad click

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:

  1. Someone clicks your ad and the GCLID is added to the landing page URL.
  2. The Google tag or Google Tag Manager stores it, usually in a hidden form field or a first party cookie.
  3. The form submission sends the GCLID into your CRM with the lead.
  4. Your team works the lead and the outcome is logged in the CRM.
  5. An automation or export sends the closed deal to Google Ads as a conversion.

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.

What to set up before you start

  • Turn on auto tagging. Without it, Google never adds a GCLID to your URLs and there is nothing to capture.
  • Create a conversion action for imports. It needs to accept click based imports, or be set up for enhanced conversions if you are layering them onto an existing form fill action.
  • Opt in to enhanced conversions for leads and accept the customer data terms. The setting sits inside the conversion action, which is why many accounts miss it.
  • Pick your match key in the CRM. Decide whether the GCLID, email or phone number reconnects a closed deal to the click, and confirm that field survives every stage of your pipeline.

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.

Which upload route fits your systems

Google tag or Google Tag Manager

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.

Google Ads Data Manager

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.

Google Ads API

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.

Third party connectors

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.

Launch checklist

  1. Create or confirm the conversion action, opt in to enhanced conversions for leads and choose your match key.
  2. Install the Google tag or GTM and confirm it captures the GCLID on a real form submission.
  3. Update the CRM so the GCLID and contact details carry through to the opportunity or deal.
  4. Connect Data Manager or the API, upload a test batch of five to ten records and read the result file for rejected rows.
  5. Run the new action for at least four weeks before making it your primary bidding conversion.

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.

Habits that improve match rates

Small daily uploads beat one large monthly upload, because Smart Bidding needs a steady signal.

Offline conversion upload habits diagram

  • Upload on a fixed schedule. Daily is ideal. Anything slower than weekly weakens bidding.
  • Use an order ID so the same deal isn't counted twice across overlapping batches.
  • Set counting to "one" for single sale events like a signed contract and "every" only for repeat purchases.
  • Send more than one identifier when you have it. Email plus phone matches better than email alone.
  • Respect the lookback window. Google rejects conversions that arrive too long after the click. If your sales cycle runs long, upload an earlier stage (such as a qualified lead) as its own conversion rather than waiting for the final close. Check Google's current limits before you plan around them.
  • Record consent for the customer data you hash and upload.

Troubleshooting upload errors

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.

  • CLICK_NOT_FOUND: the GCLID doesn't match a recorded click, usually because it was captured incorrectly or falls outside the lookback window.
  • INVALID_CONVERSION_ACTION_TYPE: the conversion action isn't set up to accept click based imports.
  • Date and time mismatches: usually a timezone problem between your CRM export and your Google Ads account.
  • Duplicates: the same deal appears in two batches without a consistent order ID.

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.

What matters most

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.

Get it set up properly

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.

FAQ

What are offline conversions in Google Ads?

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.

What is the difference between enhanced conversions for leads and GCLID imports?

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.

How long before offline conversions show up?

Usually a few hours after processing. Bidding improvements take longer, typically a few weeks of steady uploads.

Share this post
Shayan Shirvani
Founder, Tech Business Development