> For the complete documentation index, see [llms.txt](https://docs.hockeystack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hockeystack.com/technical-details/tracking/identifying-users/enhanced-fingerprinting.md). # Enhanced Fingerprinting Enhanced Fingerprint add-on for advanced VPN and cross-device visitor tracking. While our default cookieless tracking already handles most VPN scenarios, some teams need even more advanced capabilities. \ \ For organizations looking to maintain visitor identity across devices, browsers, domains, and network changes - including the most persistent VPN masking - HockeyStack offers an Enhanced Fingerprint option. \ \ This premium add-on, powered by [Fingerprint.com](http://fingerprint.com/), goes beyond standard fingerprinting by using a proprietary identification model designed to handle challenging cases like: * Visitors who regularly switch between work and personal devices * Browsers running in strict privacy modes * High-frequency VPN and proxy users * Mobile-to-desktop session transitions * Support for Customers with Multiple Domains When enabled, Enhanced Fingerprint works seamlessly alongside HockeyStack’s core tracking. No extra scripts or changes to your snippet are required - just enable it with your HockeyStack representative or Customer Success Manager, and the system begins applying the enhanced model to your existing visitor data.\ \ The result is a higher match rate for unique visitors, more accurate deduplication, and improved continuity in your analytics - without compromising on privacy or compliance. \ \ As with our standard fingerprinting, Enhanced Fingerprint never stores IP addresses or PII, and all identifiers are securely hashed before processing. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.hockeystack.com/technical-details/tracking/identifying-users/enhanced-fingerprinting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.