TinyLetter for WordPress is a lightweight bridge: it embeds the TinyLetter sign-up form, stores its configuration in wp_options under a plugin-prefixed key, and optionally logs local sign-up events as posts of a custom type with metadata in wp_postmeta. The plugin itself does not maintain a dedicated subscribers table because TinyLetter's authoritative store lives on the upstream service. What lives in WordPress is the embed config plus a local audit trail.

The default admin gives a single settings screen and (if local logging is enabled) a fixed list of recent sign-ups. Cross-cutting questions like "which pages drove the most sign-ups last month" or "which embeds get clicked but rarely complete" need either Google Analytics or manual SQL against wp_postmeta. Bulk re-tagging of locally logged sign-ups, per-embed performance comparison, and filtering by referrer all sit outside the default screens.

SleekView reads the plugin's CPT and joins wp_postmeta values into named columns so referrer URL, embed ID, IP hash, and submission timestamp all render inline. Saved views become per-embed performance reports and per-referrer cohorts, and inline edits route through the plugin's update hooks where they exist or fall back to direct postmeta writes with conflict detection.

TinyLetter for WordPress is intentionally minimal: it embeds a form and forwards submissions upstream, with optional local logging for auditing. That minimalism is a feature, but it leaves operators without a built-in workspace for the data the plugin does keep. The local log accumulates in wp_postmeta on a CPT, the embed config sits in wp_options, and questions like "which page produced the most verified sign-ups last quarter" or "which embed bounces most often" need queries that the default admin doesn't offer.

SleekView's joined view turns those questions into saved views without leaving WP Admin. Newsletter authors get a per-embed performance comparison without spinning up an analytics dashboard. Editorial ops gets a duplicate-cleanup workspace that runs through the plugin's own hooks.

Growth marketers get per-referrer attribution joining content URLs with sign-up dates. The data the plugin already stores becomes operationally useful, and the upstream TinyLetter service remains the authoritative subscriber list with no risky sync layer between them.