Account 360 Match Rules

Match rules are used to identify duplicate profiles and either merge them or flag them as Potential Matches.

Account 360 has the following match rules defined out of the box:

Table 1. Organization Match Rules
S. No Rule
1 Exact DUNS Number (Automatic)
2 Exact Name, City, Zip5, state, ID, ID Type and Fuzzy Address Line1 (Suspect)
3 Exact City, State and Fuzzy Name and Address Line1 (Suspect)
4 Exact URI, and SuspectMatchFlag=true (Automatic)
5 Exact URI, and AutoMatchFlag=true (Suspect)
Note: Rules 4 and 5 are only used by the Real Time D&B connector to process matches that are returned from D&B.
Table 2. Contact Match Rules
S. No Rule
1 Exact (First Name, Last Name) Exact or Null (email)
2 Exact (FirstName, LastName, Address Line 1, City, Country ,Identifier, Type), Exact Or Null (Gender)
3 Exact (Address Line 1, Zip5, Country), Exact or Null (Suffix Name, Zip4), Fuzzy (First Name, Last Name)
4 Exact (First Name, Last Name, Zip5, Country), Fuzzy(Address Line 1)
5 Exact(Email), Fuzzy(FirstName, LastName)
Note: All the Contact match rules Suspect Match rules, which can be changed to automatic rule if needed once data analysis and requirements have been completed.
Table 3. Location Match Rule
S. No Rule
1 Exact (Address Line1, City, State, Country, Zip5, Verification Status), Exact or All Null (Address Line 2, Street, Sub Building, Zip 4), Verification Status = 'Verified'.
Note: Depending on the implementation done in your tenant, you may or may not have Location entity in your tenant. Use of the Location entity is deprecated in Account 360, and the entity is disabled. Users should use the Addresses nested attribute instead.