Hash an email, phone number or name the way Google or Meta wants it, or hash a whole customer list. Everything stays in your browser. Nothing you type leaves this page.
Nothing you type leaves this page. Hashing runs in your browser, and this page sends us no values.
SHA-256 hash
d6117306485ed0e50afab3ac871e98f81699151f30281527d63ff5f233656c69Each platform has its own rules, so the same person can hash differently.
Sample shown. Type over it with yours.
Nothing you type or upload leaves your device. Hashing runs in your browser, using the Web Crypto API built into it. This page loads no ad tags and no session recording, and we only count that the tool was used, never what went into it. Check your browser’s network tab if you’d like to see that for yourself.
A hash only matches when both sides hash the same text, so normalize first. Customer Match and enhanced conversions want trimmed, lowercase values and E.164 phone numbers with the plus sign. Meta wants phone numbers with symbols removed. One stray capital or space gives a completely different hash.
| Rule | Applies to |
|---|---|
| Email: trim spaces and lowercaseGoogle Ads Help | Google, Meta |
| Gmail: remove dots before the @gmail.com and googlemail.com. Google Ads Help | |
| Gmail: remove the +suffixgmail.com and googlemail.com. Google Ads API | Enhanced conversions |
| Phone: E.164 with the + signLike +14155550123. Google Ads Help | |
| Phone: remove symbols and letters, keep the country codeLike 14155550123. Meta for Developers | Meta |
| Names: lowercase and trim spacesGoogle Ads Help | |
| Names: lowercase with no punctuationMeta for Developers | Meta |
| Output: lowercase hex, 64 charactersGoogle Ads API | |
| Country and Zip: don’t hashGoogle Ads Help | Customer Match |
| fbc and fbp: don’t hashMeta for Developers | Meta |
No. Hashing runs in your browser through the Web Crypto API, and nothing you type is sent to us or anyone else. This page loads no ad tags and no session recording, and we only count that the tool was used. Load the page, go offline, and it still works.
Trim the spaces, lowercase the address, and remove the dots before the @ in gmail.com and googlemail.com addresses. Then hash it with SHA-256 and use the hex output. That’s Google’s own list. You can also upload plain text, and Google Ads hashes the file on your computer first.
Not always. Enhanced conversions also removes the +suffix from gmail.com and googlemail.com addresses, and Google says those email rules differ from how Customer Match handles variations. So jane+news@gmail.com hashes differently between the two. Other domains come out the same, so pick the right target before you hash.
Google needs the exact English headers Email, Phone, First Name, Last Name, Country and Zip. Matching on a mailing address needs the last four together. Country and Zip stay unhashed. The Customer list tab keeps those names, hashes the first four columns and leaves everything else as it is.
Treat it as personal data. The US Federal Trade Commission says hashing doesn’t make data anonymous, because common identifiers like emails can be guessed and hashed again to find a match. Hashing protects the value on its way to the platform. Your consent and data rules still apply to the list.
One changed character gives a completely different hash. The usual causes are a capital letter, a trailing space, a phone number with no country code, or hashing a value twice. Compare the Hashed as line here with what your system hashes. An uppercase hex string also fails a plain text comparison.
SHA-256 is a one-way hash function. It turns any text into a fixed 64-character hex string, and the same text always gives the same string. You can’t run it backwards with a formula, which is why ad platforms use it to match customer lists without being handed plain emails.
Hashing by hand is fine for a test. For a repeatable feed, our Google Ads conversion tracking work builds it at a fixed price.
Paste this where you want it. It stays free and sends no tracking from your site.
<iframe src="https://www.martechdevs.com/embed/sha256-hasher" title="SHA-256 hasher" width="100%" height="860" style="border:0;max-width:760px" loading="lazy"></iframe>
<p style="font-size:13px">Free tool by <a href="https://www.martechdevs.com/tools/sha256-hasher">martechdevs</a></p>Last updated
Set up Google Ads enhanced conversions with current web, CRM and Data Manager requirements. Verify hashing, consent, delivery coverage and diagnostics.
Jafrin Akter AloLast updated 11 min read
Build warehouse audiences for Google Ads, Meta and HubSpot with clear entry and exit rules, marketer self-serve guardrails and honest match-rate checks.
Jafrin Akter AloLast updated 18 min read
Send qualified leads and customer outcomes back to ad platforms. Design stable IDs, consent handling, upload monitoring and a controlled bidding rollout.
Jafrin Akter AloLast updated 15 min read
Want it set up for you? See implementation plans or book a free call.