WP-SpamShield is currently sold as a Pro plugin from Red Sand Marketing. The block log shape is the same on every active install, so SleekView's chart cards read the same option keys regardless of the license tier installed on the WordPress site.

Yes. WP-SpamShield labels each block with the form integration it ran inside, so a Stacked Bar card grouped by form_source shows Contact Form 7, Gravity Forms, native comments, and registrations side by side on the same chart card for the dashboard.

No. Charts read from the existing WP-SpamShield option keys and never write to them. The plugin continues to evaluate submissions, apply its filter chain, and log blocks exactly as before, with no added load on the anti-spam pipeline on the site.

Yes. WP-SpamShield records a short reason code for every block, and the indexed source exposes that field. A Pie card grouped by reason_code shows the distribution across honeypot, bad header, blocked content, and the rest of the rule set on the same dashboard.

Yes. Each card supports CSV export of its aggregated values, and the underlying SleekView grid is one click away for the raw blocked rows behind any chart. Useful for monthly reports that need to attach both the chart summary and the underlying log on the site.

No. Black-list edits and integration toggles live inside WP-SpamShield's own settings screens. The dashboard is intentionally read-only so the visual layer never modifies the WP-SpamShield option keys or interferes with the plugin's runtime block behavior.

Yes. WP-SpamShield 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 blocked volume or by the top form source across every connected site.

That is fine. SleekView reads each plugin's log as its own source, so a dashboard can show WP-SpamShield blocks on one row of cards and a second plugin's blocks on a second row. The combined view makes it clear which filter is catching which kind of traffic.