Live demo
A real session against production infrastructure — originId resolution, smart signals, and suspect scoring you can inspect live. This demo uses the same visitor identification path as production: browser signals are collected in-page, then matched server-side so returning browsers keep a stable ID even when cookies are cleared or private mode is used. Reload the page, open an incognito window, or toggle a VPN to see how confidence and smart signals respond — and the payloads your backend receives.
Running identify
collectSignals() → POST https://dashboard.digitalfingerprintjs.com/api/demo/identify
How the demo works
The page collects browser and device signals, sends them to the hosted identify API, and displays the returned visitor profile. The stable originId helps connect repeat visits. The response also explains confidence and the smart signals available for evaluating automation, network changes, and suspicious behavior.
Re-identify or reload the page and compare the visitor ID with the previous result. You can also repeat the test after clearing site data to see how the service resolves a returning browser when a storage-only identifier is unavailable.
Review confidence, suspect score, and individual smart signals together. A VPN, proxy, or private window is context for a decision rather than proof of abuse. Your backend can combine these fields with account and transaction history.
Production integrations keep API credentials and authoritative fraud data on the server. The browser receives a slim identify response, while your backend uses the event ID to retrieve enrichment before approving a signup, payment, or other sensitive action.
