ConvertKit Pro is a thin integration plugin: forms, sequences, and tag mappings are pulled from the ConvertKit API and cached in wp_options under keys like convertkit_settings and convertkit_forms. Recent subscriber events surface in wp_postmeta on the posts that captured them, and per-form opt-in logs live in wp_options transients. The default settings screen lists forms and a global API key, but doesn't render any of this as a row-level workspace.

Auditing which posts drive opt-ins to which form, which tags are mapped to which restricted content, or which cached subscriber records are stale needs SQL today. The plugin's own UI tops out at a global settings page and a per-post meta box. Cross-post and cross-form questions, like "which posts are still mapped to a tag that was deleted in ConvertKit", aren't surfaced anywhere.

SleekView reads the wp_options entries, the per-post _ck_form_id and _ck_tag_id postmeta, and joins them to wp_posts so every form mapping renders as one filterable, inline-editable row. Bulk re-mapping, stale-tag detection, and per-form attribution all happen in the same view, and writes route through the plugin's own settings API so the next API sync stays consistent.

ConvertKit Pro is intentionally a thin layer: the real subscriber list, sequences, and broadcasts live in ConvertKit (Kit) itself, and the WordPress plugin's job is to map posts to forms and tags so opt-ins flow back upstream. That smaller surface area makes the plugin easy to reason about, but it also means there is no native screen that aggregates the mappings across hundreds of posts. Content teams running a serious newsletter end up with dozens of forms, dozens of tags, and hundreds of posts referencing them, and the only way to audit those mappings today is SQL against wp_postmeta or a CSV export.

SleekView turns that audit into a row-level workspace built on the data the plugin already caches, so stale tags surface immediately, attribution by form becomes a saved view, and bulk re-mapping after a content refresh takes one action instead of a hundred. For teams treating the WordPress site as a top-of-funnel for ConvertKit, that consolidation is what keeps the mapping layer trustworthy as the content library grows.