Person-level and company-level visitor identification are not the same product. They unlock different plays, feed different workflows, and produce different pipeline math. The right choice depends on what your team is actually trying to do with the data—not which match rate number sounds bigger in a vendor demo.

Here's the honest breakdown, including the math your sales team actually needs to make this call.

Two Types of Identification, Two Different Outputs

Company-level identification tells you which organization visited your website. You get the company name, domain, firmographics (size, industry, location), and pages viewed. It answers the question: "Acme Corp was on our pricing page yesterday."

Person-level identification goes a layer deeper. It tells you the specific individual—name, verified work email, job title, LinkedIn profile—within that company. It answers: "Sarah Chen, VP of Sales at Acme Corp, was on our pricing page yesterday."

Same signal source. Fundamentally different downstream action.

How Each Method Works (The Plumbing Matters)

Understanding the mechanics helps you evaluate vendor claims honestly and predict what you'll actually get.

Company-level identification works primarily through IP matching. When your visitor hits your site, their IP gets checked against databases of corporate IP ranges. If there's a match, you get a company record.

The structural limitation: IP matching only works well for people on corporate networks. Remote workers, VPN users, and anyone connecting from a residential ISP don't show up as their company. With over 60% of B2B knowledge workers now remote or hybrid, IP-only identification misses a substantial portion of your traffic—and that portion keeps growing.

Person-level identification adds an identity graph layer on top. Instead of relying solely on IP addresses, these tools match visitors against an identity graph — a cross-referenced network that links identity signals across publisher sites where users have previously been identified. That identity travels with them across sessions and devices, regardless of which network they're connecting from.

This is why person-level identification holds up better against remote work patterns. The match doesn't depend on an office IP; it depends on whether the visitor is in the identity graph.

The Match Rate Math: What You Can Realistically Expect

Vendors love to quote headline match rates without defining what they're measuring. The denominator matters as much as the number.

Knock2 measures identification rates against engaged sessions — visits that last 10 seconds or longer, or include two or more pageviews, as defined by Google Analytics. This is a more meaningful denominator than raw visitor counts: bots, accidental clicks, and immediate bounces inflate total traffic without representing real buying intent.

Against that benchmark, Knock2 resolves 93%* of engaged sessions to a company. For person-level identification — returning a named individual with verified work email, job title, and LinkedIn profile — that figure is 62%* on US traffic.

The gap between the two isn't a flaw — it's the cost of specificity. Not every engaged visitor has an individual record in the identity graph. But those who do are dramatically more actionable for outbound teams than either company-level records or form submissions. Most B2B sites convert 1–3% of traffic through forms; person-level identification at 62% of engaged sessions gives your SDRs an order of magnitude more identified contacts — people who are already engaged with your content and haven't raised their hand yet.

*Identification rates measured against engaged sessions. Results may vary by traffic profile, geography, and industry.

What Each Identification Type Unlocks

The real question isn't "which has a better match rate"—it's "which unlocks the workflow my team runs."

Company-level identification is a strong fit for:

• 🟢 ABM account prioritization — seeing which target accounts are in-market right now
• 🟢 Routing and alerting by company segment — enterprise vs. mid-market tiering
• 🟢 Demand gen audience building for paid channels — suppression lists, lookalike targeting
• 🟢 Account-level sales plays — alerting your AE when a named account goes active
• 🟡 SDR follow-up — possible, but requires a separate enrichment step to get to a contact
• 🔴 Direct contact outreach — no name or verified email in the output

Person-level identification is a strong fit for:

• 🔴 Broad coverage where depth isn't needed — company-level produces more volume here
• 🔴 EMEA audiences with strict GDPR requirements — needs careful evaluation before deploying
• 🟡 Account-level ABM — works well, though company-level alone is sufficient for most ABM plays
• 🟢 Trigger-based SDR outreach — name, verified work email, and pages viewed in one record
• 🟢 Buying committee detection — seeing multiple individuals from one account go active simultaneously
• 🟢 Speed-to-lead plays — no enrichment step between identification and sending the first email
• 🟢 Personalized first-touch at scale — you know who they are, what they looked at, and when

The core trade-off: company-level gives you more volume and is well-suited for marketing-side ABM plays. Person-level gives you fewer records but immediately outreach-ready ones—no manual lookup between "signal fired" and "contact created."

When Company-Level Is the Right Call

If your primary use case is account-based marketing—building suppression lists, creating in-market account segments for paid campaigns, or alerting AEs when a named account goes active—company-level identification is sufficient and often more appropriate.

It's also the smarter starting point if your monthly website traffic is under 5,000 visitors. At that volume, person-level identification may surface too few records to justify the cost difference, and company-level signals combined with a targeted enrichment step will serve just as well.

For teams with significant EMEA traffic, company-level identification generally fits more comfortably under GDPR's legitimate interest framework. Person-level identification of EU residents requires sourcing identity data from compliant, opt-in networks—which reputable tools do, but which you should verify explicitly before routing EU visitors through a person-level flow.

When You Need Person-Level

If your SDR team's job is trigger-based outbound—following up with people who just spent time on your pricing page, read three case studies, or hit your competitor comparison content—company-level identification creates friction that costs you the moment.

