Yes. The aggregation runs against the same entry storage SleekView's table view reads, which works with both free and Pro tiers. Pro features add fields and integrations; the dashboard surfaces those automatically as additional group-by options when they appear in the data.

Yes. A form filter chip on the dashboard scopes every card to the selected form IDs. Marketing might watch only contact and demo; events might watch only RSVP forms. The cards re-aggregate on filter change.

By default yes, because spam-flagged entries still live in the storage. Filter the status chip to exclude spam and every card re-aggregates without those rows. A spam-only dashboard surfaces the worst-affected forms for cleanup.

Yes. SleekView Charts is read-only; it reads stored entries and aggregates them. Zapier, Mailchimp, HubSpot, and any other Pro integrations continue to fire on submission events exactly as they did before.

File-upload counts can be charted (count of rows with non-empty upload field), but the files themselves remain in the table view. Useful for application forms where you want to read how many submissions actually attached a resume.

It includes every entry in the storage. To exclude tests, filter out the test source page or the internal email domains before the cards aggregate. The filter persists with the saved view.

If forms collect payments via add-ons that write status to the entry, yes. Group by status or by gateway, filter to paid, and the Number, Donut, Bar, and Area cards all become finance-reporting cards over the same data.

No. SleekView Charts reads the existing weForms entry storage and aggregates in the query layer. No materialized tables, no shadow database, no extra schema. The dashboard works on whatever weForms already wrote.