What is Match Recall?

  • Company data & APIs
  • Matching confidence & evaluation
  • 3 min read

The short answer

Match recall measures the proportion of true matches recovered within a defined evaluation set.

Match Recall: why it matters

Automated company-data workflows need clear meanings and traceable transformations. An operation that runs successfully can still produce a result that is unsuitable for the intended business question.

How to assess it in practice

For match recall, retain the specific source, scope and effective date, and distinguish verified facts from assumptions before using the result in a decision. Start by defining the question the team needs to answer. Identify the relevant record or evidence, check its scope and date, and retain the reasoning behind the result. If evidence conflicts, keep that conflict visible for review.

Worked example

Illustrative workflow: a team reviewing a business adds a separate check for match recall. The reviewer’s task is to for match recall, retain the specific source, scope and effective date, and distinguish verified facts from assumptions before using the result in a decision. The outcome is recorded together with the supporting evidence; an unresolved question stays open rather than being converted into a positive result.

Illustrative scenario

A test set contains 100 true links and the system recovers 80: recall is 80%. Review missed cases before claiming that a high acceptance precision means broad coverage.

Distinctions that matter

Match Recall belongs to the matching confidence & evaluation topic family. Read Probabilistic Matching alongside it to understand the adjacent question. Each page has its own intended scope; shared context does not make the concepts equivalent.

Evidence and review output

Review these

  • Representative labelled examples
  • Threshold and error definitions
  • Ambiguous and conflicting cases

The review should produce

An evaluated matching policy with explicit trade-offs and a route for unresolved candidates.

Across this family

Evaluation must state which entities, labels and thresholds the measurements describe. Precision, recall and confidence answer different questions. Include difficult common-name and cross-border cases so good results on easy records do not conceal failures that matter operationally.

A note from practice

Recall is recovered true matches divided by all true matches in the evaluation set. Estimating it requires a credible set of known matches, not merely counting accepted results.

Limits and common mistakes

The practical boundary is important: For match recall, retain the specific source, scope and effective date, and distinguish verified facts from assumptions before using the result in a decision. Do not substitute a related label for this check or assume that missing information is a negative finding. Source-specific and jurisdiction-specific rules require their own review.

Frequently asked questions

Which evidence should I review?

For this topic, focus on representative labelled examples, threshold and error definitions, ambiguous and conflicting cases. The relevant source and dates should be retained with the finding.

How is Match Recall different from Ambiguous Entity Match?

An ambiguous entity match leaves multiple plausible entities unresolved by the available evidence. The distinction matters because the evidence needed for that concept may not resolve the question addressed on this page.

What should the result of the review contain?

An evaluated matching policy with explicit trade-offs and a route for unresolved candidates. Preserve material conflicts instead of replacing them with an unexplained success flag.

Continue learning

See the registry record behind every answer.

Primary, government-sourced data on 600M+ companies in 200+ countries, with full source attribution.