Contact level data is information about one named person at a company, such as name, job title, employer, email address and phone number, as opposed to account level data, which describes the company. It becomes usable for sales only when each field carries a source, a date and a check, and when the person passes the account fit and stop fields below. Build it in order: ICP, research, a verified contact, qualification, then a CRM action. A confident score on a record is a reason to look, not a decision to call.
Contact Level Data: The Short Answer
- Fact: the term is used for three different things. Glossaries use it for the fields that identify and reach a person. Vendors also use "contact-level" for person-level advertising and person-level intent. A company named ContactLevel sells contact-level advertising under that brand name.
- Fact: vendor documentation labels contact records with confidence indicators, and those indicators measure different things. ZoomInfo's Contact Accuracy Score covers employment and email correctness, not job role, and Apollo's email status covers the address only.
- Inference: a contact record can pass every vendor check and still fail qualification, because the person may not sit in the buying group or may be in a stop state.
- Opinion: the useful unit is a stamped field, not a record. A field with a source, a date and a check can be trusted or challenged; an unstamped field is a guess.
- Fact: Lead Seeker supplies verified contacts with source-backed signals. It does not identify website visitors, does not run ads and does not decide who qualifies. That stays with your team.
What the Term Covers
Three meanings sit under the same words. Name the one you need before you buy or build anything.
| Meaning | What it describes | Source | What it is not |
|---|---|---|---|
| Contact data | Names, email addresses, phone numbers and physical addresses of people | Compelling.ai glossary (no date shown), which also notes that "contact data" and "contact information" differ in scope | A statement that any field is current |
| Person-level behaviour | Which individual is researching or engaging, as opposed to which company | Leadpipe guide to person-level intent, September 16, 2026, which says most intent data is company-level | A contact record; it needs a record to attach to |
| Contact-level advertising | Reaching a named person with ads on platforms such as LinkedIn, Meta and Google | ContactLevel product page, which states 70% to 99% match rates; the Clay listing says the vendor finds SHA-256 hashed emails from a profile URL, email address or phone number | A sales-ready contact; a match rate measures reaching a person on an ad platform |
Inference: the third row's match rate and the second row's behaviour data answer a different question from "is this person right for us and reachable?". This guide covers the first meaning and shows where the others attach.
From ICP to CRM Action: Five Steps
Fact: 6sense's guide to B2B contact databases (September 14, 2024) lists the same order in its own words: define the ideal customer profile, source reliable data, use technology, verify and cleanse, then segment. This guide adds the checks that sit between a record and a CRM action.
| Step | What happens | Who owns it | Output |
|---|---|---|---|
| 1. ICP | Write the company fit and the roles that buy | Marketing proposes, sales agrees | Written criteria, with disqualifiers |
| 2. Research | Find the account and the person from sources you can open | Marketing or an enrichment tool | Candidate people, each with a source link |
| 3. Verified contact | Stamp each field with source, date and check | Whoever supplies the record | A stamped record |
| 4. Qualification | Test account fit, role and stop fields; a person decides | Sales | Accepted, rejected or parked, with a reason |
| 5. CRM action | Create the record, set an owner and a next step | Sales operations or the rep | A task with a named owner and a date |
For the full set of fit criteria and handoff rules, see the B2B lead qualification framework from ICP to CRM action. For the person-to-address chain, see B2B contact verification methods. Opinion: do not start step 2 until step 1 lists the disqualifiers, because a long list of well-verified people at the wrong accounts is still wasted effort.
The Field Stamp
A Field Stamp is three marks attached to one field of a contact record: where the value came from, the date it was seen, and the check that was run. It is this guide's own tool.
| Field | Source mark | Date mark | Check mark | What it proves | What it does not prove |
|---|---|---|---|---|---|
| Full name | Company page, filing or profile | Date seen | Matches a second origin | That the person is named at this company | That they still work there |
| Job title | Company page or posting | Date seen | Matches the employer's wording | What the title said on that date | Authority over your purchase |
| Employer | Company page or profile | Date seen | Legal entity matched | Which company, not which subsidiary | Current employment |
| Email address | Provider or company pattern | Date checked | Verification status | The mailbox accepted the check at that time | That a message will be delivered |
| Phone | Provider or company page | Date checked | Answered or confirmed | A number existed | That the person will take the call |
| Buying role | Your own reading of the record | Date set | Sales confirmation | A hypothesis from a title | That the person decides |
Fact: ZoomInfo describes its Contact Accuracy Score as a calculated indicator of whether a contact is employed at the profiled company and whether the profiled email is correct and current, computed from factors including NeverBounce email validation, richness of the record and how recently data was validated. Inference: that covers two stamped fields, employer and email, and says nothing about title authority or buying role. For the full chain behind the address field, see the Nine-Link Chain.
What Vendor Documentation States
The table lists what each page states and what it leaves open. "Not stated" means the page cited does not say.
| Source (date shown) | What it states | What it leaves open |
|---|---|---|
| ZoomInfo help, Overview of the Contact Accuracy Score (March 4, 2026) | Scores range from 75 to 99; guidance puts expected bounce at about 2 to 3% at 95+, 7 to 9% at 85+ (the default) and 9 to 11% at 75+; a person who left a year earlier can still score 97 because the score "reflects confidence, not a guarantee" | The score is the vendor's own; it covers employment and email, not role |
| Apollo knowledge base, Understand Email Statuses (no date shown) | Statuses are Verified, Unverified, Update required, Unavailable and User-managed; an Apollo-verified email that bounces within 30 days of purchase gets its credit refunded; unverified addresses can raise bounce risk | Covers the email field; no status for title or buying role |
| 6sense, B2B Contact Database: What to Look For (September 14, 2024) | A contact database holds names, job titles, phone and email, plus company name, industry, size and revenue; steps are ICP, reliable sources, technology, verification, segmentation | Mixes person fields and company fields in one list; gives no field-level checks |
| ContactLevel, product page (no date shown) | Person-level ad targeting across several platforms at 70 to 99% match rates | The figure is the vendor's own; it describes ad matching, not field accuracy |
| FTC, CAN-SPAM Act: A Compliance Guide for Business (no date shown) | The law covers all commercial email and makes no exception for business-to-business email; each violating email can carry penalties up to $53,088 | It does not address any vendor's data |
Reading: each source covers a different slice. None attaches a source and date to every field, and none says how a role is confirmed. The Field Stamp and the stop fields below fill those gaps.
The Stop Fields
A Stop Field is a field value that ends qualification, however good the rest of the record looks. Write them in step 1 and check them in step 4.
| Stop field | Value that stops the record | Why |
|---|---|---|
| Employment | Evidence the person has left the company | Apollo's "Update required" status exists for job changes; ZoomInfo notes old addresses can keep scoring high |
| Role | Title far from your buying group | A high score does not make the person a buyer |
| Account fit | Company outside the ICP | A verified person at the wrong company is still a wrong yes |
| Suppression | Prior opt-out, existing customer or active competitor | The FTC guide gives recipients the right to have you stop emailing them |
| Email check | Unverified or unavailable status with no second check | Apollo says sending to unverified addresses can increase bounce risk |
| Provenance | No source or date on the field | A field you cannot trace cannot be defended |
The Cost of a False Positive
A false positive is a record that passes into sales and should not have. There are three kinds, and each costs something different.
| Kind | What goes wrong | What it costs |
|---|---|---|
| Wrong person | Left, or never held the role | A bounce, or a message to someone who cannot act |
| Wrong account | Company outside the ICP | Rep time and sender reputation on a dead end |
| Wrong action | Account interest read as a decision | A call booked for a person with no need |
Fact: ZoomInfo's own guidance expects about 7 to 9% bounce at its default 85+ setting. Illustrative arithmetic, with invented inputs: at that range, a list of 1,000 records would carry roughly 70 to 90 addresses that bounce. If each wrong record costs a rep ten minutes to discover and discard, 80 of them cost about 13 hours before a single reply. Inference: the useful measure is wrong records found after sales has touched them, which most CRMs can count if the rejection reason is recorded.
Worked Example
The company and numbers are invented to show the format.
Pellworth Cloud sells observability software to mid-sized retailers. Its ICP names retailers in one size band, and disqualifies retailers already on a competitor's multi-year contract. A research pass finds a candidate: a platform engineering director at a retailer that posted a platform role this month.
| Field | Stamp | Result |
|---|---|---|
| Name | Company engineering page, seen 2026-10-12, matched on a professional profile | Pass |
| Title | Same page; the posting names the team | Pass |
| Employer | Legal entity matched; not the parent | Pass |
| Verification status verified, checked 2026-10-12 | Pass | |
| Buying role | Evaluator, set by marketing; not yet confirmed | Parked |
| Stop fields | No opt-out, not a customer, no competitor contract found | Clear |
| Sales decision | Accepted for one researched first message | Action: task for the account owner, due in two days |
Inference: the buying role is the one field sales has to confirm, so the CRM record shows it as a hypothesis until sales confirms it. For role mapping across the account, see B2B buying committee mapping.
Where Lead Seeker, Percepture and Pyra Fit
Lead Seeker is not a contact database in the sense of a static list. Following how Lead Seeker works, you describe the ICP and the roles that buy, it scans public signals and returns a dossier with a verified contact and the trigger, and it syncs to Salesforce or HubSpot. Opinion: that fits steps 2 and 3 of the chain. Step 4 stays with your team, and Lead Seeker does not score or decide. Lead Compass is an on-demand signal strategist that cites public sources where available and spends no Lead Units until a search is run. For the cost per usable contact across providers, see the best B2B contact database ranking.
Lead Seeker pricing, from its live pricing page checked October 25, 2026: Pilot $99 one-time; Starter $149 per month; Growth $499 per month; Scale $1,299 per month; Enterprise from $4,500 per month.
Percepture's guide to intent data to identify sales qualified leads covers the step from signal to a lead sales will accept. Percepture is the agency Bob Generale leads, and Pyra is a related AI agent and automation company; both are related to Lead Seeker. Pyra fits only if you later want follow-up automated after a contact is accepted.
How to Run It
- Write the ICP and the stop fields first, with sales agreeing both.
- Research from sources you can open, and log the source link with the person.
- Stamp every field with source, date and check; leave a field blank rather than guess it.
- Run the stop fields, and reject or park any record that hits one.
- Let a person on the sales side accept, reject or park, with a reason.
- Create the CRM action with an owner and a date, and keep the stamps on the record.
- Count rejected records by reason each month, so you can see which source or step lets false positives through.
Limitations
- This is a documentation-based comparison, not a hands-on product test.
- Documents change. Vendor documentation and service requirements can change.
- "Not stated" is scoped to the page cited. A vendor may check fields its help pages do not list.
- Only five sources are compared. Cognism, Demandbase, Leadfeeder and others are not covered.
- Vendor figures are the vendors' own, including the ZoomInfo bounce ranges and the ContactLevel match rates; their methods are not shown in full.
- No source compared tests how accurate any contact field is, so none is asserted here.
- The Field Stamp and the Stop Fields are editorial methods, not standards.
- The worked example and its numbers are invented.
- Legal points are limited to what the FTC guide states. Other rules depend on your sender, your recipient and your location; ask counsel.
- Related-party rows rely on their own pages. Lead Seeker publishes this guide, and Percepture and Pyra are related companies.
Frequently Asked Questions
What is contact level data?
It is information about one named person at a company: name, title, employer, email, phone and similar fields. Account level data describes the company. Some vendors also use "contact-level" for person-level advertising or intent.
Is contact level data the same as account level data?
No. Account data describes a company, such as industry and size. Contact data describes a person at that company. Qualification needs both: the account must fit, and the person must be reachable and relevant.
How do you know contact level data is accurate?
Check each field, not the record. Note where the value came from, when it was seen and what check was run. Vendor scores help, but ZoomInfo's own documentation says its score reflects confidence, not a guarantee.
How This Guide Was Built
The Field Stamp, the Stop Fields, the five-step chain and the example are this guide's own editorial methods, not vendor features or benchmarks. Every source is read against the same columns, and a cell is filled only from a named page or marked "Not stated". The vendor help pages are primary sources for their own scores and statuses. The FTC guide is the primary source for the email law it describes. The 6sense guide, the Leadpipe guide, the Compelling.ai glossary and the ContactLevel pages are interested or secondary sources and are labeled so. The labels Fact, Inference and Opinion mark what a source states, what follows from it and what the author recommends. Nothing here is a hands-on test of a product or a client result. This is an October 25, 2026 snapshot.
Sources
- ZoomInfo, Overview of the Contact Accuracy Score, March 4, 2026.
- Apollo, Understand Email Statuses.
- 6sense, B2B Contact Database: What to Look For, September 14, 2024. 6sense sells intent and contact data.
- ContactLevel, product page, and Clay, Contactlevel integration. ContactLevel sells contact-level advertising.
- Leadpipe, Person-Level Intent Data: How It Works (2026), September 16, 2026. Leadpipe sells person-level intent.
- Compelling.ai, Contact Data.
- FTC, CAN-SPAM Act: A Compliance Guide for Business.
- Percepture, How to use intent data to identify sales qualified leads. Percepture is a company Bob Generale leads.
- Lead Seeker, Lead Compass, How it works and Pricing, checked October 25, 2026. Lead Seeker publishes these pages.
About the Author
Bob Generale is President of Percepture. He works across SEO, AI search, digital PR, sales intelligence and AI-powered revenue systems, with a focus on connecting visibility, buyer intent and sales action.
Next Steps
Take ten contacts your team is about to call and fill in a Field Stamp for each. Where a field has no source or date, replace it before anyone dials. Lead Seeker can supply named, verified people with the source attached; see how Lead Seeker works, or start free on your own ICP.