Know the device before the password.

Compare each login with the devices an account normally uses. Step up only when something is off, and leave known devices alone.

Signalsvelocityvpnbot
scenario
Step 4 of 4bot and velocityBlock
Figure 1Logins to one account. Illustrative data. Hover or focus to pause; pick a step to scrub.

How it plays out

The attack, what the verified event shows, and what your code does about it.

01 · The attack

How it usually goes

  1. Credential stuffingLeaked passwords tried at scale from scripts.
  2. Stolen sessionsA valid login from a device the user never had.
  3. Proxy rotationEvery attempt from a new IP to dodge rate limits.
02 · What Trace sees

Fields on the verified event

  • velocityMany accounts or IPs per visitor in a short window.
    "velocity": {  "detected": true,  "details": { "exceeded": ["linkedIdsPerVisitor24h"] }}
  • vpnTimezone that does not fit the IP country.
    "vpn": {  "detected": true,  "details": { "methods": ["timezoneMismatch"] }}
  • botAutomation frameworks driving the login form.
    "bot": { "detected": true }
03 · What you do

Decide, with your own thresholds

  • AllowKnown device for this account
  • ChallengeNew device, hosting IP: ask for a code
  • Blockbot and velocity
Read the guide

Decision lab

Switch signals on and off. The score is a plain sum of weights.

decision lab
Signals

Weights are the defaults in scoring.default.json. The cut-offs at 25 and 60 are examples; your app sets its own.

20suspectScore / 100
AllowLet the action through.
20/ 100
reasons
  • velocity+20

Implementation

One browser call, one server check.

01IdentifyCall the SDK on the action and send the eventId with it.
02VerifyYour server reads the event with a secret key.
03DecideAllow, challenge or block, with your own thresholds.
identify.ts
const trace = createClient({ apiKey: 'pk_...', endpoint: 'https://id.example.com' });

// On the action (signup, login, checkout), then send eventId with the form.
const { eventId } = await trace.get();
Example response, illustrative
{  "eventId": "evt_example"}

Start in shadow mode. Block later.

Log the decision for a week, check who it would have stopped, then turn it on.