Why some website visitors can't be identified
No visitor identification tool can attribute every visit to a company, including this one. Some B2B website traffic arrives over connections that carry no reliable link to an employer. When that happens, IntentNexa records the behaviour, leaves the company unresolved, and tells you so — rather than filling the gap with a plausible-looking name.
Where identification breaks down
Home broadband connections
Remote and out-of-hours work arrives from residential ISPs. The connection belongs to a household, not an employer, so there is nothing to attribute the visit to.
Mobile networks
A visit over a mobile carrier tells you the carrier, which says nothing about where the person works.
VPNs, proxies and relays
Privacy tools deliberately break the link between visitor and network. Any company read from that connection would be the tool's, not the visitor's.
Hosting and data centre networks
Cloud-hosted connections, previews and automated traffic look like the hosting provider. A visit through an Amazon or Google data centre does not make Amazon or Google the visiting company.
Shared corporate infrastructure
Managed offices, group IT and shared gateways put several unrelated organisations behind the same network.
Privacy protections
Browser protections and declined analytics consent legitimately reduce what is recorded. Where a visitor has opted out, less is available and that is by design.
Not enough first-party signal
No campaign link, no company domain from a form, no prior confirmed observation. Without one of these there may simply be nothing that points to an account.
Unknown domains
A domain that is not on your known account list, and not otherwise evidenced, is not turned into a company record on its own.
The network owner is not the visiting company
This is the principle behind most of the cases above. The organisation that operates a network — an ISP, a mobile carrier, a cloud host, a VPN provider — is almost never the organisation the visitor works for. Reading one as the other is what produces lists full of data centres and telecoms companies that your sales team quietly learns to ignore. IntentNexa treats network information as supporting evidence only.
The confidence levels you will see
Every company in the product carries one of these, shown wherever the company appears.
Company not identified
The evidence does not support any company. The visit is still counted and its behaviour still visible — it simply has no account attached.
Possible match
Something points to an account, but weakly. Treat it as unconfirmed; it is labelled that way throughout the product.
Likely match
The evidence points consistently to one account without being strong enough to call it settled.
High confidence
Strong evidence, typically first-party: a confirmed association, a campaign link tied to a named account, or repeated consistent observations of an established account relationship.
Evidence can strengthen over time
An unresolved visit today is not necessarily permanent. Once a legitimate account relationship has been established, subsequent consistent observations can strengthen that relationship over time. Repeated anonymous traffic alone does not create an identity.
Weak evidence
An unknown residential network with no other signal. This does not identify a company.
Stronger evidence
A domain match against a company on your own known account list.
Strong first-party evidence
An account association your team has confirmed, or a visit arriving through a campaign link for that account.
Contradictions and matches that turn out to be wrong
Identification can be wrong, and pretending otherwise would be dishonest. When new evidence contradicts an earlier match, confidence is reduced rather than quietly overwritten. Anyone on your team can mark a company match as incorrect on the company page; that rejection is recorded and stops the same weak evidence naming that account again. Confirming a match works the other way round — it becomes first-party evidence that strengthens future recognition.