Connecting

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.

Your unique visitor ID dataReading…
Your browser’s visitor ID

Collecting device signals…

Last seen
Visit history
Confidence
Browser
IP address
Operating system
Visits that kept this ID
First seen
Browsers on this device
What your backend decidesThresholds: 25 and 60

Checking

0/ 100Low risk

Checking 26 signals…

Why this score

  • Waiting for the first identification
This is a real demo on a test server. Production data will look different.

What just happened

  1. Step 01 Identify

    Waiting–

    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 SDK
  2. Step 02 Verify

    Waiting–

    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 SDK
  3. Step 03 Device graph

    Waiting–

    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.

0 of 8
  1. Next

    Come back

    Reload the page. The visitor ID stays the same.

  2. Not yet

    Clear storage, stay recognised

    Press "Forget this browser". The ID survives on device signals alone.

  3. Not yet

    Open a private window

    Same browser, private mode: same ID, and the private window is detected.

  4. Not yet

    Open another browser

    Chrome, Edge or Firefox on this computer. They share one device ID.

  5. Not yet

    Sign in as three accounts

    Type three different names above, identifying each time.

  6. Not yet

    Fake your device

    DevTools device emulation, or a user-agent switcher extension.

  7. Not yet

    Turn on a VPN

    Exit in another country. Needs a GeoIP database on the server.

  8. Not yet

    Visit with automation

    Open this page from Playwright, Puppeteer or Selenium.

This browser over time

0 visits kept in this browser

Each visit lands here.