Identity
Is this the person you intended to find?
Check the name, employer and professional profile together. A similar name is not enough.
Data quality that matters in practice
A filled field
is only useful if
you can act on it.
The right person. A useful contact channel. Enough context to make the next decision. Assess contact-data quality where it matters: in the records and workflows your team actually uses.
20 emails + 5 business-phone results included
What makes a usable record?Quality dimensions
Right personIdentity and employer agree
IdentityUseful contact fieldsEmail and phone assessed separately
CompletenessCurrent contextCheck changes in role and company
FreshnessClear outcomeMissing fields remain visible
ConsistencyA practical review framework. These labels are not verification results for a live record.
Four questions behind a useful record
Look beyond the headline match rate.
Finding more records is valuable when those records help your team reach the right professionals. Separate completeness from correctness and current context.
Completeness
Did you get the channel you need?
Assess email and phone separately. A phone-only result does not complete an email campaign.
Freshness
Does the context still fit?
Look for changes in employer, role or company. Retrieval time is not a source verification date.
Consistency
Can your systems use the result?
Keep result status and missing fields clear. Preserve the distinction between no data and a technical error.
Make enrichment improve the record
Fill the gaps. Protect the facts your team has confirmed.
A CRM record may contain customer-provided information, rep updates and data from several suppliers. Decide which fields enrichment can change before connecting it.
Use a field-by-field rule: fill an empty email, review a changed employer, and retain a customer-confirmed value when a new response conflicts with it. Keep the request reference with the update so the result can be traced.
Explore CRM enrichment recipesA practical CRM update policySuggested workflow
Work email is emptyFill with an accepted result
Employer has changedReview before overwriting
Customer confirmed the phonePreserve the trusted value
Phone was not returnedKeep the current value
Lookup encountered an errorRetry according to the error
These are recommended integration rules. Your application controls CRM writes; the enrichment response does not enforce your merge policy.
A benchmark your team can defend
Decide what good looks like before running the lookup.
Choose a sample that reflects the markets, roles and account types you actually target. Keep the same inputs and acceptance criteria when comparing providers.
Check the intended person
Use known reference records to review identity and employer fit. Record mismatches separately from missing results.
Assess each channel
Measure email availability, accepted email results and usable phone results separately. Do not classify unknown phone types as confirmed mobiles.
Calculate a useful denominator
Report the share of your original sample that returned accepted results. Keep partial and no-match records in the sample.
Record the conditions
Keep the test date, identifiers, field definitions and relevant costs. Repeat for the markets that drive your business.
Comparable measurements
Measure the outcome, not just the filled field.
Run the same input sample through each provider. Record country, role, test date and sample size alongside these calculations.
| Metric | Calculation | What it answers |
|---|---|---|
| Email match rate | Returned work emails ÷ submitted contacts | How often is an email available? |
| Accepted email coverage | Identity-confirmed, usable emails ÷ submitted contacts | How much of the original sample can you use? |
| Business-phone coverage | Returned business phones ÷ submitted contacts | How often is any business phone available? |
| Mobile coverage | Independently classified mobiles ÷ submitted contacts | How often is the specific number type available? |
| Cost per usable result | Total test cost ÷ accepted results | What does a usable result actually cost? |
| Latency | Median and 95th percentile request duration | How does lookup affect your workflow? |
Calculation example, not a TargetWise performance claim: 1,000 submitted contacts, 700 returned emails and 640 accepted emails means 70% match rate and 64% accepted coverage. An initial Free-plan test checks integration fit; it is not a country-level benchmark.
Clear information, better decisions
Know what a result tells you.
Use the evidence in the response for what it establishes. That makes the data easier to trust and the workflow easier to maintain.
| What you see | What it tells you | What to check next |
|---|---|---|
| Work email returned | An email was available for the contact result. | Identity fit and the email validation needed by your workflow. |
| Business phone returned | A number was available; the current API phone type is unknown. | Whether the number is suitable for your intended calling channel. |
| Retrieval timestamp | When TargetWise fetched the result. | Whether current employer and role context still fit. |
| Partial result | Some requested data was unavailable. | Whether the returned fields are enough for the next action. |
| Source details included | The supported company route supplied provenance. | The source and field context relevant to your decision. |
Your questions, answered
Before you get started.
Details to help you choose and put the data to work.
Explore the documentationTry TargetWise
See what TargetWise finds for your team.
Start with real contacts from the accounts you want to reach. Your free plan includes 20 emails and 5 business-phone results.