Campaigner for WP is a connector. It stores API credentials and form-to-list mappings in wp_options, keeps a small recent-events log either as a custom table or as an option blob, and writes per-user Campaigner contact ids to wp_usermeta. The platform of record (lists, segments, campaigns, analytics) lives in Campaigner.

The default plugin admin confirms the connection is healthy and shows the list-to-form mappings. It does not give a row-level view of which contact pushes landed, which failed, and what the payload contained. Per-form audit and bulk-resync of historical users aren't default capabilities, and per-user mapping coverage isn't surfaced without custom queries against wp_usermeta.

SleekView reads the sync log directly, joins it to WP users through the Campaigner id meta key, and pivots option-stored mappings into a navigable view. Failed pushes become a filterable cohort, payloads become inspectable cells, and bulk-resync routes through the plugin's push action so list memberships and registered hooks stay consistent.

Campaigner is one of the older email service providers and many accounts have decades of accumulated lists, segments, and integrations stitched together. WordPress sits in front of a lot of those accounts as the form-capture layer, and the connector handles the routing to lists. Over time mappings drift: lists get renamed, forms get retired, segments shift.

The default connector admin doesn't surface those drifts at row level, and the cost compounds quietly. A small fraction of submissions silently miss the right list every week, for months. SleekView turns the sync log and mappings into a workspace.

Failed pushes become a filter, mappings become a maintained view, and bulk resync routes through the plugin's existing push action so rate limits stay honoured. For agencies maintaining long-lived Campaigner setups, that audit layer is the difference between cleaning up once a quarter under deadline pressure and cleaning up incrementally every week.