Yes. The perk uses Gravity Forms' built-in multi-page mechanics, so completed entries live in gf_entry and partial submissions live in gf_draft_submissions with the saved page_number. SleekView reads both and exposes them as one funnel dataset for grouping and counting.

Yes. A Bar grouped by page_number on gf_draft_submissions surfaces how many users abandoned at each step. Combine with a count of completed gf_entry rows in another card to show the full funnel from page 1 to final submission.

Filter the dataset to a single multi-page form via form_id, then chart completed rows from gf_entry versus active drafts from gf_draft_submissions. Repeat the saved view per form, or group by form_id on a single Bar to compare ratios across the whole site at once.

Aggregations run as SELECT ... GROUP BY against indexed columns on gf_entry and gf_draft_submissions. Card render time scales with the cardinality of page_number and form_id, not raw row count, so even a backlog of thousands of drafts stays responsive.

Cards re-query on view load and on filter change. Set a refresh interval per view if a marketing dashboard needs near-live numbers during a launch. Idle dashboards don't poll, so a closed view doesn't add database load to a busy site.

Yes. Save views and scope per WordPress role or capability. Marketing ops sees daily completion trends, form admins see per-form drop-off, and editors see only the forms they own. Each user keeps their personal filters between visits.

SleekView counts drafts and completions as they are at query time, so a redesign mid-history shows up in the trend chart immediately. Filter to before and after the redesign date to compare drop-off page by page and confirm whether the change actually helped.

Each card exports its aggregated rows as CSV with the group-by labels and the aggregate values. Useful for sharing per-page drop-off with the marketing lead, archiving the campaign-end funnel snapshot, or feeding the numbers into a separate report.