MailWizz itself is a self-hosted PHP email marketing app with its own database (lists like mw_list, subscribers in mw_list_subscriber). The WordPress integration plugin is a bridge: it stores the MailWizz API URL, public/private key, and list mappings in wp_options (under keys like mailwizz_integration_settings) and writes signup logs to a small log table or rolling option record on the WordPress side. The canonical subscriber list stays inside MailWizz.

That makes the WordPress admin screens feel slim. The default settings page handles credentials and one form's list mapping at a time; the signup log is functional but flat. Cross-form questions like "which signups never reached the new MailWizz list this week" are not a one-click view. Per-form mapping audits after a redesign require opening each form separately.

SleekView reads the connector's options and log entries directly. List mappings render as one table you can scan in seconds; signup pushes render as a queue with status and API response. Bulk retry calls the plugin's own push function so the API behaviour matches a fresh signup, just executed in batch.

MailWizz Integration is exactly what it says on the tin: an API bridge between WordPress signup forms and a self-hosted MailWizz install. The architecture is correct, but the WordPress side stays minimal by design. A handful of options, a thin log, a few hooks, and that is the whole surface.

Operators only think about it when something stops working. A list got renamed and the old list_uid is still mapped, the API key rotated, a MailWizz upgrade introduced a timeout, signups quietly piled up unrecognised. The default admin screen makes those issues hard to see because it shows one form at a time.

SleekView pulls the mappings and the log into one workspace so the cross-form picture is obvious. That turns the silent middle of the integration into something operators can actually watch.