Directly from wp_posts joined to wp_postmeta on the _fl_builder_data meta key. SleekView parses the BB JSON blob and exposes the list of PowerPack module slugs (pp-info-list, pp-pricing-table, and so on) as a real column, so chart cards can group by them like any other field.

Yes. Group a Donut or Bar card by the parsed module slug and SleekView ranks PowerPack modules by how often they appear across pages. Filter further to a single module when an audit focuses on, for example, every page using the pp-pricing-table module before a pricing update lands.

Group an Area or Line card by post_modified truncated to week or month, aggregated by Count, scoped to pages that carry PowerPack modules. The curve shows when those pages are being touched, useful for tracking campaign cadence and stretches of zero activity that mark stale layouts.

Yes. View-level filters such as post type, author, status, date range, and parsed PowerPack module slug 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 parsing the _fl_builder_data JSON to extract module slugs. SleekView caches the parsed module list per post so subsequent chart renders hit a lightweight indexed column instead of re-parsing the BB blob, even when the postmeta row weighs hundreds of kilobytes.

Yes. The parsed module column lists every module slug found in _fl_builder_data, native BB modules and PowerPack modules side by side. Filter to pages that contain both pp-* and core fl-* modules to map the overlap, useful before swapping a PowerPack module for a core equivalent.

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 pp-* module) and open the row in the BB editor from there. Inline edits route through the standard WordPress update path as usual.

Neither Beaver Builder nor PowerPack ships a reporting screen for module usage, so there is nothing to replace. SleekView Charts adds a reporting surface on top of the postmeta the BB editor already writes, so both plugins keep owning the editor and the chart view owns the cross-site summarisation.