Anonymous visitor identification is the practice of resolving unidentified website traffic to the visiting company using IP reverse-lookup, first-party pixel data, and firmographic enrichment — without requiring the visitor to submit a form. At the company level it's GDPR-compliant under legitimate interest.
Most B2B website traffic never fills in a form. Anonymous visitor identification is the category of tools that resolve those sessions to a company name — turning silent traffic into pipeline signal.
## The Problem It Solves On a typical B2B site, 2-5% of visitors submit a form. The remaining 95% are anonymous. That's not because they're not interested — most are early-stage evaluators, competitors, or buying-committee members who don't want to be marketed to yet. Identifying which **companies** they're from gives sales an early warning system.
## How the Identification Works Modern tools combine three signals: 1. **IP reverse-lookup** against a business-IP database (WHOIS + ASN + BGP + private data) 2. **First-party pixel data** — page depth, referrer, session behavior 3. **Firmographic enrichment** — industry, employee count, tech stack, funding The output is a company name + confidence score. High confidence = corporate IP. Lower confidence = consumer ISP where a company could not be resolved.
## GDPR Position Company-level identification is not personal data. A company name, its industry, its HQ — none of these are PII. Under GDPR Article 6(1)(f), processing is permitted for legitimate interest with a documented balancing test. Person-level identification (name + email of the individual visiting) *is* personal data. In the EU/UK it requires explicit consent. Running it without consent creates real legal exposure. See [Compliance Center](/compliance).
## What a Good Tool Looks Like - **First-party pixel** — CNAMEd to your domain or served from a first-party CDN. Third-party pixels die under Safari ITP. - **Cookieless** — doesn't rely on persistent third-party cookies. Consent rejection shouldn't blind it. - **Live enrichment** — pulls firmographics + tech stack in real-time, not from a stale snapshot. - **Buying-stage detection** — surfaces Hot vs Early visits, not just a raw feed. - **CRM/Slack routing** — pushes signals into where sales work. - **De-duplication** — doesn't alert on known customers.
## Choosing Between Tools Most of the vendors in this category do roughly the same thing at the pixel layer. Real differentiation is in: - Match quality (IP dataset) - Buying-stage classification - CRM integrations - Registry cross-reference (which is where LemReveal is unique — 40+ national registries + DUNS + EDGAR) See side-by-sides: [Leadfeeder](/compare/leadfeeder-alternative), [Albacross](/compare/albacross-alternative), [RB2B](/compare/rb2b-alternative).
Company-level identification is generally permitted under GDPR Article 6(1)(f) — legitimate interest — because a company name isn't personal data. Person-level identification requires consent under GDPR. In the US, both are permitted with disclosure in your privacy policy.
LemReveal, Leadfeeder, Albacross, Warmly, RB2B, Clearbit Reveal, Snitcher, Lead Forensics, 6sense. RB2B focuses on person-level in the US; others are primarily company-level. See our comparisons under /compare/.
Consumer ISPs and mobile carriers don't map to businesses, so mobile + residential IPs return no company. VPNs also hide origin. Realistic rates: 40-60% on business-hour desktop B2B traffic, 10-15% on mixed traffic.
Yes — modern tools are cookieless. IP + browser fingerprint + first-party session heuristics don't require persistent cookies, so they work even when users reject cookie consent.