Less friction for the devices you know.
Remember the devices each user signs in from. Skip the extra code on those, and save it for the ones you have never seen.
SignalsdeviceIdvisitorId
Step 3 of 3New device: send a codeChallenge
Work laptop40 times
Phone12 times
Hotel PCNever
Trusted: no codeAllow
Trusted: no codeAllow
New device: send a codeChallenge
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
- MFA fatigueUsers tired of codes on every login.
- Blanket checksEveryone pays the friction the attacker should.
- Cookie-only trustLost when storage is cleared.
02 · What Trace sees
Fields on the verified event
- visitorIdRecognise the browser across sessions.
"visitorId": "Xk3pQ9vLmT2aR7sBn4Wc","matchKind": "token" - confidenceTrust only strong matches.
"confidence": 0.99
03 · What you do
Decide, with your own thresholds
- AllowTrusted: no code
- ChallengeNew device: send a code
Decision lab
Switch signals on and off. The score is a plain sum of weights.
Signals
Weights are the defaults in scoring.default.json. The cut-offs at 25 and 60 are examples; your app sets its own.
30suspectScore / 100
ChallengeAsk for a code, or send to review.
30/ 100
reasons
tor+30
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.