Search documentation...

K
ChangelogBook a demoSign up

Match rules

Identity resolution is only available on Business tier plans. You can use it with or without Customer Studio.

To set up identity resolution rules, you must first configure your input models. Then, you can define match rules.

This page goes through the match rule configuration.

Merge rules

Merge rules instruct Hightouch how should it should try to find connections between records. For example, two users may have the same emails, or two events may have the same anonymous id.

You can build complex merge rules using the merge rule builder to nest and/or conditions.

Hightouch supports the following comparison operators:

  • exact match
  • fuzzy
  • soundex

You can also use one of several transformations out of the box so you don't need to perform these transformations on your mdoels before hand:

  • case insensitive
  • normalize (convert multiple consecutive spaces to a single space and remove spaces from the beginning and end of strings)

Limit rules

Limit rules allow you to prevent merging records if they would violate some business rule that is important to your data.

For example, if you never want to merge two records if they have different user_id values, then you can specify a limit rule of 1 user_id per record.

Limit rule

Ready to get started?

Jump right in or a book a demo. Your first destination is always free.

Book a demoSign upBook a demo

Need help?

Our team is relentlessly focused on your success. Don't hesitate to reach out!

Feature requests?

We'd love to hear your suggestions for integrations and other features.

Last updated: Jul 11, 2023

On this page

Merge rulesLimit rules

Was this page helpful?