Yes. wp_wpzerospam_log and wp_wpzerospam_blocked exist in the free version and SleekView Charts reads from both. Premium features simply expand the available source data, and the dashboard layout stays exactly the same on every license tier.

Yes. Zero Spam labels each detection with the integration it ran inside, so a Stacked Bar card grouped by type shows Contact Form 7, Gravity Forms, native comments, and WooCommerce registration side by side on the same chart card for the dashboard.

Yes. wp_wpzerospam_log and wp_wpzerospam_blocked can sit side by side on the same dashboard. Detections answer who is being blocked, the blocked table answers which rules are active, and a shared date range filter keeps both card sets aligned.

No. Charts read from existing wpzerospam tables and never write to them. Zero Spam continues to evaluate submissions, score detections, and log blocked rows exactly as before, with no added write load on the anti-spam pipeline.

Yes. Each card supports CSV export of its aggregated values, and the underlying SleekView grid is one click away for the raw detection rows behind any chart. Useful when sharing numbers in a monthly client report or a quarterly security audit.

No. IP-rule edits live inside Zero Spam's own admin screens. The dashboard is intentionally read-only so the visual layer never modifies the wpzerospam tables or interferes with the plugin's runtime detection and blocking behavior on the site.

Yes. Zero Spam stores its data per blog, and SleekView respects that scope. A network admin can build a per-site dashboard or one network-wide rollup that ranks sites by daily detection volume or by the top form integration across every connected site.

Yes. Zero Spam can pull from shared IP block lists and write its own detections into a shared service. SleekView reads only the local wpzerospam tables, so the dashboard reflects exactly what was logged on this site regardless of what the shared service decided elsewhere.