Virtual Private Networks (VPNs) are commonly used by businesses and individuals for privacy, security, and remote access. Because VPNs mask a visitor’s true connection information, they can impact Visual Visitor’s ability to identify website visitors.
Understanding this limitation helps set accurate expectations around visitor capture rates and data completeness.
In most cases, visitors browsing your website while connected to a VPN will not be identifiable within the platform.
Visual Visitor’s identification process relies on a combination of connection and behavioral signals, including IP address recognition and other matching data.
When a visitor is connected to a VPN:
Because of this, the visitor often appears as an anonymous or non-resolvable web session rather than an identifiable lead.
VPN traffic can create a gap between your total website traffic and your identified visitor count.
If a large percentage of your audience uses VPNs, identification rates may naturally appear lower than expected.
This is especially common with enterprise organizations, remote workforces, and privacy-conscious users.
Corporate VPN usage can reduce employee-level identification because many enterprise users browse behind shared company or secure network connections.
However, the +Employee platform uses additional organizational matching signals beyond simple IP recognition, which can sometimes still allow for company-level resolution.
VPN usage has a more significant impact on consumer-style identification.
Because consumer matching relies more heavily on household and device-associated signals, VPN masking typically prevents successful identity resolution.
No. There is currently no setting within Visual Visitor that can bypass or “see through” VPN masking.
Visitors using a VPN will generally remain unidentified unless they voluntarily provide identifying information through an action such as:
VPN usage is a normal internet behavior and is one of several external factors that can reduce total identifiable visitor volume.
This does not indicate a problem with script installation or platform functionality — it is simply a limitation of anonymous visitor identification across the web.