SleekView for Hotjar Pro: surveys, feedback & recordings as tables
Hotjar itself stores its insights in Hotjar's own cloud, but the WordPress integration writes site-id, snippet, survey embed configs, and per-post overrides into wp_options and wp_postmeta. SleekView reads those configuration rows and any synced exports stored in WordPress so admins can audit what the snippet is doing on which page.
♾️ Lifetime License available
Audit which pages run which Hotjar tracking, in one queryable view
The Hotjar WordPress plugin stores its site ID, snippet variant, and conditional-load rules in wp_options under keys prefixed hotjar_. Per-post overrides (exclude this page, force-load this survey embed, attach a specific feedback widget) land in wp_postmeta with keys like _hotjar_survey_id and _hotjar_exclude. None of that is queryable from the default Hotjar settings panel, which only shows the global toggle.
SleekView reads both the wp_options Hotjar rows and every post that carries a Hotjar postmeta override. Editors can see which pages are excluded, which surveys are pinned to which posts, and which feedback widgets are active per template, in one sortable, filterable grid. Survey IDs become real columns, exclusion rules become filters, and bulk inline editing routes through the same update_post_meta the plugin uses.
The actual recordings, heatmaps, and survey responses still live in Hotjar's cloud and are accessed through their dashboard, as expected. SleekView only exposes the WordPress-side configuration: which tracking runs where, who excluded what, and which posts carry overrides. That alone usually answers the question a developer hits first: "why is the snippet firing on this page?"
Workflow
From Hotjar postmeta to one audit grid
Connect the Hotjar data sources
wp_options rows prefixed hotjar_ and any post carrying a _hotjar_* postmeta key. Settings and per-post overrides surface together.
Compose the audit columns
Save and scope views per role
Inline edit and bulk update
_hotjar_exclude, swap survey IDs, or detach feedback widgets in bulk. Updates route through update_post_meta and refresh on the next page load.
Sample columns
A typical Hotjar tracking configuration view
wp_postmeta.
wp_options (hotjar_*) + wp_postmeta (_hotjar_*)
| Page | Post type | Survey ID | Feedback widget | Excluded | Last edited |
|---|---|---|---|---|---|
| /pricing/ | page | 8421 | fb_pricing | Tracked | Apr 24 |
| /checkout/ | page | - | - | Excluded | Apr 18 |
| /blog/onboarding-redesign/ | post | 8411 | fb_blog | Tracked | Apr 22 |
| /legal/privacy/ | page | - | - | Blocked | Mar 12 |
Comparison
Default Hotjar Pro admin vs SleekView
Default Hotjar Pro admin
- Only the global snippet toggle is exposed in the settings screen, no inventory of per-post overrides
-
_hotjar_survey_idand_hotjar_excludepostmeta keys are invisible from the dashboard - No way to filter posts by which survey or feedback widget is attached
- Auditing why a survey loads on one page but not another means reading source or grepping postmeta
- Bulk-removing an exclusion across a content section requires WP-CLI or SQL
SleekView
-
Inventory every Hotjar override attached to
wp_postmetain a single grid -
Filter by
_hotjar_survey_id, exclusion state, or feedback widget slug - Sort by last edited to find recently changed tracking rules
-
Bulk update
_hotjar_excludeacross a category or post type -
Audit the
wp_optionsHotjar config row next to the per-post overrides
Features
What SleekView gives you for Hotjar Pro
Postmeta inventory
Every post carrying _hotjar_survey_id, _hotjar_exclude, or a feedback widget override becomes a row. Stop hunting through individual post editors to find where tracking is pinned.
Filter by survey or exclusion
Stack filters across post type, survey ID, exclusion state, and last edited date. The exact subset ("all blog posts excluded from tracking") becomes a saved view in seconds.
Bulk inline editing
Select rows and toggle exclusions or change attached survey IDs in batches. Edits write through update_post_meta so Hotjar's own loader picks them up on the next request.
Audience
Who uses SleekView for Hotjar Pro
Marketing operations
Maintain a clean map of which surveys run on which funnels. Filter by survey ID and post type to verify the pricing-page survey is actually attached to /pricing/ and nothing else.
Privacy and compliance
Audit which pages are excluded from Hotjar tracking. Filter _hotjar_exclude to confirm checkout, account, and legal pages are off the snippet without opening each one.
Developers and consultants
When an embed misbehaves, open SleekView, filter for the survey ID, and see every post it's pinned to. Faster than grepping postmeta or reading the snippet output.
The bigger picture
Why Hotjar's WordPress side needs an audit surface
Hotjar's core product (recordings, heatmaps, surveys) is a cloud service, and that's where the analysts spend their day. The WordPress side of the integration looks small (a snippet toggle, a few survey embeds) but it's where the operational mess accumulates. Over a year of A/B tests, a marketing team ends up with dozens of _hotjar_survey_id overrides pinned to individual posts, some long-forgotten exclusions on legal pages, and a couple of feedback widgets attached to templates nobody owns anymore.
The default Hotjar admin screen doesn't list any of that. The only way to inventory it is to read every post's metabox or query wp_postmeta directly. SleekView turns that inventory into a saved grid.
Marketing ops can verify the right survey is on the right funnel. Privacy reviewers can confirm checkout, account, and legal pages are excluded from tracking. Developers can answer "why is the snippet firing here?" in seconds.
None of this replaces Hotjar's own dashboards, it just makes the WordPress configuration legible at the scale teams actually operate at.
Questions
Common questions about SleekView for Hotjar Pro
No. Recordings, heatmaps, and survey responses live in Hotjar's own cloud and stay there. SleekView only reads the WordPress-side configuration in wp_options and wp_postmeta, which is where the plugin records which tracking runs where.
Yes. The free plugin uses the same wp_options key pattern and the same _hotjar_exclude postmeta convention. Pro adds extra postmeta keys for survey-per-post and feedback-widget-per-post overrides, and SleekView surfaces those automatically when they exist.
Yes. Filter to posts in a category, select all, and bulk-set _hotjar_exclude to true. Edits go through update_post_meta, so any front-end caching layer that respects Hotjar's loader picks up the change normally.
Yes. SleekView always routes meta updates through WordPress's normal update_post_meta, which fires updated_post_meta and any filters the Hotjar plugin or your own code has attached. There are no direct DB writes that would bypass cache invalidation.
Yes. SleekView supports per-role saved views, so a marketing editor can see attached survey IDs without access to global Hotjar settings or other plugin areas. Field-level permissions can hide the exclusion column from roles that shouldn't change tracking.
No. SleekView only loads when an admin opens the view. The post editor's own performance is unchanged because the existing Hotjar metabox keeps doing its work, and the grid only queries on demand against the existing wp_postmeta indexes.
Hotjar's WordPress integration commonly chains to a consent plugin via the hotjar_pre_load filter or a postmeta gate. SleekView shows the postmeta state for each post, so you can verify the gate exists where you expect it. The consent decision itself still runs on the front end as before.
Yes. Each subsite owns its own wp_options row and per-post wp_postmeta entries with the subsite's table prefix. SleekView respects the current site context, so a network admin building views per subsite gets a clean per-site inventory of Hotjar tracking.
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
- Woocommerce Moneris
- Woocommerce Product Add Ons
- Woocommerce Affirm
- Yith Woocommerce Tab Manager
- Woocommerce Wholesale Lead Capture
- Woocommerce Multi Currency Switcher
- Woocommerce Direct Checkout Pro
- Woocommerce Quaderno
- Etsy Shop Importer
- Woocommerce Allegro Pl
- Woocommerce Warehouse Management
- Woocommerce Currency Per Product
- Woocommerce Multilingual Currency
- Woocommerce Checkout Addons
- Woocommerce Canpar Shipping