Moosend Pro is a SaaS connector. It stores API tokens and form-to-list mappings in wp_options, keeps recent sync attempts in a small log table or option blob, and writes per-user moosend_member_id values to wp_usermeta. The footprint is intentionally light because the records of truth live in Moosend.

The default plugin screen shows whether the connection is healthy and which lists are wired up. It does not give a row-level view of which subscriber pushes landed, which failed, and what the payload contained. Bulk-resync of historical users to a different mailing list isn't a default action, and per-user mapping coverage isn't visible without custom queries against wp_usermeta.

SleekView reads the sync log directly, joins it to the WP user row through moosend_member_id, and pivots option-stored mappings into a navigable view. Failed pushes become a saved filter, payloads become inspectable cells, and bulk-resync routes through the plugin's send action so list memberships and tags stay consistent.

Moosend handles the sending and analytics, the connector plugin handles the WordPress-to-Moosend flow, and yet the operational questions land back in WordPress. Whether the contact submission landed, whether the right list received it, whether the custom-field payload was correctly mapped: all that depends on rows already sitting in the WordPress database, but the default plugin admin barely exposes them. SleekView turns the sync log and option-stored mappings into a workspace.

Failed pushes become a filter, payloads become inspectable cells, and bulk resync routes through the plugin's existing send action so rate limits stay honoured. For teams running broadcasts and lifecycle messages through Moosend on top of WordPress, the audit view is the difference between trusting the connector and rerunning it after every campaign.