Prepare user data

Upload collected customer data to create Customer Match audiences. This is sensitive data. You must properly prepare it before uploading.

Format data

Format your raw data by doing the following:

  • Take out any whitespace from first name, last name, and email address values.
  • Make all string values lowercase.
  • Format phone number value using the E.164 format. Include the country code.

Hash data

Hash raw data values of the following types using the SHA256 algorithm:

  • First name
  • Last name
  • Email address
  • Phone number

Assign data

The data that you are using determines audience type. It also determines the API object used to pass the data.

Contact information

If you are using contact information to match users:

  • Use the audience type CUSTOMER_MATCH_CONTACT_INFO.
  • Pass the data in a ContactInfo object.

The selection of data provided for a customer determines the method used to match them:

Matching method
Email address matching At least one value assigned to the hashedEmails field.
Phone matching At least one value assigned to the hashedPhoneNumbers field.
Mailing address matching Values assigned to hashedFirstName, hashedLastName, zipCodes and countryCode fields.
Combined email address, mailing address, and phone matching Values assigned to hashedEmails, hashedPhoneNumbers, hashedFirstName, hashedLastName, zipCodes and countryCode fields.

Include all ContactInfo objects for a single upload in a ContactInfoList object.

Mobile device IDs

If you are using mobile device IDs to match users:

  • Use the audience type CUSTOMER_MATCH_DEVICE_ID.
  • Pass the data using a mobile device ID string.

Include all mobile device IDs for a single upload in a MobileDeviceIdList object.

Set the consent field in the relevant data object to pass signals of consent granted by the included users.

Setting either field in the Consent object to CONSENT_STATUS_DENIED will return an error.

Consent signals apply to all users in a request. Use separate requests to upload users with different consent signals.