2026 research editionSee how 13 platforms were evaluated
Data origin map

Lead Capture vs Lead Identification vs Lead Enrichment

Three adjacent jobs, three different data origins, and three different consent boundaries.

Three jobs that create different records

Capture asks a person to provide information. Identification resolves observed activity to a person or company. Enrichment appends facts or signals to a record that already exists. The verbs sound adjacent, but the resulting confidence and permission are not interchangeable.

JobStarting pointData originWhat it can establish
CaptureA visitor chooses to respondDeclared first-party dataIdentity, needs, preferences, permission, score
IdentificationAnonymous or partial activityResolution provider and observed behaviorLikely account or person, pages, recency
EnrichmentAn existing identifierData provider or connected systemCompany, role, verification, signals

Provenance belongs on the record

A useful lead record should retain the source, collection method, provider, timestamp, verification state, consent or permitted-use basis, and downstream restrictions. Removing provenance creates false confidence and makes later quality analysis weaker.

  • Record who supplied each field.
  • Keep observed behavior separate from declared intent.
  • Preserve verification timestamps.
  • Do not infer person-level permission from company identification.
  • Route disputed or contradictory fields for review.