Count reads per visitor instead of per cookie, so a private window or cleared storage does not reset the meter.
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 paywall and metering 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
- Private windows. A fresh meter in every incognito tab.
- Cleared cookies. One click resets cookie-based limits.
- Browser switching. Five more reads in another browser.
What to look at
| Field | Why it matters here |
|---|---|
visitorId | Survives private windows and cleared cookies. Stable id of this browser, through private windows and cleared cookies. |
incognito | Know a read came from a private window. |
- 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: 'paywall' } }); - 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 { visitorId } = await trace.verify(eventId); const reads = await db.reads.countThisMonth(visitorId); return reads >= 5 ? showPaywall() : showArticle();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
Reads from one reader, this month, illustrative:
| Article | Browser | Decision | Why |
|---|---|---|---|
| Read 4 of 5 | Chrome | Allow | Within the meter |
| Read 5 of 5 | Chrome, private | Allow | Same visitorId, meter continues |
| Read 6 | Chrome, cookies cleared | Block | Show subscribe |
| Read 7 | Firefox | Block | Linked to the same device |
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.