Your data, read by people.
Scrapers copy prices, listings and content at machine speed. Spot the automated browsers and the visitors reading far more than anyone does.
SignalsbotvelocitydatacenterIp
Step 4 of 4bot + highActivityBlock
Xk3p…9Wc14 pagesAllow
Qp8w…kYa60 pagesAllow
Mn2r…e8Q900 pagesChallenge
Zt7c…1Lb4,000 pagesBlock
events per visitor, 5 min threshold
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
- Price monitoringCompetitors pulling every price, every hour.
- Listing harvestsWhole catalogues copied in one night.
- Hosted fleetsHeadless browsers on cloud servers.
02 · What Trace sees
Fields on the verified event
- botHeadless and automated browsers.
"bot": { "detected": true } - velocityEvents per visitor and visitors per IP.
"velocity": { "detected": true, "details": { "exceeded": ["eventsPerVisitor1h"] }} - datacenterIpTraffic from cloud and hosting ranges.
"datacenterIp": { "detected": true }
03 · What you do
Decide, with your own thresholds
- AllowNormal browsing
- Challengevelocity + datacenterIp
- Blockbot + highActivity
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.
60suspectScore / 100
BlockStop the action.
60/ 100
reasons
bot+60
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.