phpList is one of the original open-source email applications, and the WordPress plugin is a thin signup bridge. It writes the phpList base URL, the REST login/password and the default list IDs into wp_options, and it stamps per-form list-routing meta on signup shortcodes and blocks. When the optional submission log is enabled, each handoff lands as a row keyed to form ID, list IDs and a submitted_at timestamp.

The default plugin admin handles credentials and one global list assignment. It does not show how many signup embeds exist across the site, which phpList lists are receiving most signups, which form-builder integration is doing the work, or when the bridge last fired. On a content site that runs five newsletters across different sections, that gap is felt at every editorial meeting.

SleekView Charts reads the phpList plugin's WP-side data directly. A Number card anchors total signups this week. A Pie splits signups by phpList list. A Bar ranks signup pages by capture volume. An Area trends signups per day so the editorial lead can see whether the new top-of-page form is actually paying off.

phpList is the long-standing open-source choice for organisations that want to keep their list off a SaaS, and the WordPress plugin is the visitor-facing front door for most of those installs. The trade-off is that the WP side of phpList has been a configuration screen, not a reporting one. A signup form that went missing during a redesign, a list that quietly stopped growing after a campaign ended, a confirmation flag flipped on staging and not on production: each of those questions lives in the plugin's option store and submission log, and a chart layer is what turns those numbers from latent data into a board-room-ready picture.

Same phpList WP-side data the runtime bridge already writes, organised so the editorial team, the marketing lead and the DPO can all see the shape of the program at once.