Keep ratings honest.
Reviews, polls, likes and surveys are only useful if each one comes from a different person. Group them by device.
SignalsmultiAccount
Step 4 of 4Same visitorIdBlock
@linaDevice AAllow
@omarDevice BAllow
@lina_2Device ABlock
anonymousDevice A, privateBlock
counted2removed2
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
- Sock puppetsMany accounts praising one product.
- Poll stuffingVoting again in a private window.
- Survey farmsOne device collecting many survey rewards.
02 · What Trace sees
Fields on the verified event
- deviceIdOne vote per device, across accounts.
"deviceId": "Xk3pQ9vLmT2aR7sBn4Wc" - multiAccountFlags the device behind many accounts.
"multiAccount": { "detected": true, "details": { "accountsOnDevice": 5, "threshold": 2 }}
03 · What you do
Decide, with your own thresholds
- AllowCounted
- BlockAlready voted from this device
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.
25suspectScore / 100
ChallengeAsk for a code, or send to review.
25/ 100
reasons
multiAccount+25
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.