Referral programs pay for each new user. Check that the referrer and the new account are not the same device.
What you will build: a check on the action you protect that allows normal users, asks doubtful ones to verify, and blocks the clear cases. See the referral fraud overview for the attack in pictures.
Before you start
Finish one Web quickstart (for example JavaScript or React) and one Server quickstart (for example Node.js). The decision code below is TypeScript; every server SDK returns the same event.
How the attack works
- Self-referral. Inviting your own second account.
- Browser hopping. The invite opened in another browser.
- Referral rings. One device signing up many invitees.
What to look at
| Field | Why it matters here |
|---|---|
deviceId | Compare referrer and invitee devices. Shared by every browser on one device. Store it with the account or the action. |
crossBrowser | Catches the invite opened in another browser. |
- 1
Identify on the action
Call the browser SDK when the user performs the action, not on page load, and send the
eventIdwith the request.TypeScriptconst { eventId } = await trace.get({ tags: { action: 'referral-fraud' } }); - 2
Verify on your server
import { verifyEvent } from '@trace-id/sdk-node'; const event = await verifyEvent(eventId, { secretKey: process.env.TRACE_SECRET_KEY!, endpoint, timeoutMs: 1500 }).catch(() => null);try: event = client.get_event(event_id) except trace_device.VerifyError: event = None # fail opentry { $event = $client->getEvent($eventId); } catch (Trace\VerifyError $e) { $event = null; }Map<String, Object> event = null; try { event = trace.getEvent(eventId); } catch (Trace.VerifyException e) { /* fail open */ }const event = await trace.verify(eventId).catch(() => null);Events can be verified for 60 minutes. If verification fails, decide whether to fail open or closed; for most of this flow, fail open.
- 3
Decide
TypeScriptconst invitee = await trace.verify(eventId); const referrer = await db.users.get(referrerId); const linked = invitee.linkedVisitors.map((v) => v.visitorId); if (invitee.deviceId === referrer.deviceId || linked.includes(referrer.visitorId)) return noReward();trace.verify()is the embedded call; with a server SDK, use theeventfrom step 2 instead. The thresholds are yours. Trace scores and explains;event.reasonslists which signals added how much, so log it with every decision.
Example decisions
Referrals from @nour, illustrative:
| New account | Device | Decision | Why |
|---|---|---|---|
| @sara | Other device | Allow | Reward paid |
| @nour_2 | Nour's laptop, Firefox | Block | Linked to the referrer's device |
| @friend_x | Nour's laptop, private | Block | Same visitorId as the referrer |
Roll it out
- Ship steps 1 to 3 with logging only: record the decision, block nothing.
- After a week, look at who would have been blocked or asked to verify. Shared computers, offices and privacy tools are the usual false positives.
- Turn on Verify first, then Block for the clearest cases.