Yes for entry storage. Lite sends submissions as email only with no database persistence, so there's no source data to chart. Pro creates wpforms_entries, wpforms_entry_fields, and wpforms_payments on activation; SleekView detects the tables and the chart dataset picker lights up.

SleekView uses a left join from entries to payments so entries without a payment row still appear in entry-count cards. Revenue cards naturally exclude unpaid rows because total is null for them. This keeps volume and revenue figures consistent with how the joined table view renders.

Yes for low-cardinality entry-field keys. Dropdown selections, status fields, and radio buttons pivot well as chart dimensions. Free-text fields (names, message bodies) produce too many distinct values to chart usefully; leave those for the table view.

Spam decisions are written to the entry's status column and to wpforms_entry_meta with reason details. Chart spam-flagged entries as a count per form, or per day, with the spam reason as a secondary group-by once the meta key is added as a dimension. Useful for spotting spam waves before they bury legitimate leads.

WPForms Form Abandonment stores partials as regular entries with a partial status. They appear in entry-count charts by default, so filter them out for clean sales-triage dashboards, or build a separate abandonment dashboard filtered to status = partial.

Yes. Group revenue cards by currency to keep per-currency sums separate, or filter the view to one currency for a clean total. Mixing currencies in a single sum is supported by the math but rarely what reconciliation wants.

Aggregations run as indexed GROUP BY queries against entries and payments. Performance scales with the index on the group-by column, so sites with hundreds of thousands of entries stay responsive when grouping by form_id, status, gateway, or date.

Yes. Save a Sales triage view, a Payment audit view, and a Spam queue view, each scoped to the appropriate WordPress role or capability. Per-user filters don't leak across the team, so each role lands on a dashboard tuned to their work.