SHA-256 Hash Generator for Enhanced Conversions & Meta CAPI
Check that your user data is normalised and hashed correctly before it goes to Google Ads or Meta. Everything runs in your browser.
For gmail.com and googlemail.com addresses, Google asks you to remove dots before the @ before hashing.
Why normalisation matters
Google and Meta match hashed customer data against their own users. A hash changes completely if one character is different, so "John@Gmail.com " and "john@gmail.com" give two different hashes and only one of them can match. Each platform has rules: lowercase and trim emails, phone numbers with the country code, and names in lowercase.
Google vs Meta differences
Google Ads expects phone numbers in E.164 format with a plus sign (+15551234567) and asks you to remove dots before the @ in gmail.com and googlemail.com addresses. Meta expects phone numbers as digits only, including the country code and without the plus sign, and names in lowercase with no punctuation. Use this tool to compare your own output with the expected value.
Frequently asked questions
Do I need to hash data myself?
Only when you send it hashed, for example through a server-side integration or the API. The Google tag and many GTM templates can hash for you if you pass the raw values in the user-provided data variable.
Is it safe to paste customer data here?
The tool runs entirely in your browser using the Web Crypto API. Nothing is sent to a server. Still, use test data where you can.
What is a good Meta Event Match Quality score?
Meta shows a score out of 10 for each event. Sending hashed email and phone, plus fbp, fbc, IP address and user agent, through the Conversions API is what usually raises it.
Ready to fix your tracking and scale your ads?
Get a free audit of your tracking and ad account. Usually replies within 1–2 hours.
