Skip to main content
Note:The following hashing guidelines apply to Zeotap CDP (1P data) only. To know about the hashing guidelines for Data Partners, refer to Data Onboarding Guide for Partners.

​
Email Addresses

This section provides information about the supported customer identities (both raw and hashed) and the hashing guidelines for ingesting email addresses. Below are the ways through which you can ingest the email addresses into the Zeotap system.
  • Send Raw Email Addresses to Zeotap CDP – You can send raw email addresses to Zeotap CDP and we can hash them to SHA256 and MD5.
  • Hash Email Addresses Before Sending to Zeotap CDP – You can send hashed user identities in the formats of SHA256 and MD5. For more information about the hashing guidelines for email addresses, refer here.

​
Send Raw Email Addresses to Zeotap CDP

For Zeotap CDP to identify a value as raw email, map the field to the Zeotap catalogue Email Raw catalogue field. This ensures that Zeotap CDP encrypts the raw value and creates the four hashes as mentioned in the table below. Note that along with the hashed values, the encrypted value is available for activation for Destinations which can only activate raw values.
CATALOGUE FIELD NAMEDESCRIPTION
Email SHA256 LowercaseThis is the customer’s email address hashed to sha256 after converting it to lowercase.
Email SHA256 UppercaseThis is the customer’s email address hashed to sha256 after converting it to uppercase.
Email MD5 LowercaseThis is the customer’s email address hashed to md5 after converting it to lowercase.
Email MD5 UppercaseThis is the customer’s email address hashed to md5 after converting to uppercase.
Note:Email Addresses cannot have null values or hashes of null values.

​
Hash Email Addresses Before Sending to Zeotap CDP

If you wish to hash the email addresses yourself, you can do so by following the guidelines mentioned below:
  1. Remove all the leading and trailing spaces before hashing.
  2. Convert the email address to lower or upper case. For example, name@ and NAME@.
  3. Apply sha256 and md5 hash functions on the case-converted email address.
  4. After applying sha256 and md5, you get a set of two email-based fields for each hash function as follows:
    • sha256 (lowercase),
    • sha256 (uppercase)
    • md5 (lowercase)
    • md5 (uppercase) 
When using the BigQuery function for hashing email addresses, ensure that the correct function is used as explained below:In BigQuery, there is a function for hashing input to SHA256 as shown below: SELECT SHA256("ds.bharath@zeotap.com") as sha256However, this function only returns 44 characters, which is not accepted by the system. To produce a 64 character SHA256 hash, you must use the following function: SELECT To_HEX(SHA256("ds.bharath@zeotap.com")) as sha256.
Note:sha-256 hashing must be HEX code with 64 characters. For example, f660ab912ec121d1b1e928a0bb4bc61b15f5ad44d5efdc4e1c92a25e99b8e44a.

​
Cell Phone Numbers

This section provides information on the supported user identities (raw and hashed) and the hashing guidelines for Cell Phone Numbers. Below are the ways through which you can ingest the cell phone identities into Zeotap.
  • Send Raw Cell Phone Numbers to Zeotap CDP – You can send raw cell phone numbers and Zeotap can hash them in the formats of SHA256 and MD5. Ensure that you share the raw values in the format <Country Code> <Cell Phone Number>.
  • Hash Cell Phone Numbers Before Sending to Zeotap CDP– You can send hashed user identities in the formats of SHA256 and MD5. For more information about the hashing guidelines for cellphone numbers, refer here.
Note:Cell phone numbers cannot have null values or hashes of null values.

​
Send Raw Cellphone numbers to Zeotap CDP

