CampaignHQ is a cloud email platform whose WordPress plugin bridges forms and contacts to the SaaS. A serialized settings array in wp_options holds the API key, default list ID and opt-in default. Per-form list mappings sit on postmeta when the supported form-plugin integrations are wired up. Sync timestamps and webhook health flags are written into options on each round-trip with the cloud.

The default plugin admin focuses on connecting the account and surfacing a connection status pill. It does not show how many forms feed CampaignHQ lists, which list is the most-fed across the site, whether opt-in default is on for every blog of a multisite, or whether the sync has been stale for hours.

SleekView reads the bridge postmeta and surfaces every mapping as one row. Source form, source form plugin, target CampaignHQ list, opt-in default and last edit sit as real columns. Sort by target list to find the lists carrying the work, filter to non-default consent for a legal review, bulk-repoint bridges from a retired list to its replacement.

CampaignHQ's plugin is a thin SaaS connector, which is the right architecture for a cloud-first email platform. The trade-off is that the WP-side surface, bridges, consent strings, sync state, becomes invisible. Marketing leads who want a one-screen view of "are our bridges healthy, are consent strings current, is the sync flowing" land instead on a connection status pill and a form-by-form audit.

SleekView treats those small but important fields as a table dataset, so coverage, list usage and sync health become one sortable row per bridge. Same data the plugin already writes, organised as a list instead of a tab tour.