You identify Acme Corp. Now you need to find a contact at Acme Corp. Verify the email. Write a message that doesn't feel generic. Each step burns time. By the time your SDR reaches out, the prospect has moved on—or worse, talked to a competitor who moved faster.

Person-level identification collapses that chain. Your SDR has the name, the verified work email, the title, and the specific page they spent time on. A personalized first touch takes two minutes, not twenty. And it lands the same day the signal fires.

That speed matters. First-responder advantage in B2B outbound is real. A visitor who just spent 12 minutes on your pricing page is a fundamentally different conversation than a cold prospect—person-level identification lets you have it before the moment passes. For more on building the SDR workflow around these signals, see our BDR Playbook for Website Visitors.

Person-level identification is also the only path to buying committee detection: tracking when multiple individuals from the same account visit your site in a short window. That multi-stakeholder signal is one of the strongest pre-purchase indicators in B2B—and it's invisible if you're only resolving to the company level. Learn how to spot these patterns in our guide on detecting a buying committee forming on your website.

The Compliance Picture

Company-level identification is generally considered legitimate interest under GDPR and presents minimal privacy risk—you're identifying organizations, not individuals.

Person-level identification works from identity graph data that should be sourced from opt-in publisher networks, where individuals have consented to their data being used for business purposes. The best tools are transparent about their sourcing. When evaluating vendors, ask directly: "Where does your identity data come from, and how is EU visitor data handled?"

Your website should have a privacy policy disclosing your use of analytics and visitor identification tools. The accurate compliance framing is that tools match visitors against networks where identities were collected compliantly, not that they capture personal data independently.

For a broader look at how first-party intent signals fit into a compliant data strategy, see The 5% Rule: Why First-Party Intent Is the Most Valuable Signal in B2B.

The Decision Framework

Before choosing an identification tier, answer three questions:

1. What will my team actually do with this data? If the answer is "build account lists and inform ABM campaigns," company-level is sufficient. If the answer is "send personalized outbound sequences the same day the signal fires," you need person-level.

2. What's my monthly traffic volume? Under 5,000 visitors/month, prioritize identification quality over volume. Over 5,000 engaged sessions/month, person-level identification produces a meaningful number of outreach-ready contacts every month — especially at 62% of engaged sessions.

3. What's my outbound speed goal? If your team competes on speed-to-lead and same-day outreach on high-intent signals, person-level eliminates the enrichment step that slows everything down. If your outbound cadence is slower and more deliberate, company-level with enrichment can work.

Most mid-market and enterprise sales teams with a dedicated outbound motion—SDRs running sequences, AEs covering named accounts—will extract more pipeline value from person-level identification. Not because company-level is useless, but because it introduces a gap between "signal fired" and "outreach sent" that costs you the intent window. See how teams are turning anonymous traffic into pipeline with concrete plays that require both identification tiers.

How Knock2 Handles Identification

Knock2 identifies website visitors at the contact level—returning the individual's name, verified work email, LinkedIn profile, and job title alongside firmographic and behavioral data. The identity graph matches visitors using a consent-based publisher network rather than relying solely on IP matching, which means identification holds up against remote work and VPN traffic patterns better than purely IP-based tools.

Identified visitors flow directly into your CRM and SDR workflows as outreach-ready contacts—no manual enrichment step between signal and sequence. You can see which individuals visited, which pages they hit, and how engaged the account is overall, all in one place.

If you want to see what your traffic actually looks like at the contact level, start a free Knock2 trial.

Frequently Asked Questions

What's a realistic person-level match rate for my website?

It depends on the tool and, crucially, what denominator they use. Knock2 measures against engaged sessions — visits lasting 10 seconds or longer, or including two or more pageviews — and identifies 62%* of US engaged sessions at the person level. When evaluating other vendors, always ask whether their match rate is calculated against total sessions, unique visitors, or engaged sessions. The denominator matters as much as the number itself.

Is company-level identification enough for outbound SDR work?

Only if your SDRs are comfortable adding an enrichment step. Company-level identification tells you who's visiting, not which specific person to contact. SDRs who need same-day outreach will still need to identify a contact, verify an email, and personalize their message—all work that person-level identification eliminates. If your outbound motion is slower and more deliberate, company-level can work; if you're competing on speed-to-lead, you need person-level.

Can I use visitor identification data to contact EU visitors?

Company-level identification of EU organizations is generally fine under legitimate interest. Person-level identification of EU residents requires that the underlying identity data was collected with proper consent. Vet your vendor's data sourcing practices, configure geo-based consent flows where required, and disclose your use of visitor identification tools in your privacy policy. When uncertain, consult your legal team before routing EU visitors through person-level identification flows.

What's the difference between IP-based and identity graph identification?

IP-based identification matches your visitor's network address to a corporate IP database—it's fast and simple but fails for remote workers and VPN users, who now represent the majority of B2B knowledge workers. Identity graph identification cross-references identity signals across a publisher network to match individuals regardless of which network they're connecting from. Identity graph tools cost more but produce more actionable results in a remote-work world.

How do I know how much of my traffic fits my ICP before investing in visitor identification?

Benchmarking your existing traffic composition—by company size, industry, and seniority profile—is a smart step before committing to an identification budget. Our post on how much of your website traffic is your ICP walks through how to do this analysis before evaluating tools.