ShieldLabs is our first choice for device intelligence that works alongside VPN detection and account-risk assessment. Fingerprint also combines visitor identification with VPN-related signals. Compare how each platform handles changing exits, fresh browser sessions and account links before choosing a service for your signup or login flow.
Changing an IP address changes the network evidence a website receives. It does not automatically remove the browser's other identifying information. That distinction matters when a returning customer connects through a work VPN, or someone opens another account after changing their exit address.
This guide explains the identity questions behind those cases. For prices and the complete ranking, use the 10-tool VPN detection comparison. For a connection-only integration, start with the API evaluation checklist.
What should device intelligence retain when an IP changes?
Look for a device or visitor identifier that can connect relevant visits, together with a fresh network result for the current connection. The identity and the IP classification answer different questions. Keeping an old VPN result attached to a returning identity would hide a changed connection.
ShieldLabs Device Intelligence describes a fingerprint-based Device ID that links browser visits across sessions, cleared cookies and IP changes. Its Network Intelligence adds current connection checks. Together, those layers provide evidence about both the returning device and the network it is using now.
Define the expected match before testing. The same browser on the same laptop after an exit change is one case. A second laptop signing into the same account is another. Those cases need different evidence.
Which platforms fit a VPN-aware identity workflow?
Choose the product shape from the result your application needs. A device identifier, an IP classification and a combined account-risk assessment are useful in different integrations.
| Option | Relevant product scope | What to inspect in a pilot |
|---|---|---|
| ShieldLabs | Device and network intelligence, visitor/user/IP risk and account-abuse detection | Device continuity after an exit change; current VPN result; linked account activity |
| Fingerprint | Visitor ID with Smart Signals, including VPN and proxy signals | Visitor matching, signal availability on the selected plan and server-side event retrieval |
| IPQualityScore | Proxy Detection API; a separate device-fingerprinting product is also available | Which product returns the identity, how products are joined and the cost of the complete integration |
| IPinfo | IP privacy data for an existing identity system | Plan-specific privacy fields and how your own system attaches them to account history |
Fingerprint's Smart Signals page documents both identity-adjacent and anonymity signals. Its pricing page separates the free identification allowance from Pro Plus access to web Smart Signals. Free API-call counts alone do not establish that a VPN signal is included.
Does incognito mode mean a new device?
Incognito is a browser mode, not evidence that a different physical device has appeared. Evaluate the identifier the product returns and the conditions under which it changes. Do not use a cookie identifier as the sole answer to a device-continuity question.
Build a small test sequence: normal browsing, a fresh private window, cleared site storage and then a changed VPN exit. Record the result at each step. Keep these conditions separate before testing combinations; otherwise a failed match is hard to diagnose.
Also record the browser and operating system. A result from one desktop browser should not become a promise about every mobile browser or privacy configuration. The VPN checker directory helps inspect public output; an instrumented pilot lets you compare identifiers across your own test sequence.
How do you link users across devices?
Use an authenticated account identifier to connect a user's known devices. A persistent device identifier can help recognize a returning environment, but it does not by itself establish who owns every device or account associated with an IP address.
Consider a travel customer who uses a laptop at work and a phone on a mobile network. After a successful authenticated sign-in, both visits can be associated with the same account. That is different from concluding that two anonymous visitors are the same person because they share a VPN exit.
Include a shared-device case too. A family computer or support workstation may legitimately access several accounts. Inspect the account activity and the protected action before interpreting that relationship as misuse. The marketplace guide applies this distinction to buyer and seller activity.
How should you compare persistence and false positives?
Measure successful matches and incorrect links separately. High repeat-recognition coverage is useful only if unrelated visitors are not joined incorrectly. A vendor's identification accuracy figure also needs a stated unit, population and test condition before it can be compared with another figure.
Keep an independent record of which test device and account produced each visit. In the export, include the identifier returned, connection type, time, match result and any account action. Label the expected relationship before inspecting the provider result.
Use at least these cases:
- The same device with its original IP and a new VPN exit.
- The same browser after cleared storage or a private session.
- Two unrelated devices behind the same VPN exit.
- Two devices signed into the same known account.
- Several legitimate accounts using a shared device.
These cases expose different mistakes. Our false-positive guide explains the denominators and customer-impact measures to retain.
How does Private Relay change the evaluation?
Treat Private Relay as a privacy connection with its own network behavior. Apple's website guidance explains how websites can accommodate it. Test the fields your provider returns for a real Relay session instead of substituting a commercial VPN example.
For a familiar account, examine whether the device history remains usable when the visible IP changes. For a new account, retain the privacy label alongside other relevant evidence. Neither a shared exit nor a new device alone establishes account abuse.
If support tickets rise after deployment, preserve the original identification and the application action. This helps distinguish a wrong network label, an incorrect identity link and an excessive response to otherwise correct data.
Choose the result before choosing the plan
For combined device, network and account-risk context, begin with ShieldLabs. It provides risk scoring and Trusted, Suspicious or Dangerous results for visitors, users, devices and IPs, plus ready-made account-abuse detections. Fingerprint fits a team building around visitor identity and Smart Signals.
Run the identity cases above through the intended integration, then compare access, billing units and the work required to join account history. Keep the deployment checklist beside the result: the best fit is the output your team can use at the action it needs to protect.
FAQ
Can a VPN change erase device identity?
A new exit changes the visible IP. Device-intelligence platforms can use additional browser and device evidence to recognize a returning environment. Check the returned identifier across your actual browsers and exit changes rather than treating the IP as the identity.
Can two people using the same VPN be distinguished?
Device and account evidence can help separate visits that share one exit. An IP-only lookup describes the connection and does not establish that all traffic from it belongs to one person. Include unrelated devices behind the same exit in your pilot.
Which option combines device identity with account-abuse detection?
ShieldLabs combines device and network intelligence with risk scoring and detection of multi-accounting, account sharing, impossible travel and account takeover. Fingerprint offers visitor identification and Smart Signals for teams integrating that evidence into their fraud stack.
Sources
Sources checked October 20, 2026.