The B2B customers data product includes a predefined, standardized schema for company 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](doc:requirements-for-input-datasets). The table 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. **Tip**: You can also add attributes to the unified schema and map columns that you want to include in the mastered data product to them. # Attributes Other than Addresses, Phone Numbers, and Emails [block:html] { "html": "\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n

\nUnified Attribute\n	\nDescription\n	\nType\n
\n Primary Key	\nThe primary key used in the source dataset to uniquely identify each record. \nSee \n About Primary Keys for more information.\n	Required
Company Name	Company's name.	Required
Alternative Names	Alternate names for the company.	Optional
Previous Names	Previous legal names for the company.	Optional
Revenue	Revenue for the company.	Optional
Company Type	Legal status of the company (for example, LLC, LTD, and so on).	Optional
Industry Type	Industry type of the company.	Optional
Founding Year	Year of company formation.	Optional
Registration Number	Legal entity ID with local government. For Healthcare Organizations, the NPI number.	Optional
Registration Number Type	Company registration number type, such as EIN or NPI.	Optional
Tax IDs	Identification numbers, such as EINs.	Optional
Ticker Symbol	Company’s ticker symbol on the stock exchange.	Optional
Stock Exchange	Stock exchange where the company is listed (if public).	Optional
Email Domain	The email domain for the company.	Optional
Website	Primary website domain for the company.	Suggested
Associated Persons	Officers, Directors, and other people associated with the company.	Optional

" } [/block] # Address Attributes You can configure multiple address types. Address attributes are organized into different groups, representing different types of addresses associated with a person. 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`. Each attribute group includes the following address attributes: [block:html] { "html": "\n \n \n \n \n \n\n\n\n\n \n \n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n\n \n \n \n \n\n \n \n \n \n\n \n \n \n \n\n \n \n \n \n \n\n \n \n \n \n\n \n \n \n \n

\nUnified Address Attribute\n	\nDescription\n	\nType\n
\n Address	Either line 1 of the address, or the complete address.	\n Suggested for primary address. Optional for other address types.
\n Address Line 2	\n Line 2 of the address.	\n Optional
\n Address Line 3	\n Line 3 of the address.	\n Optional
\n Address Line 4	\n Line 4 of the address.	\n Optional
\n City	\n City of the address.\t	\n Optional
\n State	\n The state or region of the address.	\n Optional
\n Postal Code	\n Postal (zip) code of the address.	\n Optional
\n Country	\n Country of the address.	\n Suggested for primary address. Optional for other address types.
\n Latitude	\n The latitude of the address.	\n Optional
\n Longitude	\n The longitude of the address.	\n Optional

" } [/block] # 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 company. The data product schema includes **Primary** phone number attributes by default. You can choose to include attributes for additional phone number types, including: - Secondary - Office - Corporate - Previous - Other Within an attribute group, the attribute name is prefixed with the phone number type (for example: `Primary: Phone`). Each phone number group includes the following attribute: [block:html] { "html": "\n \n \n \n \n \n\n\n\n\n \n \n\n

\nUnified Phone Attribute\n	\nDescription\n	\nType\n
\n Phone	Phone number	\n Suggested for prmary number. Optional for other phone numbers.

" } [/block] # 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 company. The data product schema includes **Primary** email address attributes by default. You can choose to include attributes for additional email address types, including: - Secondary - Office - Corporate - Previous - Other Within an attribute group, the attribute name is prefixed with the email address type (for example: `Primary: Email`). Each email address group includes the following attribute: [block:html] { "html": "\n \n \n \n \n \n\n\n\n\n \n \n\n

\nUnified Email Attribute\n	\nDescription\n	\nType\n
\n Email	Email address.	\n Suggested for primary email. Optional for other email addresses.

" } [/block]