What is Fuzzy match and Exact match in Informatica MDM?

 In Informatica Master Data Management (MDM), matching strategies are crucial for identifying duplicate records and ensuring data accuracy. Two common matching techniques are fuzzy match and exact match. Here's a detailed explanation of both:

Fuzzy Match

Fuzzy matching is used to find records that are similar but not necessarily identical. It uses algorithms to identify variations in data that may be caused by typographical errors, misspellings, or different formats. Fuzzy matching is useful in scenarios where the data might not be consistent or where slight differences in records should still be considered as matches.

Key Features of Fuzzy Match:

1. Similarity Scoring: It assigns a score to pairs of records based on how similar they are. The score typically ranges from 0 (no similarity) to 1 (exact match).
2. Tolerance for Errors: It can handle common variations like typos, abbreviations, and different naming conventions.
3. Flexible Matching Rules: Allows the configuration of different thresholds and rules to determine what constitutes a match.
4. Algorithms Used: Common algorithms include Levenshtein distance, Soundex, Metaphone, and Jaro-Winkler.

Exact Match

Exact matching, as the name suggests, is used to find records that are identical in specified fields. It requires that the values in the fields being compared are exactly the same, without any variation. Exact matching is used when precision is critical, and there is no room for errors or variations in the data.

Key Features of Exact Match:

1. Precision: Only matches records that are exactly the same in the specified fields.
2. Simple Comparison: Typically involves direct comparison of field values.
3. Fast Processing: Because it involves straightforward comparisons, it is generally faster than fuzzy matching.
4. Use Cases: Suitable for fields where exactness is essential, such as IDs, account numbers, or any field with a strict, unique identifier.

Use Cases in Informatica MDM

• Fuzzy Match Use Cases:

  • Consolidating customer records where names might be spelled differently.
  • Matching addresses with slight variations in spelling or formatting.
  • Identifying potential duplicates in large datasets with inconsistent data entry.

• Exact Match Use Cases:

• Matching records based on unique identifiers like social security numbers, account numbers, or customer IDs.
• Ensuring the integrity of data fields where precision is mandatory, such as product codes or serial numbers.

Fuzzy Match Examples

1. Names:

   • Record 1: John Smith
   • Record 2: Jon Smith
   • Record 3: Jhon Smyth

   In a fuzzy match, all three records could be considered similar enough to be matched, despite the slight variations in spelling.

2. Addresses:

   • Record 1: 123 Main St.
   • Record 2: 123 Main Street
   • Record 3: 123 Main Strt

   Here, fuzzy matching would recognize these as the same address, even though the street suffix is spelled differently.

3. Company Names:

   • Record 1: ABC Corporation
   • Record 2: A.B.C. Corp.
   • Record 3: ABC Corp

   Fuzzy matching algorithms can identify these as potential duplicates based on their similarity.

Exact Match Examples

1. Customer IDs:

   • Record 1: 123456
   • Record 2: 123456
   • Record 3: 654321

   Exact match would only match the first two records as they have the same customer ID.

2. Email Addresses:

   • Record 1: john.smith@example.com
   • Record 2: john.smith@example.com
   • Record 3: john_smith@example.com

   Only the first two records would be considered a match in an exact match scenario.

3. Phone Numbers:

   • Record 1: (123) 456-7890
   • Record 2: 123-456-7890
   • Record 3: 1234567890

   Depending on the system's configuration, exact match may only match records formatted exactly the same way.

Mixed Scenario Example

Consider a customer database where both fuzzy and exact matches are used for different fields:

1. Record 1:

   • Name: John Smith
   • Email: john.smith@example.com
   • Phone: (123) 456-7890

2. Record 2:

   • Name: Jon Smyth
   • Email: john.smith@example.com
   • Phone: 123-456-7890

3. Record 3:

   • Name: Jhon Smythe
   • Email: john_smith@example.com
   • Phone: 1234567890

In this case, using fuzzy match for the name field, all three records might be identified as potential matches. For the email field, only records 1 and 2 would match exactly, and for the phone field, depending on the normalization of phone numbers, all three might match.

In summary, fuzzy matching is useful for finding records that are similar but not exactly the same, handling inconsistencies and variations in data, while exact matching is used for precise, identical matches in fields where accuracy is paramount.

Learn more about Informatica MDM here