An event lands
New identifications appear within seconds, with the visitor, the external ID and when. Filter by visitor, external ID, IP, signal, bot verdict, score and date, and save the view you review every morning.
Everything the API knows, readable without a query
Events arrive within seconds. Open one to see the visitor's week, the signals and the score, and who else used that device.
Follow a case
From the moment an event lands to the accounts behind it.
Open it
One page per event: the visitor's week, the browser and OS, the network with its VPN and proxy details, what tampering was found, how the visitor was matched, and where the score sits among the project's last 30 days.
See who shares the device
A device lists every external ID seen on it, and an external ID lists the devices and IPs it was seen with. Follow the links a few steps out to find the external IDs related through a shared browser or connection.
Hand it to your systems
Every webhook delivery with its attempts, the response and the timing, and a button to send it again. Send a test event before the first real one arrives.
Everything in it
The same data the API returns, for whoever reviews the case.
-
Events
Every identification within seconds, searchable by visitor, external ID, IP, signal and score.
-
Event page
The visitor's week, browser, network, VPN and tampering details, and the score's percentile.
-
Signals
How often each signal fired over the last 30 days, one tile per signal.
-
Insights
Chart identifications, visitors, flagged share or scores over time, split by country, browser, signal or action, against the period before.
-
Related
The external IDs that share a browser or an IP, and the ones related to them.
-
Webhooks
Every delivery with its attempts, response and timing, and a button to send it again.
-
Usage
This month's identifications, the estimated bill and the budgets.
-
Team
Invite teammates by email; everyone on a project sees and manages it.
-
Audit log
Who changed keys, settings and teammates, from where and when, with a CSV export.
A project under your control
Keys, origins, budgets and retention live in the project's settings. Every secret is shown once and stored as a hash.
- API keys
- Named public and secret keys, shown once, each with its own spend limit and expiry.
- Allowed origins
- The sites a public key works on. Any other page, or a request from outside a browser, is refused.
- Budgets
- A daily, weekly or monthly amount. Past it, identification pauses quietly instead of failing.
- Retention
- Keep events for 30 days, 1, 3 or 5 years, or until you delete them.
- Zero trust mode
- The browser gets a request ID and nothing else.
- Risk weights
- How much each signal counts in your project's score.
Watch your first event arrive
Get your keys, install the agent, and open the events page.