SleekView for Flying Analytics
SleekView reads the flying_analytics_* options, the cached self-hosted script metadata and the optional pageview log, then renders every recorded pageview as a column-perfect table with tracker type, hostname, template and timestamp.
♾️ Lifetime License available
Flying Analytics ships the tag, the table reads each pageview as a row
Flying Analytics serves Google Analytics, GA4, Matomo, Plausible or Cloudflare Insights from the local hostname, configured through flying_analytics_* options. The settings screen has a tracker dropdown, an ID field and a few advanced flags. There is no per-page list of where the self-hosted tag actually fired and no admin surface for the optional pageview log the front-end script can ship into a custom table.
SleekView reads the options, the cached self-hosted script metadata and the optional pageview log, then renders each recorded pageview as a row. Tracker type, hostname, template, post type and timestamp become first-class columns with sort, filter and inline action. A performance engineer can scope the table to pageviews served from a third-party hostname (the regression signal), an editor can spot which templates drive analytics volume without learning the third-party UI.
Flying Analytics continues to deliver the tracker exactly as before. SleekView is read-only against the same options and the pageview log, so the third-party request path on visitor sessions is untouched.
Workflow
How SleekView surfaces Flying Analytics data
Point at the tag configuration
Compose the columns
Filter and sort like a database
Save and gate the view
Sample columns
A typical Flying Analytics pageview audit view
wp_319_options (flying_analytics_*) + cached script metadata + optional pageview log
| URL | Tracker | Hostname | Template | Post type | Recorded |
|---|---|---|---|---|---|
| / | GA4 | local | front-page.php | page | 2026-05-16 09:14 |
| /blog/why-speed-matters/ | GA4 | local | single.php | post | 2026-05-16 09:13 |
| /shop/ | GA4 | local | archive-product.php | page | 2026-05-16 09:12 |
| /landing/spring-2026/ | GA4 | www.google-analytics.com | page-landing.php | page | 2026-05-16 09:11 |
| /about/ | GA4 | local | page.php | page | 2026-05-16 09:10 |
Comparison
Default Flying Analytics admin vs SleekView
Default Flying Analytics admin
- Settings screen shows tracker type and ID with no per-page list
- No way to confirm the self-hosted hostname served every pageview
- Pageview event log (if enabled) lives in a custom table with no admin surface
- Template and post-type joins require manual SQL against wp_posts
- No saved views per role for engineers, editors or agency support
SleekView
- Recorded pageviews rendered as a real table with tracker, hostname and template columns
- Filter to pageviews served from a third-party hostname to catch CDN regressions
- Sort by recorded_at to find sudden spikes or quiet windows
- Saved views per role: engineer audit, editor traffic review, agency triage
- Same dataset the chart view reads, so table and dashboard stay in sync
Features
What SleekView gives you for Flying Analytics
Tag delivery as real columns
URL, tracker, hostname, template and recorded timestamp rendered directly from the flying_analytics_* options and the pageview log, not as a single status indicator.
Real sort, filter and inline action
Sort by recorded_at, filter by hostname to surface third-party regressions, and open the affected template from a row action.
Role-scoped saved views
Save views per role and embed them on frontend pages so editors read pageview volume without learning the third-party tracker UI.
Audience
Who uses SleekView for Flying Analytics
Performance engineers
Filter pageviews to a third-party hostname to catch a CDN rule that silently falls back to remote tag delivery on a single template before it ages out.
Editorial leads
Use the per-template and per-URL table as a lightweight analytics surface inside WP Admin, scoped to the post types the team cares about.
Agency support
Give clients a read-only table of self-hosted tag status and recent pageviews so they self-serve obvious questions without opening a ticket.
The bigger picture
Self-hosted tag delivery is data, not a setting
Flying Analytics is small on purpose: pick a tracker, paste an ID, ship one less third-party request. The cost of that minimalism is that the admin surface tells you nothing past install day. Whether the self-hosted hostname still serves every pageview.
Whether a CDN rule regression silently falls back on a single template. Which templates drive analytics volume on weeks the third-party UI is offline. SleekView treats the options and the optional pageview log as the structured data they already are.
Pageviews become rows with tracker, hostname, template and timestamp, sortable and filterable, with inline action to open the affected template. The plugin keeps shipping the tag exactly as before, SleekView adds the reading layer the team can actually share and scope per role.
Questions
Common questions about SleekView for Flying Analytics
No. Flying Analytics still owns tag delivery. SleekView is a flexible reading layer on top of the same options and the optional pageview log for audit tables the plugin's settings screen does not lay out.
Only for per-pageview rows. The self-hosted hostname coverage and tracker-type columns work off the options and cached script metadata with zero front-end instrumentation.
No. Full analytics still happen in the third-party destination. SleekView only surfaces what is visible at the WordPress layer, which is enough to confirm self-hosted delivery and give editors a lightweight overview.
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.
Yes. Tracker type is a primary column, so every saved view can filter for UA, GA4, Matomo, Plausible or Cloudflare Insights without writing SQL.
Yes. Saved table views support role-based visibility so engineers, agency staff and editors each see only the views the admin allows.
Yes. Any saved view can be embedded on a frontend page with role-based access, so stakeholders read pageview behaviour without entering WP Admin.
Yes. Each subsite has its own flying_analytics_* options and its own pageview log if enabled, and SleekView respects that scope. A network sees one audit per subsite.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout