Start with critical issues
Critical issues usually indicate rows that may fail import or match poorly, such as missing identifiers, missing conversion names, invalid conversion times, or broken user data values.
CSV only · up to 10MB · browser-local validation.
Use an explicit workflow when your headers include both click IDs and user-provided data, or when hashing requirements differ between scheduled/pre-hashed and manual unhashed review.
No Google Ads login required. Your file stays in your browser.
Download fresh sample CSV files
Generated with relative dates so examples stay useful over time.
Preview will appear after validation.
The first result card will show the selected or inferred workflow, critical issues, warning count, rows without detected critical issues, and the report download action.
Independent local CSV preflight checker
Upload a CSV locally in your browser to check headers, conversion time formats, GCLID, GBRAID, WBRAID, user-data hash risks, consent fields, conversion value, currency, duplicate rows, and common Google Ads import risks before previewing the file.
Browser-local processing: your CSV is not uploaded to our server. This independent tool focuses on CSV-level checks and does not verify Google Ads account settings, conversion ownership, or final import results.
CSV upload preflight guide
This free checker is designed for advertisers, PPC operators, agencies, and local service teams that prepare offline conversion imports. It focuses on CSV-level risks that are easier to catch before opening Google Ads: missing columns, malformed rows, invalid conversion timestamps, weak identifiers, duplicate conversion records, consent values, ISO currency issues, and user data formatting issues.
The checker scans the structure and values in your CSV, then groups findings by severity so you can fix the riskiest rows first.
For a deeper troubleshooting walkthrough, read the Google Ads offline conversion upload error guide.
The tool auto-detects common Google Ads offline conversion, click-ID upload, and user-data preflight fields. Column names do not have to be perfect, but recognizable headers make the report more useful.
Use the offline conversion CSV template checklist to review required identifiers, conversion names, timestamps, values, currency codes, and Order IDs before import.
Workflow first
The same CSV column can mean different things depending on the upload workflow. Pick the closest path before interpreting critical issues and warnings.
Use this path when rows contain GCLID, GBRAID, or WBRAID values and the file is intended for a click-based offline conversion import.
Use this path when rows contain email, phone, name, street address, consent fields, or SHA-256 hash-like values for user-provided data review.
Use this path when you need a final checklist for headers, conversion names, timestamps, values, currencies, Order IDs, and duplicate rows.
The checker is intentionally scoped to file-level preflight validation. It does not score campaigns, connect to Google Ads, or make final attribution decisions.
Parse CSV structure locally in the browser
Apply the selected workflow rules
Flag row-level risks by severity
Export a fix-oriented issue report
Critical issues usually indicate rows that may fail import or match poorly, such as missing identifiers, missing conversion names, invalid conversion times, or broken user data values.
Warnings can still matter for match quality and reporting accuracy. Check old click IDs, timezone-less timestamps, suspicious phone values, duplicate Order IDs, and unusual value or currency fields.
The issue report contains the row number, field, message, current value, and suggested fix. Use it as a working checklist before you preview the corrected file in Google Ads.
This checker does not connect to Google Ads, does not use OAuth, and does not call the Google Ads API. It cannot verify conversion action ownership, account-level settings, click ownership, MCC permissions, customer data terms, Data Manager schema rules, import preview status, or final attribution. Treat it as a local CSV smoke test, then preview the corrected file in Google Ads before applying the upload.
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.
Used for file-level timezone parameters, supported conversion time formats, file import boundaries, and scheduled upload hashing notes.
Used for upload timing windows, old conversion review signals, and final Google Ads validation boundaries.
Used for the exactly-one click identifier boundary in API-style click conversion rows.
Used for the enhanced conversions for leads and Data Manager boundary.
Used for the template and file-format boundary. This checker focuses on CSV preflight and does not support every Google Ads template format.
Common questions about privacy, scope, and enhanced conversions support.
No. CSV parsing and validation happen locally in your browser. The checker does not upload your file to a server or store row-level conversion data.
No. This is a CSV-level preflight checker. Google Ads can still reject or ignore rows because of account settings, conversion action ownership, click ownership, customer data terms, or attribution eligibility.
It can flag CSV-level user-data risks such as plain-text emails, suspicious phone values, address hashing issues, missing identifiers, invalid consent values, and broken SHA-256 hash-like values. It does not replace Google Ads Data Manager or final Google Ads preview validation.