It reads the Mixpanel WordPress plugin's options (project token, event toggles, user-property mappings), the wp_posts table for post_type and post_status, and the option revision history. No Mixpanel service-account token is required for the dashboard itself.

No. SleekView Charts reports on what the WordPress plugin is doing locally: which events are enabled, which hooks they fire on, and how the configuration has changed. The actual event counts and funnel analysis stay in Mixpanel, which is where they belong.

Yes. The table view and chart view share the same dataset, so a filter for one event name, one hook source, or one post type 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 Mixpanel plugin options were edited. Useful for tying a missing event in Mixpanel back to a real WordPress configuration change.

Yes. The Mixpanel plugin maps WooCommerce hooks (purchase, add to cart, checkout) to Mixpanel events, and those mappings are part of the plugin options. SleekView Charts reads them and lets you build a WooCommerce-specific event coverage dashboard.

No. SleekView Charts paginates against existing post and option indexes and never loads more rows than the visible page. The Mixpanel plugin keeps tracking events exactly as before, on the same hooks, with no additional front-end request.

Yes. Each subsite stores its own Mixpanel project token and event mappings 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 shows. Implementation engineers and growth teams use it to attach a tracking-plan audit to a Mixpanel report or a sprint review.