Dashboard · Detection

Smart Signals

Counts per signal, the score distribution, and why some have no rate.

Which signals fired, how often, and how suspect scores are distributed across your traffic.

The signal grid#

Each tile is one signal with its detection count over the selected period. Click a tile for its series over time, or to open the events list filtered to it.

Switch between counts and percentages with the toggle at the top.

Why most signals have no rate#

A tile may say "Count only: no rate available". This is not an omission.

A check records only when it fires. A visit without that signal may have run the check and passed, or never run it, and the record cannot tell those apart. No honest denominator means no honest rate.

Bots are the exception, for the reason in Bots & AI agents.

A signal reading "Not measured" means the web engine does not measure it, usually a mobile signal. It does not mean "measured and zero".

The score distribution tab#

Visits by score band, with the challenge (35) and block (70) thresholds drawn in.

This is the screen most worth reading before turning blocking on. If a meaningful share of your ordinary traffic sits above 70, you want to know that before it becomes lost orders rather than after.

Web only#

Only the web SDK reports to this dashboard. Mobile signals always read as unmeasured. See Signal catalogue.