Vencavo’s data foundation contains 299M+ contact records and 25M+ company records. Record counts describe the size of the foundation. They do not establish unique-person totals, field completeness, matching accuracy, or freshness for a specific task.
Evaluate the records and fields relevant to your integration. Contact us to discuss representative inputs, required evidence, and acceptance criteria. This document defines the review questions; it does not publish a measured accuracy score or a universal refresh guarantee.
Keep provenance with the value
Review the evidence for each field rather than assigning one quality label to the entire record. A useful evaluation preserves the supplied value, source reference where available, date context, and the review decision.
When observations disagree, keep both values and their evidence until the conflict is resolved. A source that supports a company name does not automatically support its headcount, a person’s role, or a reporting relationship. Confirm available provenance and permitted uses for the selected delivery.
Separate the clocks
An event date describes when a change happened. An observation date describes when a system saw supporting evidence. A verification date describes a particular review. Keep these meanings distinct when assessing freshness.
An observation made today can concern an older event. A verification date cannot replace the event’s effective date. If a timestamp is absent, retain the unknown rather than substituting the time an agent asked its question.
Set an acceptable age for each field in the context of the task. Ask about the applicable source, timestamp precision, and refresh behavior during the integration assessment.
Resolve identity before joining records
Confirm that a result belongs to the intended entity before using its fields. Company names can collide, and a parent company, subsidiary, or product can need different treatment.
Review identifier semantics and matching behavior with representative cases. In the website examples, reserved .example domains and explicitly illustrative local IDs explain the joins. They are not production identifiers.
Keep a person, role, company membership, and reporting edge separate. A supplied title or department does not establish a manager or purchasing authority.
Preserve unknowns
Distinguish a supplied value from an unknown value. Missing data does not mean zero, false, or a verified negative. Confirm how the integration represents unavailable, restricted, and not-applicable fields.
In the fictional website examples, production_verified_at is null because no production verification applies to those records. Agents must carry that boundary into summaries rather than inventing evidence to complete a sentence.
Review a field against the task
The fictional employee band 51–200 illustrates the distinction. It is a supplied sample value, not an independently verified headcount. Converting the band to its midpoint would invent precision.
| Question | What to record |
|---|---|
| Is this the intended entity? | Confirmed, incorrect, or unresolved match |
| Is the field supplied? | Present or missing, independent of correctness |
| Can the value be checked? | Supporting evidence and a reviewer decision |
| Is the evidence recent enough? | Relevant date and the accepted age for this field |
| Do observations conflict? | Both values, their references, and the resolution rule |
| Can the field be used in this workflow? | Applicable usage requirements and the agreed delivery scope |
Report incorrect matches, missing values, and unverifiable values separately. A complete-looking record can still fail the requirements of your workflow.
Use the provider evaluation guide to define a representative sample. The field provenance guide contains a worked ledger, and the role-change guide separates event, observation, and verification times. For delivery-specific questions, talk to Vencavo.