Invalid Hashed Email Error in Google Ads Enhanced Conversions
Last verified: 2026-11-05
Google Ads rejects hashed email with INVALID_USER_IDENTIFIER when the SHA-256 hash doesn’t meet format requirements.
Valid Hash Format
A valid SHA-256 hash is:
- Exactly 64 characters long
- Contains only lowercase hex characters (0-9, a-f)
- Is the result of one SHA-256 hash operation
- Was computed from a normalized email
Common Mistakes
| Mistake | Result | Fix |
|---|---|---|
| Used MD5 | 32-char hash (wrong length) | Use SHA-256 |
| Didn’t normalize | Hash doesn’t match platform | Lowercase + trim first |
| Hashed twice | Different hash than expected | Hash exactly once |
| Uppercase hex | A8B14F... instead of a8b14f... | Convert to lowercase |
| Sent raw email | Not a hash at all | Apply SHA-256 |
| Included whitespace | Extra characters in hash | Trim the hash output |
The Correct Pipeline
Raw: " John@EXAMPLE.com "
Step 1: "john@example.com" ← Trim + lowercase
Step 2: SHA-256 hash
Step 3: "fd876f5e45d2e29f..." ← 64-char lowercase hex
Verify with the SHA-256 Hasher tool.
TUOCA Prevention
TUOCA normalizes and hashes automatically. You provide raw emails; TUOCA handles normalization and hashing per platform requirements.