Most of your B2B website visitors leave without filling out a form. Website visitor identification tells you which companies were on the page — not which people — so your sales team can pick up the conversation before the lead goes cold. This guide covers what the category actually is, how it works technically, what to expect on identification rates, and how to make the recognised companies useful in a real pipeline.
What is website visitor identification?
Website visitor identification is the practice of resolving anonymous B2B website traffic to the organisation behind it — the company name, industry, size and country — so that a sales team can act on the interest a prospective buyer has already shown. It works at the company level, not the individual level: no personal identifiers are used, no cross-site profile is built, and no cookie is required for the resolution itself.
In short: a visitor from ACME GmbH lands on your pricing page. Visitor identification turns that unknown session into the line 'Someone from ACME GmbH looked at pricing today' inside your sales tool. Whether ACME is a fit — and who at ACME to reach out to — is your team's call. The tool's job is to remove the anonymity of the company.
How does website visitor identification work?
Three things happen behind the scenes. A small script on your site captures each pageview with technical metadata (timestamp, URL, referrer, user-agent). The visitor's IP address is passed to a resolver that maps IP ranges to organisations using verified corporate network data. The result — company name, country, industry, size — is written to your workspace next to the page journey. No user-level cookies are set for the resolution itself.
The critical step is the IP-to-company mapping. It works because most B2B traffic still comes from corporate offices, VPNs, or company-managed devices whose IP ranges are registered to a legal entity in public network registries. Home connections, mobile networks and consumer VPNs generally cannot be resolved to a company — and honest tools tell you so instead of guessing.
What identification rates should you honestly expect?
Anyone promising 100% identification is selling something else. Realistic ranges depend on your traffic mix, industry and geography. Here is what a healthy B2B site typically sees.
| Traffic segment | Realistic identified share | Why |
|---|---|---|
| Direct + brand search | 25–45% | Buyers often visit from the office |
| Paid B2B campaigns | 20–35% | Targeted to work contexts |
| Organic long-tail | 10–20% | Mixed research vs. buying intent |
| Social referral | 5–15% | Frequently mobile / personal networks |
| Consumer traffic | < 3% | ISPs cannot be resolved to a company |
The point of the number is not to hit a leaderboard. It is to answer one question: is there enough recognised traffic in the segments you care about (pricing page, product tour, contact form abandoners) to change how sales spends its Monday morning?
What can you actually do with recognised companies?
The point of identification is not the list of company names — it is what you do with it. The four use cases below deliver almost all of the pipeline lift teams see in their first quarter.
- Warm outbound: an SDR reaches out to companies that visited pricing or the product tour in the last 48 hours, referencing the page they read.
- Alerts on target-account activity: your named-account list gets a real-time notification when one of them shows up on the site.
- ABM feedback loop: marketing sees which target accounts a campaign actually pulled onto the site, not just impressions.
- Anonymous-form-abandoner rescue: someone from ACME started a demo request and dropped off — the AE has enough context to send a useful follow-up.
Where teams get their first win
Start with the pricing-page cohort. Filter for identified companies who saw /pricing more than once in the last 14 days. That is usually the highest-signal, lowest-volume list — perfect for a 20-touch outbound sprint that pays for the tool in the first month.
Getting started — the 30-minute setup
A working setup takes about half an hour, not a project plan. The steps below assume you already know your ideal customer profile and have a place for sales to receive alerts (Slack, HubSpot, Salesforce, an email inbox).
- Install the tracking script on all pages (or a single site tag if you use one). Verify it fires on your key pages.
- Add the standard privacy-policy snippet to your site to inform visitors about company-level identification and their right to object.
- Define one primary target-account list (top 200 named accounts) and one intent segment (pricing + product tour in the last 14 days).
- Wire alerts for those two segments into your CRM or Slack channel used by sales.
- Review the identified visits at the end of week one; delete filters that produce noise, keep those that produce useful conversations.
Everything after step five is optimisation, not setup. Teams that treat identification as an operational habit — checked daily, filtered ruthlessly, reviewed weekly — see compounding returns; teams that treat it as a dashboard rarely do.
Common questions
Two questions come up in every buying conversation. First: is this GDPR-compliant? Yes, when done at the company level under Art. 6(1)(f) legitimate interest, with a transparent privacy notice and an opt-out — the details are in our GDPR guide. Second: what happens if we cannot identify the company? The visit stays in your workspace as an unidentified pageview so aggregate analytics still work; the identification simply is not attached.
If you are evaluating vendors in this category, our Dealfront alternative overview covers the GDPR-first setup we recommend and where the trade-offs sit.
Published by
lead.box Team
More articles
See lead.box on your own traffic
Start free — no card, no sales call required. Or book a 20-minute walk-through if you want the guided tour.