Source Dataset Requirements for the B2C Customers Data Product

The B2C Customers data product includes a predefined, standardized schema for customer contact data. When you add data to your data product, you identify how columns in your source datasets correspond to the attributes in the unified schema.

To prepare, review the general Requirements for Source Datasets.

The tables below describes these attributes and explains which are:

  • Required: You cannot refresh your data until you map source columns to these attributes. Mapping ONLY required attributes does not provide sufficient information for clustering or enrichment.
  • Suggested: For optimal enrichment and clustering results, map source columns to as many of these attributes as possible.
  • Optional: These attributes have minimal impact on your clustering and enrichment results. If your source data includes columns that match these attributes, map them to include that source data in your completed data product.

Attributes Other than Addresses, Phone Numbers, and Emails

Note that the matching model can use either the combination of first and family name values or full name values, whichever is mapped from the source data.

Unified AttributeDescriptionType
Primary KeyThe primary key used in the source dataset to uniquely identify each record.
See
About Primary Keys
for more information.
Required
Name PrefixThe customer's prefix, such as Ms. or Mr.Optional
First NameThe customer's first name.You are required to map either the first and family name or the full name attributes.
Middle NameThe customer's middle name.Optional
Family NameThe customer's last name.You are required to map either the first and family name or the full name attributes.
Full NameThe contact's full name.You are required to map either the first and family name or the full name attributes.
Name SuffixThe contacts's suffix, such as Jr. or Senior.Optional
Date of BirthThe customer's date of birth.Suggested
GenderThe customer's gender.Optional
National IDThe customer's national identifier. For example, Social Security Number.Optional

Address Attributes

You can configure multiple address types. Address attributes are organized into different groups, representing different types of addresses associated with the customers.

The data product schema includes Primary address attributes by default. You can choose to include attributes for additional address types, including:

  • Office
  • Corporate
  • Previous
  • Mailing
  • Shipping
  • Registered
  • Billing
  • Other

Within an attribute group, the attribute name is prefixed with the address type. For example: Primary: Address, Billing: City, and Mailing: Country.

Mail consent statuses are standardized to 'OPT-IN' with any casing of "TRUE", "T", "YES", "Y", "OPT IN", "OPT-IN", and "OPTIN". Any other value in the mail consent field will be standardized to 'OPT-OUT'. Consent dates are converted to an iso format using the list of accepted date formats ["yyyy-MM-dd", "dd.MM.yyyy", "d.MM.yyyy", "dd/MM/yyyy", "d/MM/yyyy"] and time formats ["HH:mm", "HH:mm:ss", "HH:mm:ss.SSS"].

Each attribute group includes the following address attributes:

Unified Address AttributeDescriptionType
AddressEither line 1 of the address, or the complete address.Suggested for primary address. Optional for other address types.
Address Line 2Line 2 of the address.Optional
Address Line 3Line 3 of the address.Optional
Address Line 4Line 4 of the address.Optional
CityCity of the address.Optional
StateThe state or region of the address.Optional
Postal CodePostal (zip) code of the address.Optional
CountryCountry of the address.Suggested for primary address. Optional for other address types.
LatitudeThe latitude of the address.Optional
LongitudeThe longitude of the address.Optional
Consent StatusWhether the person has opted-in to communications at this address.Optional
Consent DateThe date at which the person opted-in or opted-out of communications at this address.Optional

Phone Attributes

You can configure multiple phone number types. Phone number attributes are organized into different groups, representing different types of phone numbers associated with a person.

The data product schema includes Mobile phone number attributes by default. You can choose to include attributes for additional phone number types, including:

  • Home
  • Work
  • Office
  • Other

Phone consent statuses are standardized to 'OPT-IN' with any casing of "TRUE", "T", "YES", "Y", "OPT IN", "OPT-IN", and "OPTIN". Any other value in the phone consent field will be standardized to 'OPT-OUT'. Consent dates are converted to an iso format using the list of accepted date formats ["yyyy-MM-dd", "dd.MM.yyyy", "d.MM.yyyy", "dd/MM/yyyy", "d/MM/yyyy"] and time formats ["HH:mm", "HH:mm:ss", "HH:mm:ss.SSS"].

Within an attribute group, the attribute name is prefixed with the phone number type (for example: Mobile: Phone).

Each phone number group includes the following attributes:

Unified Phone AttributeDescriptionType
PhonePhone numberSuggested for mobile number. Optional for other phone numbers.
SMS Consent StatusWhether the person has opted-in to SMS communications.Optional
SMS Consent DateThe date at which the person opted-in or opted-out of SMS communications.Optional
Voice Consent StatusWhether the person has opted-in to voice communications.Optional
Voice Consent DateThe date at which the person opted-in or opted-out of voice communications.Optional

Email Attributes


You can configure multiple email address types. Email address attributes are organized into different groups, representing different types of email addresses associated with a person.

The data product schema includes Personal email address attributes by default. You can choose to include attributes for additional email address types, including:

  • Work
  • Office
  • Other

Email consent statuses are standardized to 'OPT-IN' with any casing of "TRUE", "T", "YES", "Y", "OPT IN", "OPT-IN", and "OPTIN". Any other value in the email consent field will be standardized to 'OPT-OUT'. Consent dates are converted to an iso format using the list of accepted date formats ["yyyy-MM-dd", "dd.MM.yyyy", "d.MM.yyyy", "dd/MM/yyyy", "d/MM/yyyy"] and time formats ["HH:mm", "HH:mm:ss", "HH:mm:ss.SSS"].

Within an attribute group, the attribute name is prefixed with the email address type (for example: Personal: Email).

Each email address group includes the following attributes:

Unified Email AttributeDescriptionType
EmailEmail address.Suggested for personal email. Optional for other email addresses.
Consent StatusWhether the person has opted-in to email communications.Optional
Consent DateThe date at which the person opted-in or opted-out of email communications.Optional
Delivery StatusEmail delivery status.Optional


Did this page help you?

© 2025, Tamr, Inc. All rights reserved.

License Agreement | Privacy Policy | Data Security Policy| AI Chatbot Disclaimer