The same-looking email can produce two different, valid SHA-256 hashes when two upload paths normalize it differently before hashing. A digest matches only when the exact bytes supplied to SHA-256 match. For Google Ads enhanced conversions, the documented email rules include trimming whitespace and lowercasing, plus additional transformations for Gmail and Googlemail addresses. Those are Google enhanced-conversion rules—not a universal way to rewrite email addresses.
How can one email produce two different hashes?
Hashing does not recognize that two strings represent the same mailbox. It processes bytes. A change in capitalization, whitespace, punctuation, encoding, or any other input byte changes the SHA-256 result. Two conversion-upload implementations can therefore produce different hashes without either having a faulty SHA-256 function: they may have fed it different normalized inputs.
As an Amazon Associate I earn from qualifying purchases.
When comparing paths, inspect the value after normalization and immediately before hashing. Compare those exact bytes first; comparing digest strings alone cannot identify the cause.
What does Google Ads require for enhanced-conversion email?
Google Ads API guidance for enhanced conversions says to remove leading and trailing whitespace and convert email text to lowercase. It also specifies additional steps for addresses whose domain is gmail.com or googlemail.com: remove periods from the username and remove the plus sign and everything after it from the username before hashing. For other domains, keep periods and plus suffixes. Apply SHA-256 after the applicable normalization. See Google’s online click conversion guidance.
#1 Best Overall
| Input | Google enhanced-conversion normalization | What changes |
|---|---|---|
[email protected] |
[email protected] |
Lowercase; remove username periods and the plus suffix. |
[email protected] |
[email protected] |
Lowercase; retain the period and plus suffix because this is not a Gmail or Googlemail domain. |
These examples describe Google’s documented enhanced-conversion behavior, not a general email-canonicalization standard. Google’s guidance distinguishes these instructions from its handling of email variations for Customer Match. Do not assume that another Google product—or another platform—uses the same transformations.
How should you check two upload paths?
Compare each implementation against the documentation for its precise destination, conversion product, and API workflow. A useful review follows the value from the original field through normalization, encoding, hashing, and upload.
- Identify the destination and use case. Record the platform, conversion product, API service, and relevant API version for each path. Similar-looking uploads may have different rules.
- Inspect normalization in order. Check trimming, lowercasing, and any domain-specific punctuation or suffix handling. Verify that each transformation is documented for that exact workflow.
- Compare the hash input bytes. Check the character encoding as well as the visible string. Identical-looking text can still differ at the byte level.
- Verify the fields and hash count. Confirm which fields the platform requires hashed and which must remain unhashed. Check whether the value is hashed once or accidentally hashed a second time.
- Trace where hashing occurs. Determine whether data is hashed in the client, application, or another stage before API upload, and compare the value at the actual upload boundary.
- Check account setup and diagnostics. For Google enhanced conversions, confirm acceptance of customer data terms and review import diagnostics; a hash mismatch is not the only possible setup or upload issue.
Google’s API guidance describes normalizing and hashing user-provided data, placing identifiers in conversion adjustment objects, uploading them through the relevant service, and reviewing import diagnostics. It lists email, phone number, first name, last name, and street address as fields to hash with SHA-256; country, state, city, and ZIP code should not be hashed. Phone numbers should be formatted using E.164. These field rules belong to the Google conversion-upload context.
Google’s official lead-upload sample provides normalization and SHA-256 implementation examples. Treat it as an implementation reference for its demonstrated workflow and version, not as a substitute for checking the production path’s current documentation.
Can you apply Google’s email rules to another platform?
No. A Conversions API direct-integration playbook hosted on Google Cloud Storage describes SHA-256 hashing with UTF-8 for matching customer-information parameters and distinguishes fields such as user agent that should not be hashed. But that playbook does not establish Meta’s current official status or current email-specific normalization requirements. It is not evidence that Meta uses Google’s Gmail-specific period and plus-suffix behavior. Check the current Meta documentation for the exact API and event type before relying on a rule.
Google’s explanation of enhanced conversions describes the feature as using hashed first-party conversion data; it does not make Google’s normalization instructions universal across products or platforms. See About enhanced conversions.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.When should you call a hash wrong?
Do not label a digest incorrect just because it differs from another upload path’s digest. First establish that both implementations target the same platform workflow, apply the same documented normalization, encode the result identically, and hash the same field exactly once. If the pre-hash bytes match but the digest does not, investigate the hashing implementation. If they differ, the difference lies earlier in the pipeline.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
