Limited drops, fair queues.
Concert tickets and sneaker drops sell out to scripts in seconds. Spot automated checkouts and one buyer behind many carts.
SignalsautomatedInputbotmultiAccount
Step 4 of 4Same device as @buyer_17Block
LIVE
@fan_lina48 sAllow
@omar35 sAllow
@buyer_172 sBlock
@buyer_182 sBlock
drop is live
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
- Checkout botsCarts filled faster than any person can click.
- Account armiesMany accounts to beat per-person limits.
- Cloud fleetsHundreds of headless browsers at release time.
02 · What Trace sees
Fields on the verified event
- automatedInputClicks and keys no person produces.
"automatedInput": { "detected": true } - botHeadless and automated browsers.
"bot": { "detected": true } - multiAccountOne device behind many buyer accounts.
"multiAccount": { "detected": true, "details": { "accountsOnDevice": 6, "threshold": 2 }}
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
automatedInput+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.