Use the Lookup endpoint to match hashed PII data to a RampID.
You should use the Lookup endpoint when:
- You don't want to send raw PII in your API call.
- You want an exact match to a single hashed PII touchpoint.
If there is a maintained record associated with the input string or ID, the maintained RampID is returned. If not, a derived RampID is returned.
Supported Inputs for Hashed PII Strings
The API accepts MD5-hashed email addresses, SHA256-hashed email addresses, SHA1-hashed email addresses, or SHA1-hashed PII strings as input.
For hashed PII strings, LiveRamp will only return a maintained identifier if the hashed string has an exact match against a maintained record in the Identity Graph. The Lookup endpoint does not perform any approximate or fuzzy string matching. While all fields in a hashed PII string are optional, the presence or absence of fields may affect the results returned.
See the table below for all supported variations of hash type and input type. The elements in brackets [] are optional.
| Hash Type | Input Type | Formula |
|---|---|---|
| MD-5 | ||
| SHA-256 | ||
| SHA-1 | ||
| SHA-1 | Phone | Phone |
| SHA-1 | Postal | Primary Number + PreDirectional + Street Name + Street Suffix + PostDirectional + Unit Designator + Secondary Number + City + State + Zip |
| SHA-1 | Name + Email | First + [Middle OR Middle Initial] + Last + [Generational Suffix] + Email |
| SHA-1 | Name + Phone | First + [Middle OR Middle Initial] + Last + [Generational Suffix] + Phone |
| SHA-1 | Name + Postal | First + [Middle OR Middle Initial] + Last + [Generational Suffix] + [Primary Number] + [PreDirectional] + [Street Name] + [Street Suffix] + [PostDirectional] + [Unit Designator] + [Secondary Number] + [City] + [State] + Zip |
General Construction Rules
The rules listed below apply to all PII string types.
- Strings must be UTF-8 encoded.
- If a field is empty, it should be excluded from the string.
- Separate fields with single spaces. Don't add additional spaces if you leave out a particular field.
- Convert all fields to lowercase before hashing.
- Phone numbers should only include digits with no special characters.
- Hyphens are allowed except in phone numbers.
- Remove all periods (.) from the name and phone fields. Do not remove periods from email addresses.
Constructing Names
See the table below for information on the elements that can be included when constructing names.
| Name Element | Description | Example | Required? |
|---|---|---|---|
| First Name | The person's first name | Eduardo Felicia | Yes |
| Middle Name | The person's middle name or middle initial | Kyu k john j | No |
| Last Name | The person's last name | Lopez Nguyen | Yes |
| Generational Suffix | The person's generational name suffix | Jr Sr II | No |
Constructing Postal Addresses
Postal addresses may be constructed in the following ways
- Primary Number + Pre Directional + StreetName + StreetSuffix + PostDirectional + Unit Designator + SecondaryNumber + City + State + ZIP
- ZIP