Person-Level vs Company-Level Visitor Identification

Company-level identification tells you which organisation a visit came from; person-level identification tries to name the individual. Company-level data covers more countries and carries less privacy risk, while person-level data is more actionable but narrower, mostly US-only and lower in match rate.

Where we quote figures, they come from BusinessMCP’s published pages, such as its RB2B comparison and its guide to how visitor identification works. BusinessMCP sells a company-level product, so weigh that perspective accordingly.

How each method works

Company level. A visit arrives from an IP address. Network registry data and enrichment sources indicate whether that address belongs to a business, an internet provider, a mobile carrier, a cloud host or a VPN. If it is a business, you get its name and perhaps domain. Home and mobile connections generally return nothing useful, which is why the share resolved is modest.

Person level. Vendors combine signals such as hashed emails and identity-graph data to guess which individual is browsing. The comparison says RB2B’s version covers only US traffic and resolves about 5 to 20 percent of it.

The trade-offs

Factor	Company level	Person level
Typical output	Company name, domain, network type	Name, email, LinkedIn URL
Geography	Global	Mostly US
Share of traffic resolved	Roughly 20-35% of B2B traffic (BusinessMCP)	About 5-20% of US traffic (per comparison)
Privacy exposure	Lower	Higher
Best for	Account-based selling, enterprise prospects	Founder-led or SMB selling in the US
Typical mistake	Treating an ISP as a customer	Treating a guess as a fact

The resolved-share figures are vendor claims, not independent measurements. They also describe different denominators: B2B traffic overall versus US traffic. They should not be compared as if one is “better”.

Key takeaway: an identification is a hypothesis about an account or a person. Confirm it with behaviour, a form fill or a human check before you act on it.

Which fits your sales motion

If you sell to organisations where several people evaluate a purchase, the company is the unit that matters. A visit from “a visitor at Acme” is useful whether it was the CFO or an analyst. If you sell to individuals, such as freelancers, solo founders or executives who decide alone, a person-level hint can speed up outreach, but it also demands more care.

Mixed approach: BusinessMCP identifies companies natively and says person-level reveal for US traffic is available by connecting your own RB2B or Leadpipe API key, which lets a team keep one dashboard while adding individual detail where the law and data allow it. See its visitor identification page for how that is described.

Accuracy: what to believe

Be sceptical of any quoted match rate that does not state a traffic mix. A site whose visitors are enterprise staff on office networks will resolve far more than one aimed at consumers or remote workers. Remote work, VPNs and mobile data push many professionals onto networks that name no employer. For a deeper treatment, read our note on RB2B match rates and the practical guide to testing a tool on your own traffic.

Privacy and legal considerations

Company-level processing is lower risk because it concerns organisations rather than people, though IP addresses can still count as personal data in some contexts, and sole traders blur the line. Person-level matching depends on identity-graph data and raises harder questions about transparency and consent, particularly for visitors from Europe. We summarise the main regimes in website visitor tracking laws and the GDPR angle in our GDPR alternative guide. None of this is legal advice.

Common mistakes

1. Emailing a company address pulled from an ISP match. Check the verdict, not just the name.
2. Counting identified companies as leads. Many are competitors, vendors or job seekers.
3. Skipping the ICP filter. Rank by fit before you rank by activity.
4. Ignoring geography. Person-level data on non-US visitors is typically absent.
5. Forgetting the follow-up. Data without an owner decays.

A decision rule of thumb

Choose company-level first if your audience is global, your buyers are organisations or you want the simplest privacy story. Add person-level only for US-heavy segments where an individual profile changes what you do next. Then check the economics with the worked example in RB2B pricing. If you want to see company resolution on a single address before choosing a vendor, BusinessMCP offers a free company lookup tool.

Three short cases

Case one: a B2B analytics vendor. The buying group includes an analyst, a manager and a finance approver. The first visitor from a target account might be any of them. A company-level signal such as “three visits from Acme this week, two to pricing” is more useful than a single named analyst, because it tells the sales team to approach the account through its likely sponsor. Person-level detail would add little.

Case two: a solo-founder coaching business. The visitor is the buyer. If a US-based founder visits the booking page twice, a LinkedIn profile lets the coach send a personal, relevant note. Company-level data would return nothing useful, because the visitor probably works at a one-person firm or uses a home network.

Case three: a global SaaS with a free trial. Most sign-ups provide an email address anyway. Identification matters mainly for visitors who do not sign up. Company-level data helps segment these by size and industry, which feeds nurture campaigns and ad audiences without profiling individuals.

Data you should not expect from either

No identification method can tell you a visitor’s intent, budget or authority. It can show which pages they read and how often, and your team infers the rest. Neither method reliably identifies people on mobile data, shared offices without a named network, or privacy-focused browsers. And neither can substitute for asking: a short form or chat prompt gives you accurate information the visitor chose to share.

Governance for either approach

Whichever level you choose, set simple internal rules. Decide which fields your team may store and for how long. Decide who can view identified records. Decide how you will respond if a visitor asks what you hold on them. Document your lawful basis for processing and update your privacy notice to match. Keep a list of vendors that touch the data, with their DPAs. These steps cost little and make later vendor changes easier, such as the move described in how to switch from RB2B.

If you run outreach on top of identification, remember that the rules for contacting a person differ from the rules for recognising a company. Our tracking law summary explains why those two questions need separate answers, and why a country-by-country approach is safer than a single global policy.