Person-Level vs Company-Level Visitor Identification: The Complete Breakdown (2026)

Company-level visitor identification tells you which business an anonymous website visitor works for; person-level visitor identification tells you who the visitor actually is — name, role, and LinkedIn profile. They rest on different technology, different geographies, different compliance frameworks, and different prices, and most vendor marketing does its best to blur which one you're buying. This guide draws the line precisely: how each works, what match rates are honest, where each is legal, and a decision framework for choosing — or, as most mature teams do, layering both.

The one-paragraph version

Company-level identification matches a visitor's IP address to a corporate network and returns firmographics: "Someone at Acme Corp (200 employees, SaaS, Boston) viewed your pricing page." It works globally and is the technology inside tools like Leadfeeder, Snitcher, Albacross, and Leadinfo. Person-level identification resolves the visitor against consented identity graphs and returns an individual: "Jane Doe, Head of Growth at Acme Corp, viewed your pricing page." It currently works reliably only on US traffic and is the technology inside VisiLead and RB2B. Company-level answers "which accounts are in-market?"; person-level answers "who exactly do we contact, today?"

How company-level identification works

1. Your site's tracking script captures the visitor's IP address.
2. The IP is matched against corporate IP registries, reverse-DNS records, and proprietary databases.
3. A match returns the company plus firmographic enrichment: size, industry, location, technology stack.
4. Behavioral data — pages, recency, frequency, colleagues visiting — accumulates on the account record.

Its known failure mode has grown every year since 2020: remote work. An employee on home Wi-Fi resolves to their internet provider, not their employer. Quality tools filter ISP and crawler traffic out rather than serving it up as leads; when a vendor advertises very high company match rates, ask what share of matches are ISPs before you're impressed. The full turn-anonymous-traffic-into-pipeline workflow is covered in our website visitor tracking guide.

How person-level identification works

1. The visitor's device and browser signals are checked against an identity graph — a network of publisher and partner sites where that person has, at some point, consensually identified themselves (a newsletter signup, an account login).
2. A graph hit resolves the visitor to an individual profile: name, title, company, LinkedIn URL, and often a business email.
3. Identity persists across sessions, so the person's journey assembles over time rather than fragmenting per visit.

Three structural facts every buyer should know before comparing vendors:

• It's US-only in practice. Identity graphs with meaningful coverage exist for US traffic. Vendors don't offer person-level identification on EU visitors — both because the graph coverage isn't there and because GDPR makes it untenable (Snitcher, a company-level vendor, states plainly that person-level ID would conflict with EU data-protection law — for EU traffic, they're right).
• Honest match rates are 8-15% of US traffic. Independent benchmarks for the person-level category cluster in that range. That's not a flaw to hide — on 3,000 monthly US visitors it means 240-450 named, in-market individuals a month who were invisible before. But any vendor implying majority-of-traffic person matching is selling against physics.
• Coverage skews professional. Graphs are built from B2B publisher ecosystems, so the person-level layer resolves exactly the audience B2B sellers want — working professionals on business-adjacent browsing — and largely misses everyone else.

The comparison, precisely

Which one do you need?

• Sales-led motion, meaningful US traffic → person-level, layered on company-level. Named individuals with observed intent are outreach-ready in a way account names never are; the company layer still catches the 85%+ of visits the graph can't resolve.
• EU-majority traffic → company-level, full stop. Person-level identification isn't available for EU visitors, and a vendor suggesting otherwise is a red flag. Choose EU-strong databases (Leadfeeder's is EU-built) and invest the savings in first-party capture.
• ABM and attribution use cases → company-level is the workhorse. Account journeys, ICP filtering, and revenue attribution all key on the account; person-level enriches but isn't required.
• Agencies reporting to clients → company-level. Client-facing reporting wants account intelligence; individual tracking raises questions agencies don't need.

The layering pattern is why the distinction increasingly lives inside single products rather than between them: VisiLead runs person-level identification on US traffic and company-level identification globally in one tracker from $29/mo, which is also the honest way to read every "identify your visitors" pitch — ask *at which level, on which geography, at what match rate*. Those three questions sort the market in about five minutes. For the tool-by-tool landscape, see our visitor identification software comparison.

Compliance, briefly and precisely

Company-level identification processes corporate network data. Under GDPR it operates on legitimate-interest grounds with proper disclosure — the data subject is effectively a business. Person-level identification processes personal data and exists inside the US framework: consented identity graphs, CCPA/CPRA disclosure and opt-out obligations, and deliberate exclusion of EU traffic. The bright line for buyers: person-level identification of EU visitors should not be on any vendor's menu, and its absence is evidence of a vendor you can trust. Implementation details live in our GDPR-compliant visitor identification guide.

Frequently Asked Questions

Q: What is the difference between person-level and company-level visitor identification?

A: Company-level identification matches a visitor's IP address to a business and returns the company name plus firmographics; it works globally. Person-level identification resolves the visitor against consented identity graphs and returns the actual individual — name, role, LinkedIn profile, often a business email; it currently works only on US traffic, at honest match rates of 8-15% of visitors.

Q: What match rate should I expect from person-level visitor identification?

A: Independent benchmarks cluster around 8-15% of US traffic. On 3,000 monthly US visitors that's 240-450 named individuals with observed buying behavior. Treat claims dramatically above that range skeptically, and note the denominator: non-US traffic resolves at approximately zero at the person level, so a site's overall rate depends heavily on its US share.

Q: Is person-level visitor identification legal?

A: On US traffic, yes — it's built on identity graphs where individuals consensually identified themselves, operating under CCPA/CPRA with disclosure and opt-out obligations. On EU traffic it is not offered by credible vendors; GDPR's consent requirements make it untenable, which is why person-level tools scope to US visitors and fall back to company-level identification elsewhere.

Q: Can I get both person-level and company-level identification in one tool?

A: Yes — that's increasingly the standard architecture. VisiLead includes both from $29/mo: individual identification on US traffic and company identification globally, with intent scoring across both layers. RB2B offers person-level from $79/mo with company-level resolutions on its free tier. Layering both maximizes coverage: the person layer names who it can, the company layer catches the rest.

Q: Which is more accurate, person-level or company-level identification?

A: They fail differently, so "accuracy" needs splitting: company-level covers more traffic but its matches carry ambiguity (which of 200 employees was it? was that home-office visitor filtered correctly?). Person-level matches a smaller share (8-15% of US traffic) but each match is precise — a specific individual with a verifiable profile. For outreach, person-level precision wins; for account intelligence and attribution coverage, company-level breadth wins. That asymmetry is the entire argument for running both layers.

Q: Why is person-level identification US-only?

A: Two stacked reasons: coverage and law. The identity graphs that make resolution possible were built on US publisher ecosystems, so their density elsewhere is too thin to be useful. And EU privacy law (GDPR's consent requirements) makes the model untenable for European visitors regardless of graph coverage — which is why credible vendors scope person-level identification to US traffic and treat any claim of "person-level ID on EU visitors" as a red flag rather than a feature.

Q: What data do person-level identification tools actually return?

A: A typical match includes full name, job title, company, LinkedIn profile URL, and — depending on tool and plan tier — a business email; some add location and company firmographics. What they do not return matters equally: no browsing history from other sites, no personal (non-work) contact details, and no data on visitors who never appear in the consented graph. The output is a professional identity snapshot attached to the visit, not a surveillance dossier.