SUMO List Builder registers each popup as a custom post type and stores captured subscribers in a plugin table with email, name, source URL, popup post ID and capture timestamp. Per-popup view and conversion counts live as postmeta on the popup CPT row. The default admin shows a per-popup stats panel and a flat, paginated subscribers list.

That layout works for confirming a single popup is live. It scales poorly the moment marketing wants the cross-popup picture or compliance needs a filtered export by capture date. Sorting subscribers by popup, filtering by source page, or surfacing a campaign cohort each requires manual SQL or repeated screen flips.

SleekView reads the SUMO subscribers table and joins the popup CPT for the popup name. The subscriber view shows email, popup, source page, capture date and any join into the CPT meta in the same row, sortable and filterable. Compliance pulls a date-bounded cohort for a data-subject request in seconds. Marketing sorts subscribers by source URL to find the page actually driving signups. Same SUMO data, a workspace instead of a paginated list.

SUMO List Builder collects clean, well-structured subscriber rows with everything a marketing or compliance workflow needs: email, popup, source URL, capture date. The default admin renders that data as a paginated screen and a per-popup stats panel, which scales poorly across dozens of popups and campaigns. A list manager who wants to find the top source page across all popups, a compliance lead who needs a date-bounded cohort, an auditor who wants to retire zero-conversion popups each end up paging through the same flat list.

The data is one table join away from the answer. SleekView surfaces it as a workspace where each role lands on a saved view scoped to their job, sorts and filters the rows they actually own, and exports a cohort as the deliverable. Same SUMO tables, the right surface to read them.