We’re on it! We will reach out to email@company.com to schedule your demo. So we can prepare for the call, please provide a little more information.
We’re committed to your privacy. Tamr uses the information you provide to contact you about our relevant content, products, and services. For more information, read our privacy policy.
Eleni Partakki
Eleni Partakki
Solutions Engineering Lead
SHARE
Updated
May 6, 2025
| Published

Tamr Updates <1 Minute: April 2025

Eleni Partakki
Eleni Partakki
Solutions Engineering Lead
 Tamr Updates <1 Minute: April 2025

Tamr just dropped a trio of features that make it easier than ever to get data into the platform, trigger jobs from it, and master customer records across languages using AI-native MDM techniques. Watch the < 1 minute video and read on for everything you need to know (and why you’ll care). 

Click‑Configure Webhook Connections

Need your downstream systems to spring into action the moment fresh records hit Tamr RealTime? We hear you. Simply add a new connection (webhook) and paste the endpoint you want events sent to—that’s it. Tamr now handles the CloudEvents‑formatted payloads for Create/Update actions automatically, so you can daisy‑chain workflows without writing glue code. With this functionality, fire off a dbt Cloud job when a golden record is updated, or drop a Slack alert when a high‑value customer appears in the System of Record (SOR).

More Source File Formats, Less Friction

Is your data lake a jungle of file types? No problem. When you create a Source Dataset from ADLS, GCS, or S3, you can now pick Avro, Delta Lake tables, JSON (newline‑delimited), and the existing Parquet and CSV staples. Browse, preview, or even tweak settings in the revamped Sources UI before hitting Add. One connector, many shapes. 

Cross‑Alphabet Matching with Name Transliteration for B2C Customers

For B2C customer mastering, matching names written in different alphabets can pose a challenge—for example, recognizing that “乔治” and “George” or “Иван” and “Ivan” may refer to the same individual. Transliteration for names helps bridge that gap in entity resolution, especially for multi-language customer data use cases. It is enabled by default in our B2C Customers data product and allows you to:

  • Convert first, middle, family, and full names using the ICU transliteration library
  • Feed those Latin‑ized values into clustering so names like “José” and “Jose” finally link up
  • Emit the transliterated fields (transliteration_first_name, etc.) if you need them downstream

Check out this short video to see these new updates in action. 

Where to Learn More

Visit Tamr Cloud Docs to get step‑by‑step setup guides, schema details, and API snippets.

Get a free, no-obligation 30-minute demo of Tamr.

Discover how our AI-native MDM solution can help you master your data with ease!

Thank you! Your submission has been received!
For more information, please view our Privacy Policy.
Oops! Something went wrong while submitting the form.