When hashing cellphone numbers from their raw format, you must adhere to specific guidelines, depending on the method of data sharing. The following are the two scenarios of sharing raw cell phone numbers: Scenario 1: Raw Cellphone Sharing through JS Tag If you want to share raw cellphone numbers through our JS tag, then you have to adhere to the guidelines outlined in the JS or SDK implementation guides. These guidelines are crucial for Zeotap to create the 6 hashes efficiently. Scenario 2: Raw Cellphone Sharing through Direct File Upload If you are sharing raw cellphone numbers through direct file upload, then Zeotap creates 6 hashes as mentioned in the table below:
CATALOGUE FIELD NAMEDESCRIPTION
Cell Phone SHA256 With CodeThis is the customer’s cell phone number withthe country code and hashed to sha256
Cell Phone SHA256 Without CodeThis is the customer’s cell phone number withoutthe country code and hashed to sha256
Cell Phone MD5 With CodeThis is the customer’s cell phone number with thecountry code and hashed to md5
Cell Phone MD5 Without CodeThis is the customer’s cell phone number withoutthe country code and hashed to md5
Cell Phone e164 SHA256This is the customer’s cellphone number in e.164 format hashed to sha256
Cell Phone e164 MD5This is the customer’s cellphone number in e.164 format hashed to md5
Ensure that you follow the format <Country_code> <Space> <Cellphone number> for sharing raw cellphone numbers. For example, a subscriber from the Spain with the phone number 679594499 (country code: 34) must be shared as 34 679594499. If it is not possible to include the space between the country code and cellphone number in the same column, share it as <Country_code> <Cellphone number>. Subsequently, we will convert it to e164 format and generate hashes, specifically Cell Phone e164 SHA256 and Cell Phone e164 MD5. However, if you share a cellphone number without the country code, then Zeotap CDP assumes it includes the country code while converting it to e164 format and creates the hashes, Cell Phone e164 SHA256 and Cell Phone e164 MD5. Therefore, be cautious while sharing the raw cellphone numbers. Once you share the raw cellphone number in the correct format, Zeotap CDP creates 6 hashes, including the e164 hashes as mentioned in the table above.
Note:e164 is an international standard that assigns globally unique numbers to devices in the worldwide Public Switched Telephone Network (PSTN). A cellphone number in e164 format is represented as [+] [country code] [Cellphone number including area code]. For example, a subscriber from the United States with the phone number 6171339687 (country code: 1) is represented in e164 format as +16171339687.

​
Hash Cellphone Numbers Before Sending to Zeotap CDP

If you wish to hash the cellphone numbers yourself, you can do so by following the guidelines mentioned below:
  1. Remove all special characters, including (), +, and - from the cellphone number.
  2. Separate the cellphone number into two formats, one with the country code and one without. For example, for Spain:
    • With country code: 34679594499
    • Without country code: 679594499
  3. Apply Sha256 and Md5 to both phone number formats (with and without the country code).
  4. You obtain a set of two hashed fields for each hash function as follows:
    • Sha256 (with country code)
    • Sha256 (without country code)
    • Md5 (with country code)
    • Md5 (without country code)
Note:Sha256 hashing results in a 64-character HEX code, such as f660ab912ec121d1b1e928a0bb4bc61b15f5ad44d5efdc4e1c92a25e99b8e44a.
  1. To hash cellphone numbers in e164 format to Sha256 and Md5, perform the following steps:
    1. Convert the cellphone number to e164 format, which includes the country code and subscriber number with the area code in the format [+] [country code] [subscriber number including area code]. For example, a subscriber from the United States with the phone number 6171339687 (country code: 1) is represented in e164 format as +16171339687.
    2. Apply Sha256 and Md5 hashing algorithms to the e164-formatted number to obtain three hashed values:
      • Cellphone Number E164 Sha256
      • Cellphone Number E164 Md5
The 6 hashes that you need to send to Zeotap are mentioned in the table below.
CATALOGUE FIELD NAMEDESCRIPTION
Cell Phone SHA256 With CodeThis is the customer’s cell phone number with the country code and hashed to sha256.
Cell Phone SHA256 Without CodeThis is the customer’s cell phone number without the country code and hashed to sha256.
Cell Phone MD5 With CodeThis is the customer’s cell phone number with the country code and hashed to md5.
Cell Phone MD5 Without CodeThis is the customer’s cell phone number without the country code and hashed to md5.
Cell Phone e164 SHA256This is the customer’s cell phone number in e164 format hashed to sha256.
Cell Phone e164 MD5This is the customer’s cell phone number in e164 format hashed to md5.
Last modified on February 26, 2026