Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Glossary term

Hashing

Converting an identifier such as an email address into a fixed string with a one-way function, so platforms can match records without the raw value.
AnalyticstechnologyUpdated

Definition

A hash function takes an input of any length and returns an output of fixed length. It is deterministic, so the same input always gives the same output, and it is one-way: there is no practical way to compute the input from the output alone. Change one character of the input, a capital letter or a trailing space, and the output is completely different.

In marketing measurement the inputs are first-party identifiers: email addresses, phone numbers, sometimes names and postal details. Each platform specifies the hashing function and the normalisation rules it expects; Google's help centre describes enhanced conversions as supplementing conversion tags with hashed first-party data, and Meta's documentation of the Conversions API lists which customer fields are hashed before sending and which are sent as they are.

In practice: normalise, hash, send

Hashing appears in three common places.

  • Enhanced conversions. The guide to enhanced conversions explains how the email or phone number typed at a conversion is hashed before it leaves the page and matched to signed-in accounts that interacted with an ad.
  • Server-side conversion APIs. The Conversions API guide covers hashing personal fields before sending, and notes that a lead coming from a CRM has no browser identifiers and must rely on hashed contact details.
  • Customer lists. The tutorial on uploading a customer list to Meta offers two routes: hash the file yourself after applying the documented normalisation, or let the upload tool hash it in the browser before it is sent.

The step that decides results is normalisation. Before hashing, values are put into the exact form the platform documents, such as lower-case email addresses with surrounding spaces removed and phone numbers in a consistent international format. The guide to connecting the CRM to ads and analytics shows why this matters when outcomes are uploaded later: the CRM must key each outcome by the same hashed value the conversion tag captured at the form, or the two never meet.

Why hashed data is still personal data

Hashing is sometimes described as anonymisation. It is not. The guide to keeping personal data out of analytics puts it plainly: a hash of an address comes out the same for anyone who applies the same method, so any party holding the address can match it. That is precisely what makes ad matching work, and precisely why the data still points to one person. Hashing protects the identifier in transit and keeps raw values out of a file; it does not settle whether the business may use the data for advertising, which is decided with whoever owns privacy before anything is sent.

Illustrative example — not a real result

A wine club fixes its customer list before the next upload

Corkwhistle Wine Club uploaded 18,400 members to an ad platform to exclude them from its prospecting campaigns, hashing the file itself from a CRM export. Only 41% matched, and members kept seeing introductory offers. A check of the export showed why: about a third of email addresses carried capital letters from the old sign-up form, and several thousand had a trailing space copied in from a spreadsheet. Because a single changed character produces a different hash, those rows could never match. The team added a step that lower-cases and trims every address before hashing, and the next upload of the same members matched 63%, which made the exclusion list large enough to stop most of the wasted offers.

Enhanced Conversions is Google's feature for sending hashed customer data with a conversion, and the Conversions API is Meta's server-side route that relies on hashed fields to match events. Match Rate is the share of uploaded records a platform matched, and normalisation before hashing is one of the main levers on it. Personal Data is the category hashed identifiers stay in, because the person can still be identified by anyone holding the original value.

Common confusions

  • Hashing is encryption. Encryption is designed to be reversed with a key; hashing is designed not to be reversed at all, and matching works by hashing the other side the same way.
  • Hashed data is anonymous. Anyone holding the original email can produce the same hash, so it remains personal data.
  • Any hash will match. Platforms specify the function and the normalisation; a different function or an un-normalised value matches nothing.
  • A low match rate means the platform is failing. Capitals, spaces and inconsistent phone formats are a common cause on the advertiser's side.
  • Hashing makes an upload permissible. Permission depends on how the data was collected and what people were told, not on its format.

More terms to look up

Where this term is used

Sources

  1. About enhanced conversions — Google Ads Help
  2. About the Conversions API — Meta Business Help Centre

Related