No. The Sendy install still owns deliverability, opens, and clicks since the sends happen there. SleekView Charts adds the WordPress-side dashboard for submissions, form distribution, and signup velocity that WP Sendy does not assemble in its own admin.

Yes. Even when contacts move to the Sendy install on submit, WP Sendy logs the submission attempt locally with form ID, list ID, and timestamp. SleekView reads those local rows to render every chart in the dashboard without an external API call.

Yes. The local log records status (success or failure) on each attempt. Group by status to chart failure rate as a trend line, or filter to failures only and rank failing forms on a Bar card for fast remediation.

Yes. Dashboard-level filters apply to every chart card. Filter by a single sendy_list_id and every card scopes to that list, so per-list dashboards become one-click switches rather than per-card reconfiguration.

Yes. Aggregations run on indexed columns and avoid full table scans. Hundreds of thousands of WP Sendy submissions render charts in seconds because the Charts engine uses pagination and indexed joins rather than scanning meta.

Yes. Each chart card exposes its underlying row set, which exports to CSV with active filters applied. The export feeds board reports, attribution tooling, and ad platforms without bouncing through the Sendy install.

Yes. Each subsite has its own WP Sendy config and submission log, and SleekView Charts reads the current subsite by default. Network-wide dashboards can be configured explicitly when reporting spans multiple subsites.

It still works. The plugin records the install or API token reference on each form, and SleekView can group by it. Multi-brand setups get one dashboard per install or a combined dashboard with brand on a Pie card.