Fluent Forms does not ship a strong reporting layer of its own beyond per-form lists and a basic dashboard widget. SleekView Charts reads the same fluentform tables and renders the picture as a configurable dashboard with cards, filters, and saved views. The two are complementary: Pro for entry-level admin, SleekView Charts for the reading and analysis layer.

fluentform_subscriptions sits alongside fluentform_transactions. SleekView joins it for renewal date, status, and recurring amount, so charts can render MRR, churn windows, and renewal volume. The per-subscription admin keeps the detail.

Where Pro records partial state for conversational forms, those rows are chartable as separate slices. Most installations only persist completed submissions, in which case drop-off is inferred from the per-step view counts captured by analytics rather than from Fluent Forms itself.

Yes. The free plugin owns fluentform_submissions and fluentform_entry_details; SleekView reads them either way. The Pro-only tables (transactions, subscriptions) only have rows when Pro is active, so revenue cards are only meaningful with Pro installed.

Live. SleekView Charts queries the Fluent Forms tables directly, so a card refresh reflects submissions, payments, and refunds up to the moment of the request. There is no separate sync that can fall behind.

Yes. Filter the base view by form_id and every card on the dashboard inherits the scope. Useful for a campaign dashboard on one paid form alongside the cross-form view for finance and ops.

No. Chart queries hit existing Fluent Forms indexes on form_id, status, and created_at. Aggregations are bounded by the date range or filter on each card, so even very large submission tables return chart numbers in well under a second.

Repeater fields store their values in fluentform_entry_details with the parent submission id. SleekView pivots them the same way it does single-value fields, and charts can aggregate over the repeated values when the form structure makes that meaningful.