SleekView for Mouseflow Pro: site keys, funnels & exclusions as tables
Mouseflow recordings, heatmaps, and funnels live in Mouseflow's cloud while the WordPress plugin stores the site key, the form-tagging map, and per-post exclusions in wp_options and wp_postmeta. SleekView turns that configuration into one inventory of which pages send sessions.
♾️ Lifetime License available
Audit which Mouseflow exclusions and form tags are pinned to which pages
The Mouseflow WordPress plugin writes its site key, post-type allowlist, and form-tagging configuration to wp_options under mouseflow_settings. Per-post overrides save into wp_postmeta as _mouseflow_exclude and _mouseflow_form_tag. The settings screen exposes the global toggle and site key but no per-post inventory.
SleekView reads both the options row and every post carrying a _mouseflow_* override into one sortable grid. Exclusion state, attached form tag, and post type become real filterable columns. Marketing teams filter by form tag to verify which pages are tracked under which funnel; compliance verifies sensitive pages are excluded; consultants see the global site key next to the overrides.
Heatmaps, session recordings, funnel reports, and form analytics stay in Mouseflow's own dashboard. SleekView only manages the WordPress side: which page is in or out, which form tag is attached, and which override happened when.
Workflow
From Mouseflow postmeta to one funnel audit
Connect the Mouseflow data
mouseflow_settings from wp_options and every post carrying a _mouseflow_* key. Settings and overrides surface in one place.
Build the audit columns
Save scoped views
Inline edit and bulk update
update_post_meta and apply on the next page load.
Sample columns
A typical Mouseflow exclusion and form-tag inventory
wp_options (mouseflow_settings) + wp_postmeta (_mouseflow_exclude, _mouseflow_form_tag)
| Page | Post type | Tracking | Form tag | Consent gate | Last edited |
|---|---|---|---|---|---|
| /contact/ | page | On | contact_form | complianz | Apr 22 |
| /account/ | page | Excluded | - | complianz | Apr 04 |
| /checkout/billing/ | page | Blocked | - | complianz | Feb 11 |
| /landing/demo-request/ | page | On | demo_form | complianz | Apr 26 |
Comparison
Default Mouseflow Pro admin vs SleekView
Default Mouseflow Pro admin
- Settings screen shows site key and global toggle, no per-post override inventory
-
_mouseflow_excludeand_mouseflow_form_tagpostmeta are invisible from the dashboard - No way to filter pages by attached form tag or exclusion state
- Auditing the form-tag map per landing page requires opening each post
- Bulk-removing a deprecated form tag needs WP-CLI
SleekView
-
Inventory every
_mouseflow_*override as a sortable row - Filter by post type, exclusion state, form tag, or consent gate
- Sort by last edited to detect override changes from a recent campaign
- Bulk-detach deprecated form tags across a section in one motion
-
Cross-reference the
mouseflow_settingsrow with per-post overrides
Features
What SleekView gives you for Mouseflow Pro
Override and form-tag inventory
Every post carrying a _mouseflow_* postmeta becomes a row. The decisions that accumulated across campaigns finally become searchable in one grid.
Filter by tag or exclusion
Stack filters across post type, form tag, exclusion state, and consent gate. The exact slice for compliance or marketing becomes a saved view in seconds.
Bulk override edits
Select rows and detach a stale form tag or toggle exclusions in batches. Updates route through update_post_meta and apply on the next request.
Audience
Who uses SleekView for Mouseflow Pro
Compliance and privacy
Verify account, billing, and legal pages remain excluded from session recording. Filter _mouseflow_exclude to spot compliance gaps before the next review.
Conversion marketers
Confirm each campaign's form is tagged correctly in Mouseflow. Filter by form-tag value to verify the right pages map to the right funnel report.
Implementation consultants
Diagnose missing recordings or broken funnels by filtering for posts where tracking was excluded or the form tag changed unexpectedly.
The bigger picture
Why Mouseflow's WordPress configuration needs a queryable layer
Mouseflow's value sits in the cloud product: session replay, heatmaps, funnel analytics, and form analytics. The WordPress plugin handles the loader and a handful of per-post overrides, which is the right scope. The unstated cost is that override decisions never stop accumulating: a new campaign adds a form tag here, a privacy review excludes a section there, a template change leaves orphaned overrides on retired URLs.
The default plugin admin shows the global toggle and the site key, leaving the per-post graveyard invisible. SleekView treats the Mouseflow options row and the _mouseflow_* postmeta as one queryable surface. Compliance teams verify their exclusions still hold.
Conversion marketers confirm each landing page maps to the right funnel report. Implementation consultants stop relying on SQL for diagnostics. Mouseflow's recordings and funnel reports stay in Mouseflow's dashboard.
SleekView only makes the WordPress configuration legible at scale, and only inside the WP admin.
Questions
Common questions about SleekView for Mouseflow Pro
No. Recordings, heatmaps, and funnel reports stay in Mouseflow's own dashboard. SleekView only reads the WordPress configuration in wp_options and per-post _mouseflow_* postmeta.
Yes. The plugin writes the same option name and postmeta keys across all plan tiers. SleekView surfaces whatever data the plugin has stored, regardless of plan.
Yes. Filter to the relevant post type or URL pattern, select matching rows, and bulk-set _mouseflow_exclude. Updates write through update_post_meta and Mouseflow's loader picks them up on the next page load.
Yes. SleekView routes meta updates through update_post_meta, firing updated_post_meta and any filter the plugin or your code has attached. Direct DB writes are never used for editable columns.
Yes. Saved views are scoped per role, so a compliance reviewer or a marketing lead can see the columns relevant to their work without access to global Mouseflow settings.
Mouseflow's loader is commonly gated by Complianz, CookieYes, or similar. SleekView surfaces the active gate as a column so admins can verify the gate exists where expected; the consent decision itself still runs in the browser.
No. The grid paginates against the existing wp_postmeta meta_key index and queries only when the view is opened. Saved views don't preload and never run on the front end.
Yes. Each subsite owns its own mouseflow_settings option and its own wp_postmeta rows. SleekView respects the current site context, so per-subsite audits stay self-contained.
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 checkoutBrowse more
- Payu Money Woocommerce
- Woocommerce Coinbase Commerce
- Curcy Multi Currency
- Woocommerce Quickbooks
- Berocket Product Filter
- Woocommerce Product Csv Import
- Woocommerce Hermes Shipping
- Woocommerce Dynamic Pricing
- Wcfm Marketplace
- Woocommerce Variation Prices
- Surecart Affiliates
- Woocommerce Product Feed Pro
- Edd Mailchimp
- Aelia Currencyswitcher
- Automatewoo