SleekView for Mouseflow
SleekView reads the Mouseflow plugin options on every site of a multisite and renders website-ID coverage, excluded-role policy and consent-mode config as a sortable, filterable WP Admin table.
♾️ Lifetime License available
Replays live at Mouseflow. Snippet governance lives here.
Mouseflow's WordPress integrations exist to inject the Mouseflow session-recording snippet keyed by a Mouseflow website ID. The plugin handles the snippet, the excluded-roles list and a consent flag that decides whether the snippet fires before opt-in. The actual session replays, heatmaps, funnels and form analytics all live in the Mouseflow dashboard and are queried there.
SleekView reads the WordPress options the integration writes, across one site or every site in a multisite, and renders one row per site with website ID, excluded roles, snippet placement, consent flag and the option_updated timestamp as columns. Sort by missing website ID to find every site where Mouseflow quietly stopped recording. Filter to consent off for a privacy compliance pass. Search across role names to confirm internal staff is filtered out of replays.
Because the data lives in standard WordPress options, the table works on a single site, a multisite network and an agency fleet managed from a central admin. Inline edits go through update_option, so changes are picked up by the Mouseflow integration on the next page load with no extra cache to clear.
Workflow
From Mouseflow plugin options to a real audit grid
Read the options
Build the columns you actually want
Save audit views
Edit inline and export
Sample columns
A typical Mouseflow config table
wp_options (Mouseflow plugin)
| Site | Website ID | Consent | Excluded roles | Placement | Status |
|---|---|---|---|---|---|
| main.example.com | a1b2c3d4-e5f6 | Required | administrator, editor | head | Compliant |
| shop.example.com | f7g8h9i0-j1k2 | Off | administrator | head | Pre-consent |
| blog.example.com | — | — | — | — | No recording |
| docs.example.com | l3m4n5o6-p7q8 | Required | administrator, editor, author | footer | Compliant |
| events.example.com | r9s0t1u2-v3w4 | Required | administrator | head | Staff not filtered |
Comparison
Default Mouseflow plugin admin vs SleekView
Default Mouseflow plugin
- Settings screen is one site at a time, no aggregate view of coverage
- No sortable list of sites by missing website ID or consent flag
- Excluded-role config hidden inside a checkbox group per site
- Multisite admins click through every site to confirm the snippet fires
- No way to share a read-only config snapshot outside the WP admin
SleekView
- One sortable table for every site's Mouseflow config
- Filter by missing website ID, consent off or stale option_updated
- Inline edits go through update_option, picked up on next page load
- Saved audit views shared per role for site owners and privacy officers
- Export filtered slices to CSV for compliance evidence
Features
What SleekView gives you for Mouseflow
Every site's Mouseflow config in one grid
Stop opening the Mouseflow settings page on twenty sites. SleekView reads the plugin options across the network and lists website ID, consent flag and excluded roles side by side.
Filter by what compliance asks
Sort by missing website ID, filter to consent off, or search role names. The exact list a DPIA cycle needs is one saved view, not a manual click-through.
Inline edits across sites
Flip the consent flag on, add a role to the excluded list or move the snippet to footer from the same row. update_option fires and the Mouseflow plugin picks the change up on the next page load.
Audience
Who uses SleekView for Mouseflow
Privacy officers
Filter to consent off before each DPIA cycle. The remediation list is a sorted table, not a screenshot from twenty Mouseflow settings screens.
Agency leads
Audit Mouseflow website-ID coverage across the client portfolio in one view. Spot the sites where a theme update wiped the snippet and ship a fix the same day.
Multisite admins
Group sites by excluded roles to confirm internal staff is filtered out of replays, instead of clicking through one site at a time before each quarterly UX research cycle.
The bigger picture
Why session replay tools still need a WordPress-side table
Mouseflow lives at its own service, where session replays, funnels, form analytics and friction events get rendered for product and UX teams. The WordPress plugin's job is the smallest part of the system: inject the snippet, exclude the right roles, decide whether to fire before consent. Small surface, large governance impact.
A single missing website ID means recordings stop. A single consent flag flipped to false means recordings ship before opt-in, and product teams build research on data that should never have existed. SleekView turns those scattered options into one table: website IDs in a column, consent flags filterable, excluded roles searchable, last-touched dates sortable.
Same plugin, same options, but a query surface privacy officers and agency leads can point quarterly reviews at without clicking through every site.
Questions
Common questions about SleekView for Mouseflow
Only the WordPress options the Mouseflow plugin writes: website ID, excluded roles, snippet placement, consent flag and the option_updated timestamp. No Mouseflow API access is involved, because the plugin itself does not query Mouseflow.
 No. The Mouseflow plugin is a script-injection plugin. SleekView only reads the local WordPress options that decide whether and how the snippet fires. The replays, heatmaps and funnels stay at Mouseflow and are queried there.
 Yes. The table can be scoped to a single site or run across every site in a network, pulling each site's Mouseflow options in turn. That makes a multisite-wide Mouseflow config audit a single grid instead of a click-through of admin screens.
 Any plugin that stores its Mouseflow website ID and filtering rules in standard WordPress options is supported, including the common Mouseflow connectors. SleekView reads whatever options the plugin uses; the column set is configured per plugin so labels match what the admin sees.
 Yes. Common fields like the consent flag, excluded roles and snippet placement can be edited from the grid. The change goes through update_option exactly like the settings page would write it, so the Mouseflow plugin picks up the new value on the next page load.
 No. The plugin still owns snippet injection and per-site settings. SleekView gives admins, privacy officers and agency leads an aggregate audit surface that the per-site settings screen cannot offer, without touching how the snippet behaves.
 No. The grid reads WordPress options on demand inside the admin and has no role in the frontend snippet at all. Visitor-facing performance is identical to running the Mouseflow plugin on its own.
 Yes. Any filtered view exports to CSV with the active columns. Privacy and agency teams typically export the no-website-ID list or the consent-off list as a quarterly action plan.
 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