Yes. The conversational UI is a presentation layer over a regular form, so entries land in wpforms_entries and field values land in the fields array inside wpforms_entry_meta. SleekView pivots that array so every field becomes a queryable column.

WPForms only saves entries on submit, so step-by-step drop-off isn't recorded by the addon out of the box. The completed-entry trend and per-form completion volume still surface meaningful campaign performance, and Form Locker or analytics integrations can fill gaps if step-level tracking matters.

Yes. Pivot the dropdown field out of the meta array, group by its value, and chart a Pie or Bar of the distribution. Useful for qualifying fields like role, use-case, or company size on a lead-capture form.

Aggregations run as SELECT ... GROUP BY against indexed columns on wpforms_entries and the pivoted meta. Card render time scales with the cardinality of the group-by more than raw row count, so high-volume conversational forms stay responsive.

Yes. Pivot the field out of the meta array and count non-null values divided by total entries for the form. Optional fields will skew lower while required fields stay near 100%. Useful for spotting friction in an optional question.

Cards re-query on view load and filter change. Set a refresh interval per view if a launch dashboard needs near-live counts. Idle dashboards don't poll, so closed views don't add database load.

Yes. Save views and scope them per WordPress role or capability. Marketing gets a campaign completion dashboard, sales ops gets a qualifier-distribution view, form admins get a field fill-rate audit. Personal filters stay scoped to each user.

Each card exports aggregated rows as CSV with the group-by labels and the counts. Useful for handing marketing the per-form completion breakdown or archiving a campaign-end snapshot of dropdown distributions.