What's New: Multiple Email and Phone Number Support in B2C Customers
You can now configure multiple phone and email types in the B2C data product. In the Configure Data Product page, phone and email attributes are now organized into different groups, representing different types of phone numbers and email address associated with customers. These groups also include attributes that track customer consent for SMS, voice, and email communications.
See B2C Customers Data Product for more information about consent attributes and using the new attributes in your data product.
Updated Data Product Schema
The data product schema includes Mobile Phone and Personal Email attributes by default. You can choose to include attributes for additional phone number and email address such as: work, office, and other.
New Attributes in the UI and Published Datasets
The phone and email types are included in the attribute names in golden records - both in the UI and in published data. For example, notice in the images below that the mobile phone attribute names include “mobile”.
Golden record pages

Publish configurations

360 customer views
You see all email addresses and phone numbers for each contact on the 360 page, including whether the customer has opted-in to communications on that channel.

Migrating to the New Attributes
If you have existing B2C Customers data products, the new phone and email options are available automatically, but your existing configuration is not changed.
You can continue to run the data product and publish results without making any changes to the current data product configuration.
You can update the attribute mapping to take advantage of the new phone and email groups. This involves:
- Updating the data product configuration and refreshing the data product.
- Updating display settings.
- 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 phone and email attributes, prompting you to remove these mappings and re-map the attributes to the new phone and email attribute groups.

The Refresh Data Product button is still enabled; you can refresh the data product without remapping the attributes.
Step 1: Remap Attributes
To remap fields to the new attribute groups:
- Map the phone and email group attributes for each source dataset.
- Remove the mappings for the deprecated address attributes. After you remove the mappings, the deprecated attributes are removed from the schema.
Important: Once you begin mapping to the new phone or email groups, 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 (Mobile, Office, and so on) to open the configuration rules.

Step 3: Select Attributes to Include in Uniformity Scores
For each attribute in the phone or email attribute group, 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.

Step 4: Update Clustering Rules
If you have existing clustering rules that refer to the deprecated phone or email 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 Phone and Email attributes to include in the table.

Updating Publish Configurations
After refreshing the data product, existing publish configurations for the golden records dataset are automatically updated to include the new attributes. To ensure that publishing succeeds if you do not make changes to existing publish configurations:
- The deprecated address attributes are not removed from the configuration; they are still selected for inclusion in the published dataset.
- The new phone and email 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.