← Back to checker

Google Ads Offline Conversion CSV Checker FAQ

Common questions about privacy, independence, scope, supported files, and what this Google Ads offline conversion CSV checker can and cannot verify.

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

Is my CSV uploaded to your server?

No. The file is processed locally in your browser. The checker does not upload your CSV file to a server and does not store row data.

Is this an official Google tool?

No. This is an independent CSV preflight checker. It is not an official Google product and is not affiliated with Google.

Can this guarantee my Google Ads upload will succeed?

No. It checks CSV-level issues only. Google Ads account settings, conversion action ownership, click ownership, MCC permissions, customer data terms, and final attribution must still be checked inside Google Ads.

Does it support Enhanced Conversions for Leads?

It supports local CSV-level checks for user-provided data risks, such as invalid email format, suspicious phone values, plain-text values in pre-hashed workflows, incomplete address data, consent values, and invalid SHA-256 hash-like values. It is not a Google Ads Data Manager schema validator, account setup checker, or final matching validator.

Can it fix my CSV automatically?

The first version generates a report and clear suggested fixes. Auto-fix and hash-export workflows are intentionally kept out of the MVP.

What file types are supported?

The MVP supports UTF-8 CSV files with a header row, comma delimiter, and a 10MB browser-side file limit. Google Ads supports additional template formats, but XLSX files and Google Sheets URLs are not supported in this checker.

Official sources used

These links support the page boundary and the local checks described here. They are not copied into the checker as a complete Google Ads validator, and the checker should not be described as official Google guidance.