Back to guides

Enhanced Conversions CSV Preflight

Use this page for local user-data preflight only. It is not a Google Ads Data Manager schema validator, not an account setup check, and not a guarantee that enhanced conversions for leads will import or match.

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

Important boundary

Use the official Google Ads, Data Manager, Google Ads API, or other supported workflow for enhanced conversions for leads setup and final validation. This checker can only flag local CSV-level symptoms such as invalid email, suspicious phone values, plain pre-hashed fields, incomplete address data, missing identifiers, consent value issues, duplicate rows, and conversion-time risks.

Data Manager and official workflow boundary

Enhanced conversions for leads should be configured and validated in the official Google Ads workflow. This page only explains local CSV-level user-data risks that can be reviewed before final validation.

Scheduled/pre-hashed user-data upload

When a workflow expects pre-hashed user data, plain email, phone, first name, last name, and street address values should be treated as blockers until they are normalized and SHA-256 hashed.

Manual unhashed review

Some official manual review workflows may accept unhashed values, but this checker cannot confirm which account workflow will hash them. Plain values still need valid formatting, and invalid email or phone values should be fixed before Google Ads preview.

Broken SHA-256 hashes

A SHA-256 hex digest should be 64 hexadecimal characters. Short hash-like strings are often caused by truncation, wrong hashing code, missing normalization, or exporting the wrong CRM field.

Address-style user data

First name, last name, and street address may require hashing in pre-hashed workflows, while city, state, country, and postal code are location fields. Country or postal code alone is not a useful user identifier.

Consent fields

When your workflow uses consent signals, Ad User Data and Ad Personalization should use clear Granted or Denied values. Blank or unexpected values should be reviewed before previewing the file in Google Ads.

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.

Check before upload

The browser-local checker can flag email, phone, address hashing, consent values, hash-like values, missing identifiers, duplicate rows, and conversion-time issues without uploading your CSV to a server.

Open the checker