The Kit for WordPress plugin (the rebrand of ConvertKit) authenticates against the Kit API and caches forms, sequences, tag IDs, and broadcast metadata in wp_options under keys like convertkit_settings and convertkit_forms. Per-post mappings live in wp_postmeta (_ck_form_id, _ck_sequence_id, _ck_tag_id), and a local sync log tracks recent opt-in pushes so transient failures can be retried.

The plugin's default UI shows a settings page, a per-post meta box, and a Gutenberg block for inline forms. There is no aggregated view that lists which posts map to which form or sequence, which mappings point at items deleted upstream, or which opt-in events stalled. Cross-cutting questions, like "top posts by 30-day opt-in count grouped by mapped sequence", live in SQL only.

SleekView joins the cached form, sequence, and tag lists in wp_options with the per-post meta keys and the sync log, then attaches it all to wp_posts. Stale mappings, top-performing forms, and retry queues become first-class views, and writes route through the plugin's own update path so the local cache and the Kit account stay consistent on the next API sync.

Kit's WordPress plugin makes a sensible architectural choice: form, sequence, and tag mappings each live in their own postmeta key so future product changes can evolve independently. That separation is fine for one post but expensive for an editorial team managing a library of hundreds. Every audit means opening three meta boxes per post, or running ad-hoc SQL that joins three meta keys back to the cached references in wp_options.

The plugin's settings screen tops out at a global API key and a list of cached forms because the install wizard doesn't need more; the operational reality of a serious newsletter does. SleekView joins the three meta keys, the cached references, and the local sync log into one row-level workspace, with inline edits routing through the plugin's update hooks so the next API sync stays consistent. For teams that treat Kit as the revenue layer and WordPress as the top-of-funnel, that workspace is what keeps the mapping layer auditable as the archive grows past the point where per-post meta boxes can be inspected by hand.