Enhanced Conversions for Leads CSV Errors
Use this guide to review user-provided data problems before importing enhanced conversions for leads.
Plain-text email values
If your upload workflow expects hashed user-provided data, plain email addresses should be normalized and hashed before upload. The checker flags plain-text email values so you can review the workflow before importing.
Phone formatting issues
Phone values should be consistently normalized. When plain text is used, E.164-style formatting is usually easier to audit. Suspicious phone values such as words, short numbers, or broken strings should be fixed before upload.
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, or exporting the wrong CRM field.
Missing identifiers
Every row should include at least one useful identifier such as a click ID, email, phone, or address-style user data. Rows with no identifier cannot be matched reliably.
Address-style user data
If you use name and address fields, include country and postal code when available. Partial address data is harder to match and should be reviewed before import.
Check before upload
The browser-local checker can flag email, phone, hash-like values, missing identifiers, duplicate rows, and conversion-time issues without uploading your CSV to a server.
Open the checker