SleekView for FullStory
Read the FullStory plugin's org ID, excluded role list, and template settings directly. Show every published URL with recording status, excluded role, post type, and the last setting change in one sortable WP Admin table.
♾️ Lifetime License available
An org ID in a settings field is not a list of recorded pages
The FullStory WordPress plugin stores an org ID, a list of WordPress roles to exclude from recording, and a set of toggles for which front-end templates run the snippet. The settings screen confirms the plugin is connected. It cannot tell you which published URLs the recorder reaches today, which excluded role applies on each one, or which templates were quietly opted out.
SleekView turns the same options and exclusion lists into a row-level view. Each published post and page is a row with recording status, excluded role, post type, template, and the last option-modified timestamp. Sort by status, filter to one role, or scope to one post type and the table updates without leaving WP Admin.
The same dataset powers the SleekView Charts rollout dashboard for FullStory, so filters carry between row-level audit and chart-level coverage on one shared source.
Workflow
How SleekView reads FullStory plugin data
Pick the source
wp_posts and the user role map as one joinable source.
Compose the column set
Save and scope the view
Filter, sort, and export
Sample columns
A typical FullStory coverage table
wp_posts. Each published URL gets a row with recording status, excluded role, and the template it ran through.
wp_options (FullStory settings) + wp_posts + wp_usermeta
| URL | Post type | Recording | Excluded role | Template | Last change |
|---|---|---|---|---|---|
| /checkout/ | page | Live | — | checkout.php | Apr 25 |
| /signup/ | page | Live | — | default | Apr 23 |
| /account/ | page | Excluded | subscriber | default | Apr 21 |
| /admin-preview/ | page | Excluded | editor | preview.php | Apr 18 |
| /blog/funnel-tips/ | post | Live | — | single.php | Apr 16 |
Comparison
Default FullStory plugin settings vs SleekView
Default FullStory plugin settings
- Settings tab shows the org ID, not the list of recorded URLs
- Role exclusions are easy to misconfigure and not visible per page
- Template-level opt-outs are not surfaced anywhere as a row-level list
- No saved per-role view for product, privacy, or agency reviewers
- No way to export the filtered rollout set without writing custom SQL
SleekView
- Read directly from the FullStory plugin options and excluded role list
- Per-page recording status, excluded role, and template in one row
- Saved views per WordPress role for product, privacy, and client access
- Shared filters with the SleekView Charts rollout dashboard
- CSV export of the filtered rollout set without leaving WP Admin
Features
What SleekView gives you for FullStory
Rollout as a list
Build a product view that shows checkout, signup, and onboarding URLs alongside their recording status. The whole rollout becomes a list, not a settings tab.
Precise exclusion filters
Filter to one excluded role or one template and confirm the privacy posture matches policy on every row. Save the filter as a quarterly review view your team reuses.
Same data, two surfaces
The table view and the SleekView Charts rollout dashboard read the same FullStory plugin options. A filter applied to one applies to the other without a rebuild.
Audience
Who uses SleekView for FullStory
Product analytics teams
Filter the table to checkout, signup, or onboarding URLs and confirm every step is being recorded before drawing funnel conclusions from FullStory session data.
Privacy reviewers
Sort by excluded role and confirm admin, editor, and contributor accounts are correctly opted out on member-only templates before the next audit cycle.
Agency leads
Filter to one client's post types and export the rollout list to CSV. The monthly client report ships with coverage as a real list, not a screenshot of the settings tab.
The bigger picture
Why session replay needs a recorded-pages list
Session replay tools live or die on coverage. A FullStory account with the wrong page set recorded is worse than no FullStory at all, because the product team builds confidence in a funnel view that quietly misses half the relevant traffic. The WordPress plugin keeps installation simple, which is correct, and keeps coverage invisible, which is the part that breaks in long-running implementations.
SleekView turns the same plugin options and exclusion lists into a table where every published URL is a row, with recording status, excluded role, and template in plain view. Same data, same WordPress hooks, but a list a product team, an agency, or a privacy reviewer can actually point to.
Questions
Common questions about SleekView for FullStory
It reads the FullStory plugin's options (org ID, excluded role list, template toggles), the wp_posts table for post_type and post_status, and wp_users / wp_usermeta for role analysis. No FullStory API token is required for the table view itself.
No. SleekView reports on what the WordPress plugin is doing locally: snippet coverage, exclusion configuration, and template reach. The recorded sessions stay in FullStory's UI, which is where you analyse them once the coverage list is verified.
Yes. If your install adds custom keys for template-level opt-outs, SleekView lists them in the column picker so the table can show those fields alongside the FullStory plugin's own template toggles.
Yes. The table view and the SleekView Charts rollout dashboard share one dataset. A filter for one post type, one excluded role, or one template applies to both surfaces, so you can pivot between row-level inspection and chart summaries.
Inline edits in the table write to the same WordPress options and meta the FullStory plugin reads, so the next request honours the change. Recording sampling, identity, and session handling are untouched, since SleekView never writes to the FullStory account itself.
No. It is an additional admin surface on top of the existing plugin. The FullStory settings tab stays where it is, and the snippet keeps rendering on the same hooks, with no change to recorded session behaviour.
Yes. Each subsite stores its own FullStory org ID and exclusion rules, and SleekView respects that boundary. Network admins can build per-subsite tables or a network view scoped to specific blog IDs.
Yes. Any filtered set in the table exports to CSV with the visible columns. Agencies and internal teams use the export to attach a coverage list to a quarterly client deliverable or a privacy review.
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