When a visitor was judged suspicious or blocked, the first question is why. The “Analytics” page of a key has two tabs for it: “Block Reasons” and “Block Log”. This post shows both. The film below shows them on the real dashboard with sample data, silent and with short captions. The text under it says the same in words, so you can follow along without playing the film.
The film in short
The film opens “Analytics”, switches to the tab “Block Reasons” and points at the card “Block Reason Codes”, switches to “Block Log” and points at the table, then opens one entry with “View”: the “Block Detail” with the “Confidence breakdown”. The visitors in the sample data are scripts and are judged “Suspicious”; the film makes no statement about how many requests a site gets or how many are stopped. It has no sound and does not start by itself.
Step 1: Block Reasons
“Block Reasons” counts the reason codes for the chosen period. Each line shows the code, for example “MOUSE_CLAIMED_BUT_UNUSED”, a bar, the count and a plain description such as “Neither typed nor moved the mouse” or “No Mouse Movement”. The codes tell you which signals made the difference.
Step 2: the Block Log
“Block Log” lists recent blocked and suspicious requests with their time, verdict, confidence, reasons, page and country. A request shows reasons where they are known; some rows have none. What actually happens to a suspicious visitor is set in the security policy of the key (see set up the security policy).
Step 3: open one entry
“View” opens the “Block Detail” of a request: verdict, confidence, timestamp, page, country, device and browser, the “Reasons” and the “Confidence breakdown” with one bar per signal, for example keyboard, pause, mouse, speed, context and scroll. This is the same view as in understand the result, reached from the analytics.
What the film does not show
The film does not show the count of attempts rejected by your server-side check; that figure appears only once your server reports blocks. It also does not say which reason is the right one to act on. The documentation page for analytics lists everything the page offers.