B2B Customers Data Product

Use the B2B customers data product to master site-level company data and enrich company entities with referential data from selected data providers.

This data product provides a consolidated view of businesses at the granularity of individual sites (headquarters versus satellite offices, for example) that is enriched with corporate hierarchy and other referential data from selected data providers. See Tamr Firmographic Enrichment and Dun & Bradstreet Enrichment for more information about supported data providers.

This data product provides:

  • An industry-standard schema for company data.
  • A machine learning model that deduplicates entities within, and across, your data sources.
  • Data quality services for company name, phone number, url, and address data.
  • Firmographic enrichment services that supplement your data with company hierarchy and other referential data. You can choose to use data from public firmographic enrichment providers, or from a supported premium provider for which you have license.

These data products provide a view of companies that identifies, and differentiates, various business locations. In your data, companies might mean customers, suppliers, prospects, health care organizations, portfolio companies, or another type of organization.

B2B Customers Data Processing

The following diagram explains how your source records are prepared for clustering, and how Tamr creates and enriches the golden record for each B2B customer.

Source record preparation includes:

  • Aligning source columns to data product attributes.
  • Cleaning, validating, and enriching source record values. This includes cleaning for any specified bad values. These enhanced values provided by the data quality services are used as input when creating your golden records.
  • Assigning each record a unique primary key, the tamr_record_id. This ID is a 128-bit hash value of the source dataset name and the source primary key.
  • Matching each source record to a Tamr Enrich ID (tamr_enrich_id). This ID is a unique, proprietary organizational identifier owned and managed by Tamr, which is used to match your source company data to referential data provided by the Tamr Enrich service and other data providers (Enigma, Pitchbook, and so on).

Source record clustering includes:

  • Applying the clustering model and any clustering rules to group source records that refer to the same company. (This model is described in the section below.) Each record in a given cluster is assigned the same Tamr ID. This is ID is a unique, persistent identifier that links records in a cluster with each other and with the generated golden record for that cluster.
  • Applying any previous cluster overrides and verifications.

Golden record creation includes:

  • Applying logic to select the best value for each golden record attribute, and associating a Tamr ID with the golden record.
  • Enriching golden records with firmographic data from selected data providers.

B2B Customers Clustering Model

By default, the B2B customers model groups records as follows. Additionally, Tamr applies any custom clustering rules you have added to for the data product when clustering source records.

First, records are clustered by either:

  • tamr_enrich_id for data products not using D&B enrichment, when matched based on company name and full address
  • High confidence DUNS number for data products using D&B enrichment.

Then, remaining records are clustered by similarity.

Clustering by tamr_enrich_id

Depending on the available source data, Tamr matches companies in your source datasets to Tamr Enrich IDs based on one of the following:

  • Company name and full address. For this match level, address information must be available and mapped to input fields used by the enricher.
  • Company name and city. Tamr identied a match based on the company name, city, country, and either region or postal code.
  • Company name, domestic ultimate parent company, and country code. Tamr identified a match based on the company name, domestic parent company, and country code.
  • Registration number. Tamr identified a match based on the company's registration number.
  • Company name and country code. Tamr identified a match based on the company name and country code. For companies with US addresses, state is used in case of a tie. Postal code and city are further used to break ties, for all countries.
  • Phone number. Tamr identified a match based on the cleaned phone number.
  • Website. Tamr identified a match based on the cleaned website.

If a tamr_enrich_id is assigned to a source record based on the company name and full address (tamr_firmographic_match_status is MATCH_NAME_ADDRESS), then records with matching tamr_enrich_id values are clustered together and records with different tamr_enrich_id values are not clustered together.

Clustering by DUNS Number

If D&B enrichment is enabled for this data product, the clustering model identifies records that represent the same entity by first considering the DUNS number instead of thetamr_enrich_id. If two records have been enriched with the same DUNS number, they are clustered together, provided that the DUNS match is above the configured Confidence Code threshold or matches any specified Match Grade Patterns. See Configuring the B2B Customers Data Product for more information on configuring these settings.

Clustering by Similiarity

Records that are not clustered based on their tamr_enrich_id or DUNS number are clustered based on similarities between these attribute fields:

  • Company name
  • Alternate company names
  • Full address and address components
  • Phone number
  • Website

The model considers similarities in these values, not exact matches. For example, two addresses on the same street may correspond to the same company site.

Data Quality Services

This data product includes data quality services for the following values:

These services supplement your source data with standardized, validated values for these essential attributes. They examine values for these attributes, and add any resulting validated, standardized values to each record in new enrichment-specific attributes. The original values mapped from your source datasets remain present and unchanged. They also help identify additional communication channels, including which phone numbers can receive text messages. With reliable, up-to-date information, your organization’s representatives can more efficiently and effectively work on their accounts.

See the topics linked above for processing details and added attributes.

Firmographic and Healthcare Organization Enrichment

The B2B customers data product includes Tamr firmographic enrichment services that enrich your data with referential data from one or more selected public and premium data providers.

Firmographic enrichment can help solve problems such as:

  • Missing corporate hierarchy information.
  • Out-of-date information, such as company names that have changed due to acquisition.
  • Missing details about an organization, such as number of employees, revenue, SIC codes, national identifier, and so on.
  • Misidentifying different companies that reside in the same building as the same company.

Public providers include:

Premium data providers, for which separate licensing is required, include:

DUNS Match and D&B Data Block Enrichment

In addition to other data enrichment providers, can choose to enrich your data with referential data from Dun & Bradstreet Enrichment. Dun & Bradstreet (D&B) enrichment enriches your company data with a DUNS number and data from the D&B Data Blocks to which you are entitled. D&B Data Blocks include:

  • Company Information L2
  • Hierarchies and Connections L1
  • Diversity Insights L1
  • Third Party Risk Insights L1

Requirements

If you are using DUNS Match and D&B Data Block Enrichment, you must:

  • Have an API key that provides access to one or more of the supported data blocks above.
  • Add your D&B API secret and key on the Admin > API Keys page. See Managing API Keys.

Using this Data Product

To learn more about this data product's requirements, configuration, and resulting mastered entities, see: