Google Ads Offline Conversion CSV Guides

Short, practical guides for checking CSV structure, timestamps, click identifiers, user-data fields, and template risks before Google Ads preview.

Last updated: June 6, 2026. Re-check the official Google Ads documentation before changing production import workflows.

Start here

Start here when Google Ads preview fails or a CSV export looks risky.

PPC operators and agencies troubleshooting an upload

Use this when rows have timezone, future-date, old-click, or unparseable time warnings.

CRM, analytics, and operations teams exporting conversion times

Use this for local email, phone, address, consent, and hash preflight checks only.

Teams using user-provided data or enhanced conversions workflows

Use this when you need to explain how severity, workflow selection, and privacy boundaries are applied.

Agencies, PPC leads, and data owners documenting review steps

Fix common CSV upload problems before import.

Use when the file fails preview or has many row-level issues.

Format conversion timestamps, time zones, Parameters:TimeZone rows, and date values before upload.

Use when rows are timezone-less, future-dated, or too old.

Choose the right click identifier columns and avoid mixed click-ID rows.

Use for click-ID upload or API-style click conversion workflows.

Review columns, dates, values, ISO currency codes, consent fields, and identifiers.

Use before sending a cleaned export to Google Ads preview.

Check email, phone, address hash, consent, and user-data issues without treating this as a Data Manager schema validator.

Use for local user-data field review, not final ECL validation.