AcyMailing is one of the few WordPress newsletter plugins that owns its data with a real schema instead of stuffing rows into wp_options. Subscribers live in wp_acym_user, lists in wp_acym_list, memberships in wp_acym_user_has_list, campaigns in wp_acym_mail, the queue in wp_acym_queue, and per-recipient history in wp_acym_history. The default admin presents one table at a time.

SleekView Charts treats those tables as chart sources. A Number card pins total confirmed subscribers. A Pie shows the list-membership mix. A Bar ranks lists by subscriber count. An Area card plots send history per day so campaign cadence and delivery dips read in one curve. The queue gets its own card for retry-heavy recipients so SMTP rejection rates become a one-glance metric.

The dashboard joins across tables the way the schema was designed to be queried. A subscribers-by-list Pie uses wp_acym_user_has_list; a queue-health Bar uses retry counts on wp_acym_queue; a send-history Area reads wp_acym_history by date. None of that is novel data; it is the schema finally getting a query layer that matches its shape.

AcyMailing's design choice (own the data with a real schema) unlocks segmentation, send history, and queue management at scales that option-driven plugins cannot reach. The cost is that the default UI presents one table at a time, which makes the schema feel smaller than it is. The most useful operations are joins.

Subscribers in the main list who never opened the last campaign is a join between membership and history. Recipients with three or more retries on the queue is a sort on the queue table. Subscribers with a custom field equal to a specific value is a join through the user-has-field table.

Charts treat the schema as a query target because that is what the schema was built for. The result is fewer admin clicks for newsletter operators, faster turnaround on segment audits, and a single dashboard that pulls every related table together rather than asking the operator to assemble the picture from five separate screens.