Refer friends, not yourself.
Referral programs pay for each new user. Check that the referrer and the new account are not the same device.
SignalscrossBrowser
Step 3 of 3Same visitorId as the referrerBlock
one device
deviceId Xk3p…@saraOther deviceAllow
@nour_2Nour's laptop, FirefoxBlock
@friend_xNour's laptop, privateBlock
accounts on device3limit 2
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
- Self-referralInviting your own second account.
- Browser hoppingThe invite opened in another browser.
- Referral ringsOne device signing up many invitees.
02 · What Trace sees
Fields on the verified event
- deviceIdCompare referrer and invitee devices.
"deviceId": "Xk3pQ9vLmT2aR7sBn4Wc" - crossBrowserCatches the invite opened in another browser.
"linkedVisitors": [ { "browser": "firefox", "confidence": 0.9, "sameNetwork": true }]
03 · What you do
Decide, with your own thresholds
- AllowReward paid
- BlockLinked to the referrer's 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.
15suspectScore / 100
AllowLet the action through.
15/ 100
reasons
crossBrowser+15
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.