Common Issues with Offline Conversion Imports in Google Ads and How to Fix Them

Diagnosing and fixing the top issues

1. Missing or malformed click IDs

Symptoms: low or zero match rate on uploads, or most imports flagged as "Unmatched." Root causes often include missing URL parameters, improper form handling, or server-side stripping of query params. Fixes:

• Ensure gclid or mobile click IDs are appended by Google Ads and accepted in your landing page scripts.
• Persist the click ID server-side (session cookie or hidden form field) immediately on first hit.
• Verify backend storage truncation limits; gclid is ~100 characters in some auto-tagging contexts - store as varchar(255) or text.

2. Time windows and timezone mismatches

Google Ads requires that the click timestamp and the offline conversion timestamp fall within the conversion action's lookback window. If your sales cycle is long (30+ days), configure the conversion action to accept a longer window. Also confirm timezone alignment - using UTC inconsistently can shift dates and cause mismatches.

3. Formatting errors on upload

Common CSV issues include incorrect headers, date formats, or missing required columns (Google requires conversion name, timestamp, gclid/hash, and conversion value for revenue imports). Use the BigQuery or API upload when CSV repeatedly fails. Example date format expected: 2023-10-15 14:23:05 (YYYY-MM-DD HH:MM:SS) in account timezone.

4. Low match rates due to privacy and hashing

When using hashed customer data (email, phone), ensure you use SHA256 hashing as required and normalize values (lowercase emails, strip non-numeric characters from phone numbers). If match rates drop after iOS or Android changes, rely more on server-side click ID persistence and hybrid matching strategies. For US ecommerce stores on Shopify, confirm your checkout does not strip identifying parameters before redirecting to external payment processors like Stripe.

5. Attribution and deduplication conflicts

If you import the same offline conversion multiple times or have parallel online conversion tags, Google may deduplicate differently than your internal reports. Map your business logic: decide which event represents the authoritative conversion (lead vs closed sale) and use unique order IDs in uploads so deduplication is deterministic.

Practical checks and a remediation checklist

• Verify gclid capture on the first server hit and store with lead/order.
• Confirm conversion action settings: lookback window, timezone, and value type.
• Validate CSV headers, timestamp format, and no trailing spaces in conversion names.
• Use SHA256-hashed identifiers with consistent normalization if matching on email/phone.
• Test uploads in a staging account or use small sample sets before full imports.

For many scaling brands, automated ETL pipelines that pull CRM events, enrich them with persisted click IDs, and write to BigQuery before programmatic upload reduce manual formatting errors. Prebo Digital builds data-forward solutions that combine server-side tracking and ETL to improve match rates and attribution clarity - explore the homepage for our methodology. Prebo Digital home

Example troubleshooting scenario (US SaaS sales)

Scenario: A US B2B SaaS company sees only 30% match rate on offline closed-won imports. Steps taken:

• Confirmed gclid present at form submit and stored in CRM.
• Discovered sales team manually recreated leads in CRM, losing gclid - implemented required field enforcement and a middleware to preserve gclid during manual edits.
• Adjusted conversion action lookback to 90 days to match a typical 45-60 day sales cycle (examples in the US often span multi-week procurement processes).
• Moved to automated BigQuery pipeline to standardize timestamps and ensure timezone parity.

After these changes the match rate rose from ~30% to an estimated 75% within four weeks. Note: these figures are examples and will vary by business; they are provided as an illustrative US scenario, not guarantees.

When to escalate to a specialist

Escalate if you see persistent low-match rates after fixing capture and format issues, or if your business requires cross-account or cross-platform attribution (e.g., combining Google Ads with Meta/LTV modelling). A technical-first partner can audit server-side tagging, implement robust ETL, and align conversion definitions across tools.

For specifics on build-and-scale processes that pair with offline conversion imports, review our services overview for analytics, tracking, and data engineering offerings. Services overview

Sources

• Google Ads Help - Upload conversions using offline data
• Google Ads API - Offline Conversion Tracking guide
• Google Ads Help - Improve match rate for offline conversions