LayerSift
Log inStart free

Playground

Everything below is computed from this browser, right now, by the same agent and API that customers integrate. Change something about your environment and hit re-identify.

Your visitor ID
—

Nothing is read from this browser until you press Identify. Then our agent reads it as it would on a customer's page, and the result is kept in our demonstration organization for a week.

Match confidence

—

Waiting for identification

Suspect score

—

Bot

Clear

…

Incognito

Clear

…

VPN

Clear

…

Proxy

Clear

…

Tampering

Clear

…

Virtual machine

Clear

…

DevTools

Clear

…

Remote control

Clear

…

Privacy mode

Clear

…

Request context
Browser—
Operating system—
IP addresslocal
LocationPrivate network
Event ID—
Risk band—

Accuracy improves with production traffic volume — this demo organization has a small identity graph.

Try breaking it
Each of these changes something a naive fingerprint would fail on.

  • Open an incognito window

    The visitor ID stays the same. The incognito signal flips to detected.

  • Clear cookies and site data

    Nothing changes — identification never reads or writes storage.

  • Turn on a VPN

    The IP and geolocation move; the VPN signal fires on the timezone mismatch.

  • Open developer tools

    Re-identify and the developer-tools signal picks up the open inspector.

  • Run it under Playwright

    The bot signal reports `bad` with the automation markers that triggered it.

  • Resize the window, switch monitors

    Fuzzy matching absorbs the drift and keeps the same visitor ID at lower confidence.

Verify it server-side
The browser payload is convenience; this is the source of truth.
# Copy the event ID from the raw response above, then verify it
# with a secret key from your own organization.
curl "$ORIGIN/api/v4/events/$EVENT_ID" \
  -H "Authorization: Bearer $ANTIBOT_SECRET_KEY"
Full API reference
How the visitor ID is built
Each entropy source contributes a weighted vote. A device matches an existing visitor when the weighted similarity clears 82%, which is what lets identity survive a GPU driver update or a new monitor.
canvas
12
fonts
10
webgl
10
webglRender
8
audio
8
screenResolution
8
fontMetrics
6
hardware
6
platform
6
cssFeatures
5
codecs
4
mathProfile
4
speechVoices
4
engineGlobals
3
errorSignature
3
intlProfile
3
languages
3
plugins
3
userAgentData
3
storageApis
2
webgl2
2
applePay
1
privacySignals
1

Volatile sources — user agent version, timezone, storage usage, battery and permission grants — are collected for signal analysis but excluded from identity, because they change without the device changing.