Kadence Conversions ships popups, slide-ins, sticky bars and content gates from the same builder used elsewhere in the Kadence ecosystem. Each campaign lives as a custom post type with display rules, an A/B variant flag, optional Kadence Blocks form embeds and per-campaign impression and conversion counters stored in postmeta.

SleekView reads that CPT and its meta directly and renders one row per campaign: title, campaign_type (popup, slide-in, sticky bar, gate), status, impressions, conversions, ab_variant and last published date. Filter to campaign_type=popup to scope a refresh review. Sort by conversions to find the long tail of zero-conversion campaigns. Filter by trigger meta (exit intent, scroll depth) to assemble per-trigger shortlists.

The plugin keeps owning the builder, the runtime trigger logic and the per-campaign analytics tab. The table view owns the portfolio surface, so cross-campaign questions stop meaning a tab marathon and start meaning a saved filter.

Kadence is known for a tight, fast ecosystem, and Kadence Conversions fits that pattern: the campaigns ship clean, the analytics are honest, the per-campaign tab is well designed. The trade-off is that the operational picture is cross-campaign, and the plugin admin lists campaigns without aggregating. A new popup launched last week, a slide-in retired three months ago, a sticky bar nobody remembers shipping: those rows are all in the CPT, but the per-campaign analytics tab is the wrong surface for portfolio review.

SleekView reads the same CPT and stats meta the plugin already uses, then renders the result as a sortable, filterable admin grid. The plugin keeps owning the builder and the per-campaign deep dive; the table view owns the cross-campaign audit marketing, growth and content all needed.