Identity matching connects records or activity to an entity. The important question is how that connection is made and what evidence supports using it.
We publish this guide at Leadpipe to help buyers evaluate identity outputs. Leadpipe describes its matching approach as deterministic and uses its own identity graph. Those are product characteristics; a buyer still needs to review coverage and correctness on the intended inputs.
How the approaches differ
| Dimension | Deterministic matching | Probabilistic matching |
|---|---|---|
| Decision rule | Specified identifiers or linking rules establish a match | A model or scoring method estimates a match |
| Typical input question | Do these identifiers satisfy the required linkage? | How strongly do these signals support the same entity? |
| Important failure modes | Shared, stale or incorrectly linked identifiers | Ambiguous signals, poorly calibrated scores or thresholds |
| Evaluation need | Validate identifiers and linking policy | Validate calibration, thresholds and outcomes |
| Buyer requirement | Explain evidence behind the link | Explain confidence and handling of uncertain cases |
A deterministic process can produce an incorrect result if an input or an earlier graph link is wrong. A probabilistic process should not be treated as proven wrong simply because it uses inference. The relevant evidence is how the configured system behaves on the population and task being evaluated.
Separate an identifier from a person
An email address, browser identifier or household connection does not carry the same meaning in every workflow. Shared devices, role mailboxes and old employment records can complicate interpretation. Ask what entity each identifier represents and how the provider handles changes over time.
For website identification, ask whether the returned row represents a visiting company, an independently supported individual match or a suggested contact. The person-versus-company guide explains the practical distinction.
Coverage and correctness are separate
A system may return fewer records because its acceptance rules are stricter or because it has less relevant data. A system returning more records may have broader coverage or a different rule. The return count alone does not distinguish those explanations.
Measure unique output against eligible input for coverage. For correctness, use independently established ground truth. Where it is unavailable, label the result unknown. Our measurement guide defines the denominators and evidence requirements.
Questions to ask the provider
- Which identifiers and sources support this match?
- What entity does the output represent?
- How are conflicting or stale identifiers handled?
- Can the system leave an identity unresolved?
- What happens when a person changes employer or shares a device?
- How can a customer correct, suppress or delete a record?
- Which evidence can be inspected without exposing unrelated personal data?
These questions should apply to Leadpipe and competitors equally. Do not infer a competitor’s implementation from its brand or an old comparison article.
Match the review to the action
An account-prioritization process may use a company signal and require a rep to research the buying group. A person-specific message requires stronger evidence about the person. Automated actions need clear acceptance and suppression rules because errors can propagate quickly.
Keep the original signal and its evidence with the record. Do not transform a suggested contact into a confirmed visitor merely because it entered the CRM. Separate record acceptance from message approval and allow a person to review ambiguous cases.
Evaluate Leadpipe on your requirements
Leadpipe identification supplies eligible website visitor records for sales workflows. Person-level coverage is strongest in the US. EU/UK defaults to company-level, with person-level requiring affirmative consent. Confirm required fields and delivery on actual traffic.
The trial scorecard supports a consistent review. Check current plans or start a trial: 7 days or 500 profiles, whichever comes first, no card.
