Mailster stores subscribers in wp_mailster_subscribers with stats on sends, opens, clicks, and bounces aggregated per recipient. Lists, actions, and forms each live in their own tables, which gives Mailster a real CRM-style schema underneath. The default admin presents subscribers and campaigns on separate screens with default columns that are clicks-deep for the operational data marketers actually need. SleekView reads the schema and surfaces subscribers with status, list memberships, sent count, opens, clicks, and last activity in a single grid tuned to segment-building.

The grid stacks filters across status, lists, engagement, and bounce class to match Mailster's own segment logic. Build a high-engagement segment in seconds: status equals subscribed, opens greater than 10 in last 90 days, lists includes weekly. Build a list-cleanup segment: status equals hard bounce or last activity older than 180 days. Inline list moves route through Mailster's own helpers so segment counts stay accurate and any list-triggered automation fires normally.

Campaign-level stats live in a separate view that surfaces opens, clicks, unsubscribes, and revenue per send if Mailster is tracking it. Drill from a campaign row to the recipient list to find who clicked or who unsubscribed, which is the segment-building shortcut that follows naturally from a post-mortem. Custom subscriber fields registered through Mailster appear as additional columns and filters. Saved views replace repetitive segment work; export the filtered segment when feeding ads platforms or external tools, and keep the source segmentation inside WordPress where Mailster owns the data.

Email campaign performance is decided long before the send button: it is decided by the segment. A broadcast to the entire list usually underperforms a targeted send to engaged recent subscribers, and the operator who can build that targeted segment in 30 seconds will run more focused campaigns more often. Mailster has the schema (subscribers, lists, actions, custom fields, bounce class), but the default admin presents the data through screens optimized for managing the plugin rather than running campaigns.

SleekView treats the schema as what it is: a CRM-style data model that benefits from a fast, filterable grid where status, engagement, list membership, and custom fields combine freely into segments. The marketer running a campaign builds the segment in seconds. The growth lead audits list health weekly.

The support team finds the subscriber's full history when handling a ticket. Mailster keeps doing what it does well; the people running campaigns get a surface that matches how they think.