Yes. When an editor attaches a Kit form to a post or page the plugin writes _wp_convertkit_settings to wp_postmeta with the form_id and display position. SleekView reads that postmeta directly, so the dashboard reflects the same attachment data the plugin uses at page render time.

Yes. The form_id stored in _wp_convertkit_settings is a direct chart dimension. Group by form_id on a Donut or Bar card to see per-form coverage across the WordPress site, useful for spotting forms that are attached everywhere and forms that should be promoted to more posts and pages.

Yes. Joining wp_postmeta to wp_posts on post_id exposes post_type as a chart dimension. A Bar card on post_type shows whether Kit forms live mostly on standard posts, pages, or a custom post type, which is the single most useful breakdown for content audits and growth strategy discussions.

Yes. Joining wp_term_relationships and wp_terms exposes the taxonomy terms each post belongs to. A Bar card on term_name shows per-category Kit coverage, useful for confirming the highest-traffic content categories on the site carry the right Kit forms attached at publish time.

No. SleekView reads the local postmeta and the cached forms option that the Kit plugin maintains. No additional API calls are made to the ConvertKit central platform, which keeps the dashboard fast and avoids consuming any Kit API rate limits even on sites with frequent dashboard refreshes.

Yes. Aggregations run on the meta_key index on wp_postmeta and the post_type index on wp_posts, so large WordPress sites with tens of thousands of posts render charts in seconds. Pagination on detail drill-downs keeps the dashboard responsive on the largest content-heavy WordPress installs.

Yes. Each chart card exposes the underlying rows for CSV export with the active filters applied. Useful for handing the content team a per-post coverage list to action, or for sharing with marketing during a quarterly Kit audit that reconciles WordPress coverage with the Kit central form data.

Yes. SleekView reads the existing _wp_convertkit_settings postmeta key, so as long as the Kit plugin keeps writing that key the dashboard continues to render. If a major plugin update renames the key the dataset is updated once and every card on the dashboard picks up the change automatically.