No. SleekView reads the Snap pixel configuration stored in wp_options and the per-page event meta. It shows what the plugin is set to fire, not what Snap Ads Manager received. For impression and conversion data you still use Snap Ads Manager, which SleekView can complement with the WordPress-side configuration story.

Yes, when the plugin stores them. Some Snap Pixel for WordPress builds add server-side CAPI flags to the events configuration. SleekView reads whichever keys live in snap_pixel_events, so a Pie card can split client-side and server-side events when the option array carries both.

Yes. WooCommerce-specific builds of the plugin still write to wp_options under snap_pixel_* keys and add WooCommerce-specific events (PURCHASE, ADD_CART) plus per-product meta. SleekView reads both flavors without configuration changes, and the chart definitions stay portable.

Yes. Page-level filters can scope every card to a post_parent, a category, or a custom taxonomy. Useful when a publisher wants to verify that all product pages in a single collection have the right Snap event override applied before a campaign launches.

SleekView reads the live wp_options and wp_postmeta rows on dashboard load, so a settings change or new event override appears immediately on the next refresh. Heavier aggregates can opt into a configurable cache, but the default behaviour is live reads against the rows the plugin writes.

Yes. Saved chart views support role-based visibility, so ad ops, store managers, and external partners see only the dashboards you allow. Role scoping is per view, not per row, so the underlying audit trail stays intact for compliance reviews.

Yes. Any saved chart view can be embedded on a frontend page with role-based access, useful for an internal team page or a client portal where the dashboard needs to live outside WP Admin behind a login of its own.

No. The plugin reads its option key once per request to inject the pixel snippet; SleekView only queries when the dashboard renders. The two systems share the same rows but the frontend pixel injection path is untouched by anything SleekView Charts does.