No. Per-funnel conversion reports remain the right place for individual funnel analytics. SleekView Charts adds the cross-funnel weekly dashboard the default screens do not assemble. The two layers complement each other rather than competing for the same screen real estate inside WP Admin.

Yes. The SleekView dataset filters gh_events by step_type equal to send_zapier (or whichever step type the Zapier extension registers in your version) so every card scopes cleanly to Zap dispatches. Other funnel event types stay on a separate dashboard if you want them.

It uses the status column on gh_events, which Groundhogg sets based on the Zapier webhook response. Failed, cancelled, and skipped statuses surface on the same Donut, so any dispatch that did not land cleanly is visible without leaving WP Admin to check Zapier's task history.

Yes. Dashboard-level filters apply to every chart card. Scope the whole dashboard to a single funnel, a tag from gh_tag_relationships, or a contact segment to see Zap activity for that audience without rebuilding cards. The same dashboard powers per-funnel views with a one-click switch.

Yes. Aggregations run on the indexed columns Groundhogg already maintains (contact_id, funnel_id, step_id, time, status), so dashboards with tens of thousands of dispatched rows render in seconds. The Charts engine paginates and pushes filters into SQL rather than loading rows into PHP for counting.

Yes. Each chart card exposes its underlying row set, which exports to CSV with the active filters applied. That gives ops a clean handoff to spreadsheets or BI tools for monthly board reports without round-tripping through screenshots of the Groundhogg admin.

Skipped and failed are separate values in the gh_events status column. The status Donut shows them as distinct slices so a high skipped count (often a tag-based exclusion working as intended) is not confused with a real webhook failure that needs a fix in the funnel step configuration.

Yes. Both the free and Pro versions of the Zapier extension write into the same gh_events and gh_activity tables. Whichever step types your install registers can be pulled into the dataset, so Pro-only triggers appear alongside the standard send_zapier rows on the same dashboard.