One entry. One chance.

Giveaways, sweepstakes and contests only work if each entry is a different person. Count entries by device.

Signalsincognito
scenario
Step 3 of 3Same deviceIdBlock
Figure 1Entries to one giveaway. Illustrative data. Hover or focus to pause; pick a step to scrub.

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

  1. Entry stuffingDozens of entries under different emails.
  2. Private windowsA fresh entry in every incognito tab.
  3. Entry botsScripts submitting the form all day.
02 · What Trace sees

Fields on the verified event

  • incognitoPrivate windows keep the same visitorId.
    "incognito": { "detected": true }
  • deviceIdOne entry per device, across browsers.
    "deviceId": "Xk3pQ9vLmT2aR7sBn4Wc"
03 · What you do

Decide, with your own thresholds

  • AllowCounted
  • BlockSame visitorId
Read the guide

Decision lab

Switch signals on and off. The score is a plain sum of weights.

decision lab
Signals

Weights are the defaults in scoring.default.json. The cut-offs at 25 and 60 are examples; your app sets its own.

5suspectScore / 100
AllowLet the action through.
5/ 100
reasons
  • incognito+5

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.