What is Enrichment Match Evidence?
The short answer
Enrichment match evidence records why an incoming data record was selected for an existing account or contact.
Enrichment Match Evidence: why it matters
Commercial workflows depend on consistent account identity and useful information. A record or signal should support a defined sales question rather than simply add another populated field.
How to assess it in practice
Store the fields, selected entity and decision method so an incorrect enrichment can be diagnosed later. 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 enrichment match evidence. The reviewer’s task is to store the fields, selected entity and decision method so an incorrect enrichment can be diagnosed later. The outcome is recorded together with the supporting evidence; an unresolved question stays open rather than being converted into a positive result.
A lead lands with the wrong account owner after enrichment. The saved match key reveals that a shared domain, rather than the registration identifier, drove the decision.
Distinctions that matter
Enrichment Match Evidence belongs to the crm enrichment & maintenance topic family. Read CRM Data Enrichment 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
- Account-to-entity link
- Field mapping and authority
- Update history and correction route
The review should produce
An auditable enrichment outcome with clear ownership of changes and unresolved matching cases.
Across this family
Enrichment should respect the meaning and owner of each CRM field. Resolve the legal entity first, then decide which sourced attributes may update which account attributes. Track matching evidence and field changes so an apparently useful refresh does not silently overwrite a valid operational record.
A note from practice
Store the inputs, matched entity identifier, matching method and relevant confidence or rule version. A success flag alone makes an incorrect assignment difficult to diagnose or reverse.
Limits and common mistakes
The practical boundary is important: Store the fields, selected entity and decision method so an incorrect enrichment can be diagnosed later. 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?
How is Enrichment Match Evidence different from CRM Data Enrichment?
What should the result of the review contain?
Continue learning
Related topics
- CRM enrichment & maintenanceCRM Data EnrichmentCRM data enrichment adds or refreshes information about accounts and contacts using additional sources. For company accounts, that can include legal identifiers, industry, location, ownership or financial attributes where available. Effective enrichment starts by identifying the right entity and defining which source is allowed to update each field.
- CRM enrichment & maintenanceContact EnrichmentContact enrichment adds or refreshes information about a person’s business role or contact record.
- CRM enrichment & maintenanceAccount EnrichmentAccount enrichment adds or updates company-level information on an account record.
See the registry record behind every answer.
Primary, government-sourced data on 600M+ companies in 200+ countries, with full source attribution.