See Trace in action
Trace is reading your browser right now: a visitor ID, every fraud signal with its reason, and the device graph.
Everything below is the real response from a test server, not a mock-up. What the demo stores.
Collecting device signals…
Checking
Checking 26 signals…
Why this score
- Waiting for the first identification
What just happened
Step 01 Identify
The browser SDK reads device traits and asks the Trace server who this is. The browser never makes the decision.
Browser SDK → Trace server
Browser SDKStep 02 Verify
Your backend sends the event ID with its secret key and gets the trusted result back. Only a verified event should drive a decision.
Your backend, with the secret key
Node SDKStep 03 Device graph
Trace looks up the other browsers and the accounts it has seen on the same device, and returns them as a graph.
Browsers and accounts on this device
API reference
Challenges
Try to fool it
Each of these is how fraudsters try to look like a new person. Do one, press R, and watch the ID hold.
- Next
Come back
Reload the page. The visitor ID stays the same.
- Not yet
Clear storage, stay recognised
Press "Forget this browser". The ID survives on device signals alone.
- Not yet
Open a private window
Same browser, private mode: same ID, and the private window is detected.
- Not yet
Open another browser
Chrome, Edge or Firefox on this computer. They share one device ID.
- Not yet
Sign in as three accounts
Type three different names above, identifying each time.
- Not yet
Fake your device
DevTools device emulation, or a user-agent switcher extension.
- Not yet
Turn on a VPN
Exit in another country. Needs a GeoIP database on the server.
- Not yet
Visit with automation
Open this page from Playwright, Puppeteer or Selenium.
Each visit lands here.