Yes. A/B variants are stored as related cartflows_step posts that point back to the canonical step. SleekView shows variants grouped under their parent step with conversion deltas and a clear winner badge once enough traffic accumulates, so test decisions get made on the data instead of in a separate spreadsheet.

Yes. Cart abandonment data tracked by CartFlows lives in its own structure and surfaces as joinable rows in a separate view. That view answers the abandonment-recovery questions — average time-to-abandon, recovery rate per email — alongside the main funnel performance table.

Yes when SleekView uses CartFlows' status-change API. The plugin's hooks for analytics events, automation triggers, and cache invalidation all fire as expected. Direct DB edits skip hooks by design and are an opt-in per view for bulk clean-up where hooks would just churn the system.

Yes. The chosen page builder for each step — Elementor, Beaver Builder, Divi, Bricks, Gutenberg — is stored in step postmeta and exposed as a filterable column. That matters when you're standardising on one builder and need to find the legacy steps still using the old one.

Yes. Orders flagged with the source flow ID via meta are joinable to flows for revenue attribution. The funnel-revenue view answers which flow drove which orders across any date range, which is the number that justifies the funnel-building work to the rest of the business.

Yes. Views are gated by WordPress capability and savable per role. Growth marketers see ranking views; funnel ops sees status and bulk-edit views; stakeholders see a read-only summary. Column sets save per role for predictable workflows across the team.

Yes. CartFlows distinguishes global checkout configuration from per-flow checkout step config. SleekView surfaces both — a global view for the platform-level config and per-flow rows for flow-specific overrides — so a misconfigured per-flow checkout that bypasses a global rule gets caught quickly.

Yes. Joining ordered steps within a flow and computing the visitor delta between consecutive steps produces a drop-off column that lights up the worst points in the funnel. That column is often more actionable than raw conversion rate, because it shows where customers leave rather than just whether they converted at the end.