We are pleased to share the latest improvements in Tamr Cloud, including better enrichment results for firmographic enrichment data products, recent improvements, and fixed issues.

Better Enrichment Results for Company Mastering with Firmographic Enrichment Data Products

With improved logic to match your company data to available firmographic enrichment data, we are now able to enrich more of your source data with referential data from your selected provider. We now match your company records to enrichment data based not only company name and full address or country, but also by phone number. Tamr first tries to find a match based on company name and full address. If a match is not found, Tamr then tries to find a match based on the company name and country. Finally, if a match is not found, Tamr looks for a match based on phone number.

Additionally, we now provide similarity scores between key attribute values and the corresponding values returned by your selected data provider. These scores can help you validate the accuracy of firmographic enrichment. For example, Tamr calculates the similarity between the company name in the mastered entity and the company name returned by the data provider.

These improvements are available in newly created Company Mastering with Firmographic Enrichment data products. Learn more about Company Mastering with Firmographic Enrichment.

Other Recent Improvements

• In Designer, the Deliver Data to Studio step has been renamed to the Configure Attributes step for newly created data products.
• Curator improvements:
  • Users can now set table views using numeric operators (i.e., =, <, or >).
  • Similarity scores are only whole numbers now.
  • Simplified the experience of merging entities.
  • General styling improvements.

Fixed Issues

• Deduplication metrics could appear incorrectly after a flow failure.
• If you removed the attribute that stores the entity display name in the Designer Configure Attributes step (previously Deliver Data to Studio), your flow would fail to run and your data would not appear correctly. For company mastering templates, this attribute is company_name. For people mastering templates, this attribute is full_name. Now, this attribute cannot be deleted; you receive an error message if you attempt to remove it.
• The footer of the Source Records table did not appear.
• Flow runs could be stuck in a running state after a flow failure. Failures are now correctly showing.
• For editors and publishers, the Menu was showing the wrong options according to user roles and permissions.