The flying_analytics_* options, the cached self-hosted script metadata, the wp_posts table for template joins, and the optional pageview event log if the tag is configured to ship events into a custom WordPress table. No third-party API is involved.

Only for the time-series and pageviews-by-template cards. The tag-coverage KPI and tracker-type pie run off configuration and the cached script metadata, with zero event ingestion. Sites that want trends over time can wire the pageview hook into a small custom table that SleekView reads alongside the rest.

No. Flying Analytics still ships the third-party tracker payload to its own destination, and full analysis happens in that destination. SleekView Charts only surfaces what is visible at the WordPress layer, which is enough to confirm the self-hosted optimisation is working and to give editors a lightweight pageview overview without leaving WP Admin.

No. SleekView runs entirely in the admin and never alters the analytics request path. Front-end visitors keep getting the self-hosted tag exactly as Flying Analytics serves it, and the dashboard updates as posts and options change.

Yes. tracker_type is one of the primary columns, so every chart card accepts a filter for UA, GA4, Matomo, Plausible or Cloudflare Insights. Multisite networks where each subsite picks its own tracker get a clean per-tracker dashboard slice.

Yes, when the event log is enabled. Group by event_date with an Area or Line card and a Count aggregation to see pageviews per day or per week. Without the event log the configuration cards still report on coverage in real time.

Yes. Any filtered set behind a chart card exports as CSV with the same columns the underlying table view would show. Useful for sharing a regression snapshot or briefing a developer on the templates with unexpected pageview gaps.

Yes. Each subsite has its own flying_analytics_* options and its own event log if enabled, and SleekView respects that scope. A network sees one dashboard per subsite, matching how Flying Analytics itself behaves when activated network-wide.