Yes. fluentform_transactions and fluentform_subscriptions are exposed as separate chart datasets. Build a transactions dashboard for refund and chargeback audits, or a subscriptions dashboard for renewal status mix, with each table's columns as group-by options.

Yes for low-cardinality keys (dropdown selections, status fields, radio buttons). The pivot runs at query time so new fields show up immediately. Free-text fields produce too many distinct values to chart usefully and are better left to the table view.

Geo fields are populated from the IP at submission time by Fluent Forms itself. Accuracy depends on which version of the plugin captured the data — older entries may have nulls if the feature wasn't enabled then. SleekView surfaces whatever's in the column; it doesn't re-resolve historical IPs.

The base submissions table exists in the free version. Payment columns, conversational forms, and certain integrations are pro features, so a payment-focused dashboard needs Pro to have data in payment_total and payment_status. SleekView reads whatever the plugin populates, regardless of edition.

Numeric sums treat payment_total as a number regardless of currency, so a multi-currency sum mixes EUR, USD, GBP into one figure. Filter or group by currency to keep per-currency sums separate, which matches how finance reconciles against gateway payouts.

Deleted submissions disappear from the source table, so they drop out of charts automatically on the next refresh. There's no cached aggregate to clean up. Trashed entries (soft-deleted) can be included or excluded per view depending on whether the team wants audit visibility into trashed rows.

Aggregations run as SELECT ... GROUP BY queries against indexed columns. Performance scales with the index on the group-by column, not just total row count, so grouping by form_id, created_at, or payment_status stays fast on millions of rows when the indexes are healthy.

Saved views have a stable identifier that's shareable inside WP Admin to anyone with the right capability. Anonymous-public sharing isn't part of the design; charts always render inside the admin so the same role and capability checks apply.