Steps to Set Up Offline Conversion Tracking in Google Ads

Why offline conversion tracking matters for US advertisers

Offline conversion tracking in Google Ads lets you import sales and lead outcomes that happen outside the browser - phone calls, point-of-sale purchases, or closed deals from your CRM. For Shopify and WooCommerce stores using phone orders or B2B teams closing leads offline, mapping those events back to ad clicks improves attribution accuracy and helps optimize toward profitability rather than surface-level metrics.

Key outcomes this setup supports

• More accurate ROAS and MER by attributing revenue to ad interactions.
• Reduced wasted ad spend when campaigns are optimised on true revenue.
• Better bidding signals for automated strategies by feeding real conversions.

High-level steps to set up offline conversion tracking in Google Ads

Below is the step sequence. Each step includes implementation notes for US eCommerce and B2B workflows, plus suggested instrumentation (GA4, server-side, CRM ETL).

1. Identify offline conversion events and schema

Define what counts as an offline conversion: phone sale, store pickup, qualified CRM opportunity, or an offline subscription. Standard fields to capture: conversion time (UTC), conversion value (use $ in examples), currency, Google click identifier (GCLID) or Google Ads click ID (gclid), and optionally customer identifiers (email hash, phone hash) for deterministic matching.

2. Capture click identifiers at the moment of the ad click

When a user clicks an ad, record the gclid or store a hashed email/phone tied to the session. For Shopify stores, append gclid to checkout and save it to the order meta. For server-side measurement, forward identifiers to your server endpoint using GA4 or a custom endpoint. See the team approach in our services overview for instrumentation options.

3. Persist identifiers in your systems

Persist gclid (or hashed identifiers) in your CRM, order records, or POS. Typical pattern: session -> checkout -> order/lead record. If the sale closes offline days later, you still have the link to the original click. For implementation patterns and developer workflows, review our agency approach to tagging and data pipelines.

Technical options and architecture patterns

Choose between a direct Google Ads upload, server-side conversion uploads, or an ETL that imports CRM closed-win records into Google Ads. Each option balances complexity, match rate, and privacy controls.

Conversion tracking diagram (simple flow)

Click → capture gclid/email hash → persist in checkout/CRM → offline sale closes → extract record with gclid → upload to Google Ads API or CSV.

Visual (text) diagram:

Compliance and US privacy considerations

In the United States, ensure consent and cookie notices reflect your use of identifiers and server-side forwarding. For California residents, consider CCPA data subject requests when storing customer identifiers. When hashing emails/phones for matching, use secure one-way hashes and document retention policies.

For implementation guidance across analytics and tracking, see our homepage for service alignment and technical capabilities: Prebo Digital homepage.

Step-by-step implementation: CSV vs API

Choose CSV uploads to Google Ads when you need a simple, manual method. Use the Google Ads API for automated, scheduled imports. The API supports higher volumes and lower latency, which is preferable for ongoing retainer work and fast feedback loops on campaign performance.

CSV upload checklist

• Columns: Google Click ID (gclid), conversion_name, conversion_time (UTC), conversion_value, currency.
• Timestamp accuracy: use ISO 8601 format where possible.
• Validation: run a small test file (5-10 rows) and confirm match rates in Google Ads.

API upload checklist (server-to-server)

• Authenticate with OAuth or service account as required.
• Batch conversions and include deterministic identifiers (gclid or hashed email/phone).
• Monitor response codes and implement retry logic for transient failures.

Attribution, reporting, and testing

Once offline conversion tracking is feeding Google Ads, evaluate attribution windows and conversion action settings. Start with a 90-day lookback for B2B deals and shorter windows for eCommerce transactions. Compare Google-reported conversions to server-side revenue to measure match rate and adjust the pipeline where identifiers are missing.

Funnel breakdown (TOF → MOF → BOF)

• TOF (Top of Funnel): Paid search and social driving awareness - capture click identifiers.
• MOF (Middle of Funnel): Qualification and engagement - persist identifiers in CRM and email systems.
• BOF (Bottom of Funnel): Offline close or in-store conversion - upload final conversion to Google Ads.

Common pitfalls and troubleshooting

• Missing gclid in orders: ensure URL parameter persistence across redirects and payment gateways.
• Low match rates: verify hashing algorithm consistency and time zone mismatches.
• Attribution conflict: align conversion actions in Google Ads and GA4 to avoid double-counting.

If you want to see a real-world example of a server-side implementation and ETL approach, our services outline includes tracking, GA4, and server-side options that are commonly used by US stores and B2B teams.

Measurement hygiene and next steps

Track match rate, conversion value accuracy, and time-to-close. Periodically reconcile Google Ads conversions against CRM revenue (sample-based) to estimate attribution accuracy. Use server-side tracking for improved persistence and pair it with hashed identifiers when storing customer data.

For teams looking to formalize this into a recurring growth system, consider integrating the workflow with monthly reporting, experiment design for bidding changes, and CRO work on BOF flows. Learn how Prebo Digital approaches scaling measurement and growth in our contact resources: talk to a tracking expert.

Final checklist before you go live

• Confirm gclid persistence across checkout and stored in order/CRM.
• Test a small batch upload and inspect match rate in Google Ads.
• Document retention, hashing approach, and privacy notices per US requirements.

Sources

• Google Ads Help - Import conversions from clicks (offline conversions)
• Google Ads API - Offline Conversion Uploads
• GA4 Measurement Protocol and server-side best practices
• California CCPA Overview (official resource)