Troubleshooting 1 min read

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

MistakeResultFix
Used MD532-char hash (wrong length)Use SHA-256
Didn’t normalizeHash doesn’t match platformLowercase + trim first
Hashed twiceDifferent hash than expectedHash exactly once
Uppercase hexA8B14F... instead of a8b14f...Convert to lowercase
Sent raw emailNot a hash at allApply SHA-256
Included whitespaceExtra characters in hashTrim 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.

Frequently Asked Questions

Common causes: (1) Using MD5 instead of SHA-256, (2) Not normalizing before hashing (must lowercase and trim), (3) Hashing twice, (4) Uppercase hex characters in the hash, (5) Including whitespace in the hash. The hash must be a 64-character lowercase hexadecimal string.

Stop Guessing. Start Proving ROI.

TUOCA connects your CRM and call tracking data directly to your ad platforms. Set up in minutes.