What's New: Expanded Schema for All Data Products

We are pleased to announce that new attributes are now available for B2B Customers, B2C Customers, Contacts, and Healthcare Providers.

❗️

Important Note for Webhook Notifications

If you have a configured a webhook for record event notifications, the addition of these attributes will trigger a one-time update notification per record in your System of Record (SOR) the next time you refresh the data product and apply the changes to the SOR.

Multiple Phone and Email Types for B2B Customers, Contacts, and Healthcare Providers

You can now configure multiple phone and email types for B2C Customers, Contacts, and Healthcare Providers.

In the Configure Data Product page, phone and email attributes are organized into different groups, representing different types of phone numbers and email addresses.

Phone Number Attribute Groups

For Contacts and Healthcare Providers, you can configure the following types of phone numbers:

  • Mobile
  • Home
  • Work
  • Office
  • Other

For B2B Customers, you can configure the following types of phone numbers:

  • Primary
  • Secondary
  • Office
  • Corporate
  • Previous
  • Other

Each phone number group include the following attribute:

Unified Phone Attribute Description Type
Phone Phone number. Suggested for mobile/primary number. Optional for other phone numbers.

Email Attribute Groups

For Contacts and Healthcare Providers, you can configure the following types of email addresses:

  • Personal
  • Work
  • Office
  • Other

For B2B Customers, you can configure the following types of email addresses:

  • Primary
  • Secondary
  • Office
  • Corporate
  • Previous
  • Other

Each email address group will include the following attribute:

Unified Email Attribute Description Type
Email Email address. Suggested for personal/primary email. Optional for other email addresses.

Multiple Licenses for Healthcare Providers

You can now configure up to 20 licenses in the Healthcare Providers data product. These licenses are used as input for NPPES enrichment.

In the Configure Data Product page, license attributes are organized into groups numbered 1 through 20, representing different licenses.

For each license, you can provide the following attributes:

Unified License Attribute Description Type
License: Number The provider's license number. Suggested
License: State The state where the provider was licensed. Suggested
License: Country The country where the provider was licensed. Suggested
License: Status The provider's license status. Optional

Address Communication Consent Attributes for B2C Customers

You can now track communication consent status for each address type in the B2C Customers data product. Each address attribute group includes the following:

Unified Attribute Description Type
Consent Staus Whether the person has opted-in to communications at this address. Optional
Consent Date The date at which the person opted-in or opted-out of communications at this address. Optional

Migrating to the New Attributes

The new attributes are available automatically in existing data products, but your configuration has not changed.

You can run your data product and publish results without making any changes to the current data product configuration.

Using the new attributes in the data product involves:

  1. Updating the data product configuration and refreshing the data product.
  2. Updating display settings.
  3. Updating publish configurations.

Updating the Data Product Configuration

When you first open the Configure Data Product page, you see yellow warning messages for the existing deprecated attributes, prompting you to remove these mappings and re-map the attributes to the new attributes.



The Refresh Data Product button is enabled, allowing you to run the data product without remapping the attributes.

Step 1: Remap Attributes
To remap fields to the new attribute groups:

  1. Map the new attributes for each source dataset.
  2. Remove the mappings for the deprecated attributes. After you remove the mappings, the deprecated attributes are removed from the schema.

Important: Once you begin mapping to the attributes, you cannot refresh the data product until you remap all of the source datasets to the new attributes and remove the deprecated mappings.



Step 2: Set Record Consolidation Rules
Configure the record consolidation rules for the new attributes. You configure these rules at the group level. Select the name of the group to open the configuration rules.

Note: For the License attributes in the Healthcare Providers data product, only the Tamr recommended value option is available.




Step 3: Select Attributes to Include in Uniformity Scores
For each attribute, you can choose whether to calculate the uniformity score. The uniformity score provides insight into how similar the values for this attribute are within the source record cluster.

Note: You cannot configure License attributes in the Healthcare Providers data product.



Step 4: Update Clustering Rules
If you have existing clustering rules that refer to the deprecated attributes, update the rules to use the new attributes.

Step 5: Refresh the Data Product
When you have completed the configuration changes, refresh the data product.

Updating Display Settings

On the golden records page for your data product, you can select which attributes are included in the golden records table in the Tamr Cloud UI.

When the data product refresh is complete, open the data product, and then select the Settings (gear) icon above the golden records table. Select the new attributes to include in the table.

Golden record table display settings

Updating Publish Configurations

After refreshing the data product, existing publish configurations for the golden records dataset are updated automatically to include the new attributes. To ensure that publishing succeeds if you do not make changes to existing publish configurations:

  • The deprecated attributes are not removed from the configuration; they are still selected for inclusion in the published dataset.
  • The new attributes are available, but are not selected for inclusion in the output, as shown below.



To publish the golden records dataset with the new attributes, either:

  • Add a new golden records publish configuration. After you remove the deprecated attributes from the data product configuration page, those attributes are not included in the publish configuration.
  • Update existing publishing configurations; de-select the deprecated attributes and select the new attributes. If you are publishing to Snowflake and change the publish configuration, you must either update the destination Snowflake table to match the updated schema or delete the destination table; otherwise, publishing will fail.

© 2025, Tamr, Inc. All rights reserved.

License Agreement | Privacy Policy | Data Security Policy| AI Chatbot Disclaimer