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.
Suggested: For optimal enrichment and clustering results, map source columns to these attributes.
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 Attribute	Description	Type
Primary Key	The primary key used in the source dataset to uniquely identify each record. See About Primary Keys for more information.	Required
Name Prefix	The customer's prefix, such as Ms. or Mr.	Optional
First Name	The customer's first name.	You are required to map either the first and family name or the full name attributes.
Middle Name	The customer's middle name.	Optional
Family Name	The customer's last name.	You are required to map either the first and family name or the full name attributes.
Full Name	The contact's full name.	You are required to map either the first and family name or the full name attributes.
Name Suffix	The contacts's suffix, such as Jr. or Senior.	Optional
Date of Birth	The customer's date of birth.	Suggested
Gender	The customer's gender.	Optional
National ID	The customer's national identifier. For example, Social Security Number.	Optional

Address Attributes

You can configure multiple address types in the B2C customers data product. 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, and other addresses.

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

Each attribute group includes the following address attributes:

Unified Address Attribute	Description	Type
Address	Either line 1 of the address, or the complete address.	Suggested for primary address. Optional for other address types.
Address Line 2	Line 2 of the address.	Optional
City	City of the address.	Optional
State	The state or region of the address.	Optional
Postal Code	Postal (zip) code of the address.	Optional
Country	Country of the address.	Suggested for primary address. Optional for other address types.
Latitude	The latitude of the address.	Optional
Longitude	The longitude of the address.	Optional

Phone Attributes

You can configure multiple phone number types in the B2C customers data product. Phone number attributes are organized into different groups, representing different types of phone numbers associated with the customers.

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, and 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 Attribute	Description	Type
Phone	Phone number	Suggested for mobile number. Optional for other phone numbers.
SMS Consent Staus	Whether customer has opted-in to SMS communications.	Optional
SMS Consent Date	The date at which the customer opted-in or opted-out of SMS communications.	Optional
Voice Consent Status	Whether customer has opted-in to voice communications.	Optional
Voice Consent Date	The date at which the customer opted-in or opted-out of voice communications.	Optional

Email Attributes

You can configure multiple email address types in the B2C customers data product. Email address attributes are organized into different groups, representing different types of email addresses associated with the customers.

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, and 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 Attribute	Description	Type
Email	Email address.	Suggested for personal email. Optional for other email addresses.
Consent Staus	Whether customer has opted-in to email communications.	Optional
Consent Date	The date at which the customer opted-in or opted-out of email communications.	Optional
Delivery Status	Email delivery status.	Optional