It reads the Heap Analytics WordPress plugin's options (app ID, role exclusion list, template toggles), the wp_posts table for post_type and post_status, and the wp_users / wp_usermeta tables for role-based exclusion analysis. No Heap server-side API token is required.

No. SleekView Charts reports on what the WordPress plugin is doing locally: snippet coverage, exclusion configuration, and post-type reach. The auto-captured events and Heap definitions stay in the Heap project UI, which is where they belong.

Yes. The table view and chart view share the same dataset, so a filter for one post type or one excluded role applies to both. Analytics leads pivot between row-level inspection and chart summaries without rebuilding the filter.

Yes. Group by the option-modified timestamp with an Area or Line card and a Count aggregation to see when the Heap plugin options were edited. Useful for tying a sudden gap in Heap data back to a real WordPress configuration change.

Yes. The plugin app ID is part of the option set the dashboard tracks. An unexpected change to the app ID, surfaced by the configuration-changes-over-time chart, is the clearest signal that the wrong environment is feeding the Heap project.

No. SleekView Charts reads existing options, posts, and user metadata and never writes to the Heap plugin's settings. The snippet keeps rendering on the same hooks, with no change to capture behaviour, identity, or session handling.

Yes. Each subsite stores its own Heap app ID and exclusion rules in its own options table, and SleekView respects that boundary. A network admin can build per-subsite dashboards or a network-level view scoped to specific blog IDs.

Yes. Any filtered set behind a chart card exports as CSV with the same columns the table view would show. Agencies and internal analytics teams use this to attach a coverage audit to a Heap implementation review or a quarterly client deliverable.