Five free articles means five.
Count reads per visitor instead of per cookie, so a private window or cleared storage does not reset the meter.
Signalsincognito
Step 4 of 4Linked to the same deviceBlock
4of 4
Read 4 of 5ChromeAllow
Read 5 of 5Chrome, privateAllow
Read 6Chrome, cookies clearedBlock
Read 7FirefoxBlock
Limit reachedSame visitor, different window
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
- Private windowsA fresh meter in every incognito tab.
- Cleared cookiesOne click resets cookie-based limits.
- Browser switchingFive more reads in another browser.
02 · What Trace sees
Fields on the verified event
- visitorIdSurvives private windows and cleared cookies.
"visitorId": "Xk3pQ9vLmT2aR7sBn4Wc","confidence": 0.97 - incognitoKnow a read came from a private window.
"incognito": { "detected": true }
03 · What you do
Decide, with your own thresholds
- AllowWithin the meter
- BlockShow subscribe
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.
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.