Yes. The add-on is what populates the wp_wpcw_subscriptions table with Stripe subscription rows. Without it the WPCW course tables still exist but the subscription join is empty, so cards that reference MRR or renewal trend fall back to enrolment-only counts.

Yes. Page-level filters propagate to every card, so picking a course_id, a date range, or a status recomputes every Number, Pie, Bar, and Area on the dashboard. Saved views per launch keep historical numbers stable.

Yes. An Area card grouped by the cancelled timestamp on the subscriptions table trends churn per day or week. A second Number card computes the rolling churn rate (cancellations divided by active subscriptions at period start) for a real metric, not just a count.

Yes. The period column on wp_wpcw_subscriptions stores the billing cycle. SleekView normalises recurring_amount to monthly using the period so MRR cards mix annual and monthly subscribers on the same basis.

Reads run against the live tables on dashboard load, so a subscription just created or cancelled by the Stripe webhook appears immediately. Heavier aggregates (LTV by course year-to-date) opt into a configurable cache so they do not recompute on every visit.

Yes. Each card exports its underlying aggregated rows as CSV or JSON. Useful for finance reviews that need to send the WPCW-side subscription roster alongside the Stripe export for reconciliation.

Yes. SleekView Charts reads the same wp_wpcw_subscriptions rows the SleekView Table view writes to, so a manual status change from on_hold to active recomputes the dashboard. WPCW hooks fire normally so downstream automation continues.

Yes. Each subsite has its own WPCW tables and SleekView Charts reads the current subsite. Cross-site aggregation is not supported, but per-site dashboards behave as expected and can be scoped per role on each subsite.