Yes. The view reads rows from the same log table Google Captcha writes per challenge, including form key, outcome, timestamp, and score. The grid reflects the live log without an export step.

Yes. The form column is filterable, so isolating login, registration, lost-password, or comment traffic is one click. A login-only view scoped to the last 24 hours is the standard credential-stuffing detection slice.

Yes. The Pro version adds advanced form integrations like WooCommerce and BuddyPress checkout but writes to the same verification log table. SleekView reads whichever forms are present without additional configuration.

Yes. The score column is sortable, which is how threshold tuners find the verifications sitting on the edge of the current threshold. The grid turns score-distribution analysis into a one-click operation.

Yes. The same data source feeds both, so a row reviewed in the grid stays in sync with the donut on the next chart render. The grid is the row-level workspace; charts are the rollup over the same log.

Yes. Google Captcha supports multisite, and SleekView respects that scope. On multisite each subsite has its own verification grid, and a network-level view can roll forms up across blogs when one security team monitors the whole network.

No. Only the rows on the current page are queried, and the log table is indexed on the timestamp column. A site with millions of verifications a month queries the same as a site with a few thousand because pagination keeps the row count constant.

Yes. Any filtered view exports to CSV with active filters preserved. Security reviews get a defensible sheet of the exact failed-verification slice the auditor asked for.