The B2C customers template includes a predefined, standardized schema for customer data. The mastering flow for data products produced by this template includes a schema mapping step in which you identify how columns in your source datasets correspond to the attributes in the supplied schema.
To prepare, review the general Requirements for Source Datasets. Then, identify the column or columns in each of your source datasets that you will map to the attributes in the people schema. After you map your source data columns, Tamr Cloud can enrich your data and consolidate similar records into entities.
The table below describes these attributes and explains which are:
Required: The Schema Mapping step will be marked as incomplete and you cannot run the flow until you map source columns to these attributes.
Recommended: For optimal data quality, 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.
|primaryKey||The primary key used in the source dataset to uniquely identify each record. See About Primary Keys for more information.||Required|
|trusted_id||A non-unique key, such as a customer or contact identification number used by your internal systems.
The clustering model always clusters together records that have the same
|Address_Line_1||Line 1 of the customer’s address.||Recommended|
|Address_Line_2||Line 2 of the customer’s address.||Optional|
|City||City of the customer’s address.||Recommended|
|Country||Country of the customer’s address.||Recommended|
|Date_of_Birth||The customer’s date of birth.||Recommended|
|The customer’s email address.||Recommended|
|First_Name||The customer’s first name.||Required|
|Gender||The customer’s gender.||Recommended|
|Last_Name||The customer’s last name.||Required|
|Middle_Name||The customer’s middle name.||Optional|
|Name_Suffix||The customer’s suffix, such as Jr. or Senior.||Optional|
|National_ID||The customer’s national ID, such as Social Security Number.||Recommended|
|Phone||The customer’s phone number.||Optional|
|Postal_Code||Postal (zip) code of the customer’s address||Recommended|
|Region||The region of the customer’s address, such as the state or territory.||Recommended|
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. The template does not use these additional attributes as part of the mastering process.
Updated about 1 month ago