--- updatedAt: 2025-12-15T13:08:17.000Z agentTools: projectIndex: https://cloud.docs.tamr.com/llms.txt --- # Steps Completed by B2B Customers When you create a <> using the B2B customers template, <> creates a mastering flow with steps specific to mastering and enriching business customer data. The following table describes each step in the B2B customers flow, and explains which steps usually need to be edited for your data. If you need to make changes to the mastering flow beyond those described in this documentation, contact Support at for assistance. [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 \n\n \n \n \n \n \n \n \n \n \n\n \n \n \n \n

Usually Requires Changes\n	Step\n	Description\n
✅\n	Add Data\n	You verify that source data meets both general requirements \n and template-specific \n requirements. Then, you \n add source data.\n
✅\n	Align to Customer Data Model\n	You map input columns \n to attributes in the supplied schema. If you add attributes to the unified schema, you will need to update the following steps, as described in the rows below, to ensure that these attributes appear in your final mastered entities:\n \n Consolidate Records \n Configure Attributes \n \n
❌\n	Create `tamr_record_id`\n	This transformation step ensures that each source record has a unique primary key across all \nsource datasets by adding a new primary key field: `tamr_record_id`. The `tamr_record_id`\n is a 128-bit hash value of the source dataset name and the source primary \nkey. See the\n Tamr Core \n documentation for a description of the function used to generate the hash value. \n \n Important: If records within the same source dataset have duplicate primary key values, the `tamr_record_id` value for those records will also be duplicates.\n If you mapped an empty placeholder column to the `trusted_id` attribute, add the following transformation: `SELECT *, '' as trusted_id;`.\n
❌\n	Prepare Data for Address Enrichment\n	This step transforms the data in the unified dataset to match the expected inputs for the address enrichment service.\n
❌\n	Standardize URL\n	This step provides a cleaned version of the website domain in `url` attribute values. The cleaned domain is available in the Website Domain field in the mastered entity. \nSee URL \n Standardization and Cleaning.\n
❌\n	Enrich Address\n	\n This step standardizes and validates address information, and enriches addresses with latitude, longitude, and detailed address information.\n See \n\nAddress Standardization, Validation, and Geocoding.\n
❌\n	Prepare Address Fields\n	This step transforms the data in address fields in the unified dataset to prepare for clustering.\n
❌\n	Prepare Data for Phone Enrichment\n	This step transforms the data in the unified dataset to match the expected inputs to the phone number \ndata quality service included in the mastering flow. This step replaces empty country values in source\n records with the country returned by the Enrich Address step.\n\n
❌\n	Enrich Phone\n	This step validates, standardizes, and enriches phone number data. See \nPhone Number Enrichment.\n
❌\n	Prepare Fields for Tamr Enrich ID Step\n	This step prepares fields to be used by the Tamr Enrich ID step.\n\n
❌\n	Enrich Company Name\n	This step cleans and enriches company name data. See Company Name Enrichment.\n
❌\n	Tamr Enrich ID\n	This step matches each company in your source datasets to a Tamr Enrich ID. If a matching \n Tamr Enrich ID is identified, the ID is used by the clustering model to identify duplicate source \n records. The ID is also used by the Tamr Enrich step to add the referential data from your selected \n data provider to your mastered entities, if available. \n \n The step looks for a matching Tamr Enrich ID based on the following attributes, and prioritizes matches available in the public sources:\n First, by company name and full address. \n Next, by company name, city, country, and either region or postal code. \n Next, by company name and country. \n Next, by the cleaned phone number. \n Finally, by the cleaned website. \n \n See Tamr Enrich ID for information about this enricher, including the output fields it adds to your data.\n
❌\n	Prepare for Clustering\n	This step transforms the data in the unified dataset to create the fields used by the \ntrained clustering model to identify similar and matching records. \n \nThe fields created as input to \n the model are prefixed with `ml_`. Many of these `ml_` fields are created as arrays of unified source \nfields and fields added by the enrichment services. The model identifies \nthe most similar values across the arrays and assigns weights based on these similarities.\n
❌\n	Apply Clustering Model\n	This step groups records that refer to the same entity into a cluster, using the trained model.\nSee Features of B2B Customers.\n
✅\n	Consolidate Records\n	This step applies rules to produce a single record, called the mastered entity record, that best represents a cluster. For most fields, these rules select the most common value from the clustered records.\n \n Additionally, this step adds a Tamr ID (`tamr_id`) to each mastered entity record. The Tamr ID \nis a unique, persistent id.\n \nIf you added new attributes in the Schema Mapping step, add lines in the transformations to \ntell Tamr Cloud what value to set for each attribute when creating the mastered entity. See \nModifying Record Consolidation Transformations.\n
✅\n	Tamr Enrich\n	This step enriches each mastered company entity that has a Tamr Enrich ID with referential \ndata data from a public source, if available. By default, Tamr enriches each company with the best match from the \nthese public sources. \n For example, if Tamr identifies a match in both the public sources and in \n BoldData, this step enriches your data with the match from the public sources, even if the BoldData match is a higher confidence match.\n \n\n\n See Public Source Enrichment for the attributes added by the public sources.\n Note: If you would like to use a data provider other than the Public Sources \nservice, contact Tamr at help@tamr.com\n to discuss data provider entitlement.\n
❌\n	Calculate Similarity Scores\n	This step calculates the similarity between attribute values in the mastered entity and the attribute values\nreturned by your selected data provider. This step provides both an average similarity between the mastered entity and the \nvalues returned by the data provider, and attribute-level similiarity for key attributes. \n \n Scores range from 0-1, with 0 being low similarity and 1 being high similarity. To calculate these scores, the step first splits the text into tokens on \nspaces and special characters (with the exception of underscore (_) characters), removes special characters, and converts all letters to lowercase. \nThen, the step uses a Jaccard similarity function to evaluate the similarity between tokens, returning\n a score between 0-1.\n\n Unlike other scores, phone number and website similarity are either 0 or 1. A similarity of 1 is returned\nif the characters in the cleaned source phone number or website and phone number or website returned by the data provider are an exact match, or \nif one value is contained in the other. Otherwise, the similarity is 0.\n\n You can review these scores on the Entity Details page after the flow runs, and investigate entities with low \n similiarity scores.\n \n \n This step calculates the following similarity scores:\n \n Tamr Enrich Average Similarity \n Tamr Enrich Name Similarity \n Tamr Enrich Alternate Name Similarity \n Tamr Enrich Address Line 1 Similarity \n Tamr Enrich City Similarity \n Tamr Enrich Region Similarity \n Tamr EnrichPostal Code Similarity \n Tamr Enrich Phone Number Similarity\n \n Tamr Enrich Website Similarity \n \n
✅\n	Configure Attributes\n	You configure how mastered entity attributes appear in Tamr Cloud and published datasets. If you added new attributes in the Schema Mapping step, add and map those attributes in this step to include them in your final mastered entity output. See \nConfiguring Data Display.\n

\n" } [/block]