ConvertBox is fundamentally a SaaS funnel and lead capture tool. The WordPress plugin is a thin bridge: it writes the account UUID and global script flags to wp_options, registers an inline [convertbox] shortcode for hand-placed boxes and exposes a per-post toggle stored in postmeta to suppress ConvertBox on specific pages.

The plugin's settings screen surfaces the account UUID and a global on/off switch. It does not show which pages have ConvertBox suppressed, which posts embed a manual shortcode, which post types skew the exclusion list or how recently any of those decisions were touched. The data sits in wp_options, wp_postmeta and parsed post_content, but the cross-site coverage list is missing.

SleekView reads the ConvertBox WP-side data directly. Every post that suppresses the script or carries an inline shortcode appears as a row with post type, suppress flag, shortcode count and last modified date as real columns. Sort by last modified to find stale exclusions, filter to one post type for a coverage audit, bulk-clear suppress flags across a legacy section.

ConvertBox lives in the cloud, but the WordPress plugin is the gate that decides whether the script runs on any given page. A suppress flag set on a high-traffic post type breaks a campaign quietly. A stale inline shortcode renders a box that no longer matches the funnel strategy.

The default plugin admin shows the account connection, not the coverage shape. SleekView surfaces the WP-side footprint as a real table so growth marketers can see, at a glance, where ConvertBox is muted, where inline shortcodes are placed and how recently any of it was touched. The data is already in wp_options, wp_postmeta and post_content, the table layer turns it from per-page inspection into a site-wide list with bulk actions.