Below are some common or basic examples of both Dedupe+ and Merge rules.
This rule will identify any active accounts with names that match the current account record through the Company Fuzzy Name rule set. It makes use of the real-time checking functionality, and is enabled for use with the global search function. It will check all records, regardless of the current users access rights (permissions).
With the default configuration, the 'fuzzy company name match' rule set will compare strings ignoring common legal terminators such as 'ltd', 'limited', 'plc' etc.
There are a whole bunch of fuzziness options available to customise how the rule set identifies potential duplicates. For this example, the below configuration was used:
This configuration will match names with spelling mistakes and spelling variations (such as '8' versus 'eight'), regardless of legal terminators.
For demonstration purposes, variants of the Data8 account were created with mistakes, various legal terminators etc. Using the global search feature, Data8 returned the following results:
Here we can see some of the fuzziness options that were set up coming into play. For example, Data8 Eight Ltd was detected as a potential duplicate thanks to the 'standardise numbers and symbols' option, and The Data 8 was matched due to the 'ignore common leading words' and 'allow a company name with no legal terminator to match one with a legal terminator' options being enabled.
This is a simple yet effective dedupe+ rule, designed to only allow a single person at a single account.
The sample of data we often use for this would be "Mathew Jones at Data 8 Ltd" would match "Matthew Jones at Data Eight".
If any of the duplicated Accounts/Contacts/Leads preferences are marked as “Do Not Allow” then this value must be carried over as Output.
- 3 duplicated Accounts.
- 1 account has the ‘Do not allow phone Calls’ field marked as “Do Not Allow”. No matter what the values are of the other Accounts, I must retain this Preference.
Merge+ Rule Setup
Here we created a Merge+ rule for the account entity. We added a Filter & Sort rule to the suitable Contact Preferences field, in this case: Do Not Email.
This rule configuration will sort all duplicates by true value first and then take the value of the first (master) record. Therefore, if any of the duplicates have a true value, the true value will be used.
Some text here explaining the use case of the merge rule.
Merge+ Rule Setup
Some text here explaining the setup of the merge rule and why.