No. SleekView reads the PixelYourSite configuration stored in wp_options and the event custom post type. It shows what the plugin is set to fire, not what Meta or TikTok received downstream. For the network-side data, you still log into Ads Manager or use the Conversion API logs, which PixelYourSite can also store in wp_options for SleekView to read.

Yes. The pys_facebook_settings, pys_tiktok_settings, pys_pinterest_settings, and pys_google_settings option keys all share the same shape, so a single dashboard can mix cards across networks. A donut card can split active events by target pixel network using the events_pixels meta on each PixelYourSite event post.

Yes. Both versions write to the same pys_* option keys and the same events custom post type. Pro adds more event types and triggers (DTA, server events, dynamic remarketing), and SleekView reads those columns just like the free standard events. The dashboard configuration does not change between tiers.

Yes. PixelYourSite stores the server event flag on each event post when CAPI is enabled. A Pie card grouped on that flag splits client-side and server-side events for the same pixel, useful for verifying CAPI rollouts during audits or when migrating away from browser-only tracking.

SleekView reads the live wp_options rows and the event posts on dashboard load, so an event toggle or a new event post appears immediately. Heavier aggregates can opt into a configurable cache, but the default behaviour is live reads against the actual rows PixelYourSite writes to.

Yes. Saved chart views support role-based visibility, so ad ops, store managers, and external auditors see only the dashboards you allow. The role scoping happens at the view level, not at the data level, 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 its own login boundary.

No. PixelYourSite reads wp_options once per request to print its pixel snippets; SleekView only queries when the dashboard renders. The two systems read the same rows but the frontend pixel injection path is untouched by anything SleekView Charts does, even on busy stores.