To identify B2B website visitors, install a first-party JavaScript pixel that captures the visitor's IP + browser fingerprint, then reverse-lookup the IP against a business-IP database. Modern tools resolve 30–60% of B2B traffic to a company name without requiring the visitor to fill in a form.
Every B2B marketer eventually asks: *of the thousand people who hit my pricing page this month, who were they?* Visitor identification tools turn anonymous traffic into named accounts. Here's how they actually work — and where they fail.
## The Three Signals That Identify a B2B Visitor 1. **IP address + reverse lookup** — every corporate network has one or more public IPs. Match the IP against a business-IP database (WHOIS + ASN + BGP + private data) to resolve to a company. 2. **First-party JavaScript pixel** — served from your domain, survives Safari ITP and ad-blockers. 3. **Behavioral fingerprint** — pages visited, referrer, device, browser, session duration. Used for deduplication and scoring.
## Why IP Alone Isn't Enough A large chunk of internet traffic comes from consumer ISPs (Comcast, Sky, Deutsche Telekom, Free) that don't map to businesses. Mobile carriers are worse. So the raw IP-to-company match rate on total traffic is often 10-15%. On **business-hour desktop B2B traffic**, that jumps to 40-60%.
## The Cookieless Advantage Safari's Intelligent Tracking Prevention caps third-party cookies at 7 days. Firefox Total Cookie Protection blocks them entirely. Cookie-based visitor identification silently loses 30-50% of Safari/Firefox traffic. First-party + IP-based identification is unaffected.
## What Modern Identification Tools Do - Serve the pixel from your domain or a first-party CDN - Cross-reference IP against a live business-IP dataset - Enrich with firmographics (industry, size, revenue, tech stack) - Detect the buying stage from behavior (Hot / Warm / Building / Early) - Deduplicate against known customers so sales aren't spammed
## GDPR + Compliance Reality **Company-level identification** — resolving an IP to 'Acme Corp' — is not personal data under GDPR. It falls under legitimate interest (Article 6(1)(f)) as long as you document the balancing test and honor opt-outs. **Individual-level identification** — resolving a session to 'Jane Smith' — *is* personal data. In the EU/UK it requires explicit consent, and running it without consent creates legal exposure. Our approach is company-only in the EU by default. See [Compliance Center](/compliance).
In the EU/UK, only with explicit consent — that's PII under GDPR. In the US, some tools (like RB2B) do surface individual identities, but the compliance risk is significant. B2B visitor identification tools resolve to the company level, which is not PII, and is generally permitted under GDPR Article 6(1)(f) legitimate-interest.
For B2B traffic on business hours, 30-60% is normal. Consumer/mobile traffic is closer to 10-20% because most residential ISPs don't map to businesses. Publish or long-tail content skews lower.
Yes — company-level identification is generally allowed under legitimate interest (GDPR Article 6(1)(f)) because company data isn't personal data. See our [Compliance Center](/compliance) for the full legal analysis.
The best tools are. IP + browser fingerprint + session heuristics don't require persistent cookies. Cookie-based tools break under Safari ITP and consent rejection.
LemReveal ships a first-party pixel, cookieless identification, and 40+ national registry cross-reference in one workspace. See detailed comparisons: [Leadfeeder alternative](/compare/leadfeeder-alternative), [RB2B alternative](/compare/rb2b-alternative).