Giveaways, sweepstakes and contests only work if each entry is a different person. Count entries by 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 giveaway and contest abuse 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
- Entry stuffing. Dozens of entries under different emails.
- Private windows. A fresh entry in every incognito tab.
- Entry bots. Scripts submitting the form all day.
What to look at
| Field | Why it matters here |
|---|---|
incognito | Private windows keep the same visitorId. |
deviceId | One entry per device, across browsers. Shared by every browser on one device. Store it with the account or the action. |
- 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: 'giveaway-abuse' } }); - 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 { deviceId } = await trace.verify(eventId); if (await db.entries.exists({ contestId, deviceId })) return alreadyEntered(); await db.entries.insert({ contestId, deviceId, email });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
Entries to one giveaway, illustrative:
| Browser | Decision | Why | |
|---|---|---|---|
| [email protected] | Safari | Allow | Counted |
| [email protected] | Safari, private | Block | Same visitorId |
| [email protected] | Chrome | Block | Same deviceId |
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.