From wp_posts.post_content parsed with WordPress's parse_blocks() API for block usage, and from the kadence_form custom post type for Pro form definitions. SleekView exposes Pro block names and form rows as real columns, so chart cards can group by them like any other field.

Yes. Group a Donut or Bar card by the parsed block name and SleekView ranks Pro Kadence blocks by how often they appear across the site. Filter further to a single block when an audit focuses on, for example, every page using kadence/advancedform before a form update lands.

Yes. SleekView reads the kadence_form custom post type as a real data source. A Number card counts active forms, a Bar card ranks forms by usage (joined to posts that embed the form ID), and a Donut card splits form rows by author or status for ownership audits.

Group an Area or Line card by post_modified truncated to week or month, aggregated by Count, scoped to posts that carry Pro kadence/* blocks. The curve shows when those pages are being touched, useful for tracking campaign cadence and stretches of zero activity.

Yes. View-level filters such as post type, author, status, date range, and parsed Pro block name apply to every chart card on the dashboard. One saved configuration drives both the audit table and the chart view, so reporting and housekeeping stay aligned.

Yes. The expensive operation is calling parse_blocks() on every post_content. SleekView caches the parsed block name list per post so subsequent chart renders hit a lightweight indexed column instead of re-parsing the block markup, even on sites with tens of thousands of posts.

Charts are read-only summaries by design. To act on a chart insight, switch to the audit table filtered to the same slice (for example, every page using a specific Pro kadence/* block) and open the row in the block editor from there. Inline edits route through the standard WordPress update path as usual.

Kadence Blocks Pro does not ship a reporting screen for block or form usage, so there is nothing to replace. SleekView Charts adds a reporting surface on top of the post_content markup and kadence_form CPT Kadence already writes, so the plugin keeps owning the editor and the chart view owns the summarisation.