Customer Data Hasher

Convert email / phone / name lists to SHA-256 — ready for Google Customer Match, Meta CAPI, or offline conversion uploads. Runs entirely in your browser.

Header optional. Columns: email, phone, first_name, last_name.

How normalization works

  • Email: lowercased, trimmed.
  • Phone: stripped to digits + leading +; double-zero international prefix becomes +.
  • Name: lowercased, trimmed, accents stripped (Google + Meta convention).
  • All hashes are computed locally — your data never leaves the browser.

Hashed output (0 rows)

Hashed values appear here.

Want this automated?

We wire up server-side jobs that hash + push customer data to Google Customer Match and Meta CAPI on a schedule, with deduplication and consent honoring built in.

INTERACTIVE DEMO Want to test how this tool works?
Save these results as a PDF report A clean, branded copy to share with your team or client.
Free PDF report

Where should we put your name on the report?

Your PDF downloads straight away. Your tool data never leaves your browser.

Jobair Mahmud, Web Analytics & Tracking Architect
Tool Creator

Jobair Mahmud

Founder & Tracking Architect

100% Top Rated
5.0 / 5.0

Need automated data hashing in your GTM container?

I build custom GTM client templates and server-side transformation variables that normalize and hash user data on the fly.

Consult with Jobair →

How to use the Client-Side Customer Data Hasher (SHA-256)

Advertising platforms like Meta CAPI, Google Enhanced Conversions, and TikTok Events API require customer identifiers to be hashed using the SHA-256 cryptographic algorithm. This utility normalizes and hashes strings 100% locally in your browser memory without transmitting any data over the network.

Step by step

  1. Select the data type: Email, Phone Number, First Name, Last Name, or Postal Code.
  2. Enter the raw user string (e.g., " John.Doe@Domain.com ").
  3. The tool automatically normalizes the input: strips whitespace, converts to lowercase, and formats phone numbers with international country codes.
  4. Copy the resulting 64-character hexadecimal SHA-256 hash string for tag validation or testing.

How to read your result

Valid SHA-256 Hash Generated

Properly formatted 64-character hexadecimal string ready for Meta CAPI, Google Ads, or TikTok payload insertion.

Common mistakes

  • Hashing email addresses with uppercase letters (e.g., User@Domain.com), which produces a completely different hash that fails platform matching.
  • Including spaces before or after email or phone strings before hashing.
  • Hashing phone numbers without international country codes (e.g., "12345678" instead of "+112345678").

Questions

Does any personal data leave my computer?

No. This tool uses the native Web Cryptography API (crypto.subtle.digest) inside your browser. No data is sent to any server.

Why is normalization critical for SHA-256 hashing?

SHA-256 is a one-way deterministic algorithm. Changing even one lowercase letter to uppercase or adding a single trailing space results in an entirely different hash, causing a 0% match rate.

Need automated data hashing in your GTM container?

I build custom GTM client templates and server-side transformation variables that normalize and hash user data on the fly.