How to Track Offline Conversions in Google Ads (2026)

In 2026, you track offline conversions in Google Ads through offline conversion import, now most commonly implemented as its upgraded version, enhanced conversions for leads, which uploads a conversion record tied to a Google Click ID (GCLID) or hashed customer data (email, phone) so a sale that closes in-store, over the phone, or weeks after a form fill gets matched back to the ad click that generated the lead. This is a data-import feature for events that finish offline, distinct from call conversion tracking (which measures calls placed through your ads) and store-visit conversions (which estimates physical foot traffic from location history, not a confirmed sale).

How It Actually Works

• The click gets an ID. Every ad click Google Ads serves can carry a GCLID appended to the landing page URL.
• Your lead form captures it. A hidden form field (or the Google tag or Google Tag Manager) reads the gclid parameter, or your form captures hashed first-party data like email and phone at the moment of lead submission, per Google's enhanced conversions for leads documentation.
• The sale happens later, offline. Days or weeks pass while a rep closes the deal by phone, in a showroom, or in-store.
• You upload the result. You send Google Ads a record with the conversion action name, the conversion timestamp, the value, and either the GCLID or the hashed user data captured at lead time.
• Google Ads matches and attributes. The upload is matched to the original click, or to a signed-in Google user via the hashed data, and folded back into reporting and Smart Bidding signals.

What You Need Before You Upload

• A GCLID or user-provided data. Google requires each conversion event to include a conversion timestamp plus at least one of GCLID, user-provided data (hashed email or phone), or a BRAID.
• An import-type conversion action. Create one in Google Ads whose name matches your uploaded Conversion Name value exactly, including case.
• A timezone declaration. Offline conversion files need a Parameters row declaring the timezone all conversion timestamps are interpreted in.
• Hashed PII, not raw PII. Enhanced conversions for leads requires email and phone data to be hashed before it's sent.

Upload Methods and Timing Windows

• Data Manager is Google's current recommended path — a point-and-click interface inside Google Ads that no longer requires changes to your CRM or website code.
• Google Tag Manager or the Google tag can also capture and forward user-provided data automatically.
• Manual upload via spreadsheet or the Google Ads API is still supported for now, but not for much longer.

• 90-day window for GCLID-based imports. A standard offline conversion tied to a GCLID must be uploaded within 90 days of the click.
• 63-day window for enhanced conversions for leads. Conversions matched by hashed user data must be uploaded within 63 days of the associated last click or they won't import.

Why It's Not the Same as Call or Store-Visit Tracking

Offline conversion import is the umbrella mechanism for any conversion that starts with an ad interaction and finishes off-platform. Within that umbrella, Google Ads treats a few event types differently: call conversions use a separate upload type built specifically for tracking outcomes of calls placed through your ad's call extension or forwarding number, and store-visit conversions are a separate, advanced feature that estimates physical foot traffic using aggregated location history rather than reporting a confirmed sale value. If what you're trying to report is a closed deal, a signed contract, or an in-store purchase amount, offline conversion import through GCLID or enhanced conversions for leads is the correct tool, not those two.

Bottom Line

If you generate leads through Google Ads and close them later by phone or in person, set up enhanced conversions for leads through Data Manager now: it replaces manual GCLID spreadsheet uploads with hashed first-party data matching, and it's the path Google is steering all offline conversion tracking toward before the June 15, 2026 API cutoff.