No Matches Found

Getting zero results from a matching run is a common issue, usually caused by configuration problems rather than a software error. Work through the checks below to identify what needs to be adjusted.

1. Check Field Mappings

In Match Definitions, fields from one datasource must be mapped to corresponding fields in the other datasource. Without mappings, there is nothing for the matching engine to compare.

• Open Match Definitions and verify that field mappings exist between your datasources.
• Confirm that the mapped fields contain actual data — use Data Profiling to check completeness (non-null %).

2. Similarity Threshold Too Strict

Fuzzy matching uses a similarity threshold to decide whether two values are "close enough" to match. If the threshold is set to High or Very High, only very similar strings will match, and records with any meaningful variation will be excluded.

Fix: Lower the similarity level to Medium or Low and re-run the matching job.

3. Wrong Match Type

Exact matching will only find records where the field values are character-for-character identical. It will not match "Jon" with "Jonathan," "Smith" with "Smyth," or "St." with "Street."

Fix: Switch to Fuzzy matching for name and address fields. Use Phonetic matching for fields where names may be spelled differently but sound the same.

4. Fields Are Mostly Empty

If the fields you are matching on contain a high percentage of null or empty values, few comparisons will produce a positive result.

Fix: Open Data Profiling and check the completeness rate of your matching fields. If completeness is low, consider matching on different fields or running Data Cleansing to populate missing values.

5. Incorrect Strategy for Single-Source Deduplication

If you are deduplicating records within a single file and the match strategy is set to Between Sources, the engine will look for matches across two different datasources — not within one. This produces no results when only one source is involved.

Fix: In Match Configuration, set the strategy to Within Source for single-file deduplication.

6. Match Job Was Not Re-Run After Changes

Saving new match definitions does not automatically re-run the matching engine. You must explicitly trigger a new match run.

Fix: Go to Match Results, click Run Match, and wait for the job to complete before reviewing results.

7. Data Cleansing Changed Field Values

If Data Cleansing transformed the fields used for matching (e.g., stripping all special characters from phone numbers), but the matching is running against the original uncleansed data, field values may differ significantly.

Fix: Confirm whether matching runs against cleansed or original data in your configuration, and ensure consistency.