Can You See Who Visits Your Website? The Honest Answer

Yes and no, and the line between the two is precise. Yes: you can often see which company a visitor works for, because IP intelligence can match the network they browse from to a registered business. No: you cannot see the person’s name, email, or job title from a normal visit. Person-level identity only appears when the visitor gives it to you, through a form, a chat conversation, a signup, or a login.

Any tool that promises more than that for ordinary anonymous traffic deserves skepticism. The honest version of this category is company-level identification plus behavior, and that combination is genuinely useful for B2B teams. This article explains how it works, where it fails, and what to do with it.

Company-level identification is IP intelligence. Every visitor reaches your site from an IP address. Businesses often route traffic through IP ranges that are registered to them or attributable to their network. Identification tools compare the visitor’s IP against databases of these business network assignments and, when there is a match, report the company: name, domain, industry, size.

Note what is not happening here. There is no camera, no personal data broker lookup, no scraping of the visitor’s device. The signal is: this session came from a network associated with Acme Corp. Combined with behavior, that becomes: someone at a company matching your ideal customer profile viewed your pricing page twice this week.

Standard analytics does not do this. Google Analytics documentation describes storing a client ID in a first-party cookie to distinguish users and sessions; it reports behavior in aggregate and does not name companies or people. Visitor identification tools sit alongside analytics, not inside it.

You cannot see the individual. Not their name, not their email, not their photo, not which employee at the matched company was browsing. A company match on a 500-person business tells you the account, not the buyer.

Some US-focused vendors market "person-level" identification, which works by matching cookies or device signals against third-party identity graphs. That approach carries much heavier privacy weight, is largely restricted to US traffic, and still misses most visitors. It is a different product with a different risk profile, and it is not what most of this category, including PageFox, does.

IP-to-company matching has real failure modes, and any vendor who does not mention them is selling too hard.

• Residential internet: a visitor working from home resolves to their ISP, such as Comcast or BT, not their employer.
• Remote and hybrid work: the more distributed the workforce, the fewer visits arrive from identifiable office networks.
• Mobile networks: phone traffic resolves to the carrier, not a company.
• VPNs and privacy tools: traffic exits from the VPN provider’s network, masking the origin.
• Shared buildings and coworking spaces: one IP range can serve many companies.
• Stale databases: companies move offices and reassign ranges; matches can lag reality.

The practical consequence: some meaningful share of your B2B traffic will resolve to a named company, and the rest will not. Treat every match as account-level context with a confidence level, not as proof, and treat the identified slice as a sample of your traffic rather than a census.

If you research this topic, you will run into a claim repeated across vendor blogs: that 98% of website visitors leave without identifying themselves, sometimes phrased as "98% of your traffic is anonymous." It appears in different articles with different framings, and almost never with a citation.

We looked for the primary source and could not find one: no named study, no published methodology, no dataset. As far as we can tell, it is marketing folklore, a number that sounds plausible and has been copied between articles for years. We are not claiming the true figure is higher or lower; we are saying nobody appears to have measured it in a citable way.

The directional point behind the stat is real: most visitors do not fill out your form, and that is exactly why company-level identification exists. But if a vendor leads with a precise-sounding number and cannot tell you where it came from, apply the same skepticism to their accuracy claims.

The short version: company-level visitor identification is widely used, but it is not a regulation-free zone. The Court of Justice of the EU held in the Breyer case (C-582/14) that even dynamic IP addresses can be personal data when the operator has legal means to link them to an individual. So how a tool collects, stores, and discards IP data matters, and cookie or similar-technology rules can apply depending on the implementation.

This is a mechanics-and-questions topic, not a one-paragraph verdict. We cover the GDPR and ePrivacy considerations, and the questions worth asking your DPO, in the companion post on website visitor identification and GDPR.

Seeing that a company visited is only useful if it changes what you do next. A workable loop for a small B2B team looks like this:

1. Define your high-intent pages: pricing, comparisons, integrations, demo.
2. Turn on company-level identification and let it run for a couple of weeks to see your real match pattern.
3. Score visits by fit and behavior, so one pricing view from a target account outranks ten blog views from nowhere.
4. Alert on the strong signals only, into Slack or email, so nobody has to watch a dashboard.
5. Follow up on business relevance, never on surveillance. "Teams like yours usually hit this problem" works; "we saw you on our pricing page" does not.

And keep a path for visitors to identify themselves voluntarily. A chat widget that answers real questions converts curiosity into a conversation, which is still the only way to get from company to person honestly.

PageFox is built on the honest version of this answer. It identifies visitors at the company level through IP intelligence, scores leads using transparent signals you can inspect, and pairs that with an AI chat widget that answers questions grounded in your own content, with sources, so visitors have a reason to identify themselves.

• Company-level identification, with the limits stated rather than hidden.
• Lead scoring with transparent signals, not a black-box number.
• Passive mode: run identification with no visible widget if chat is not your thing.
• A single script install that takes about five minutes.

You will not get person-level names from PageFox without the visitor sharing them, because that is not how anonymous traffic works. What you get is the piece that is actually knowable: which companies are showing intent, and enough context to follow up well.