Step 1
Parse the CSV locally
The checker reads the selected CSV in the browser, handles UTF-8 BOM, detects a header row, checks row width, and reports malformed quote or delimiter structure before value-level validation starts.
CSV Check Methodology
This page documents how the local checker reviews a Google Ads offline conversion CSV. It is written for PPC operators, agencies, and data teams that need to explain why a row was flagged before previewing the file in Google Ads.
Last updated: June 6, 2026. Re-check the official Google Ads documentation before changing production import workflows.
Validation pipeline
Step 2
Identify the workflow
Validation changes depending on whether the file is a click-ID upload, scheduled/pre-hashed user-data upload, or manual unhashed review. The selected workflow controls how identifiers, hashes, and plain user data are interpreted.
Step 3
Validate row-level risks
Each row is checked for conversion name, conversion time, timezone context, click identifiers, user-provided data, consent fields, conversion value, ISO currency code, Order ID, and duplicate conversion keys.
Step 4
Return a fix-oriented report
Findings are grouped by severity and exported with row number, field, current value, issue, and suggested fix so the CSV owner can correct the source export before using Google Ads preview.
Severity model
Severity is assigned from the expected impact on upload preview, matching quality, reporting accuracy, and workflow safety. It is not a final Google Ads account decision.
| Severity | Meaning | Examples |
|---|---|---|
| Critical | Rows likely to fail upload, fail matching, or need workflow review before preview. | Missing conversion time, missing conversion name, invalid time, missing usable identifier, invalid pre-hashed user data. |
| Warning | Rows that may import but deserve operator review because reporting or match quality can degrade. | Old conversion time, timezone-less timestamp, suspicious phone value, duplicate Order ID, non-standard value shape. |
| Info | Contextual findings that help clean the file but are not immediate blockers. | Recognized optional columns, local-only limitations, or workflow reminders. |
Privacy boundary
CSV parsing and validation run in the browser. The checker does not upload the selected file, file name, row values, click IDs, email addresses, phone numbers, Order IDs, search text, or conversion values to a server. Aggregated product events may be recorded as described in the privacy policy.
What this local checker cannot verify
The checker reads a CSV in your browser and reports file-level risks. It does not connect to Google Ads, Data Manager, Google Ads API, your CRM, or your account. It cannot confirm conversion action ownership, click ownership, account permissions, customer data terms, Data Manager schema rules, template compatibility for every file format, import preview status, or final attribution. Always preview and validate the corrected file in the official Google Ads workflow.
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.
- Google Ads Help: Import conversions from ad clicks using files
Used for file-level timezone parameters, supported conversion time formats, file import boundaries, and scheduled upload hashing notes.
- Google Ads Help: Guidelines for importing offline conversions
Used for upload timing windows, old conversion review signals, and final Google Ads validation boundaries.
- Google Ads Help: About enhanced conversions for leads
Used for the enhanced conversions for leads and Data Manager boundary.
- Google Ads API: Manage offline conversions
Used for API-style offline conversion and hashed user-provided data context.
- Google Ads Help: Enhanced conversions for leads diagnostics report
Used for user-provided data hashing, normalization, and match-quality diagnostics context.