BigMailer is a transactional and bulk email platform whose WordPress plugin acts as a thin connector. A serialized settings array in wp_options holds the API key, brand ID and the default opt-in flag. Per-form bridges to BigMailer lists store their state on the source form's postmeta when the supported form-plugin integration is enabled. Sync timestamps and webhook health land in options alongside the credentials.

The default plugin admin focuses on connecting the BigMailer brand and toggling the default opt-in. It does not surface how many forms feed BigMailer lists, which list is the most-fed across the site, whether the sync is current, or whether the consent strings on each form match the latest legal-approved copy.

SleekView reads the bridge postmeta and surfaces every mapping as one row. Source form, source form plugin, target BigMailer list, consent override 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.

BigMailer is a SaaS-first email platform whose WordPress plugin connects forms and stores to the cloud. The trade-off of that thin architecture is that the WP-side surface, bridges, consent strings, sync state, becomes invisible. The team that owns lead capture is the team most likely to want a one-screen view of "are we collecting where we should be, is the integration healthy, are consent strings current".

SleekView treats those small but important fields as a table dataset and renders the coverage as one row per bridge. The data is already in wp_options and wp_postmeta, the table surface makes it operational instead of buried in a settings tab.