SleekView for Wisepops for WordPress
The Wisepops WordPress plugin stores the site ID and inclusion rules in wp_options and (optionally) records script emissions in an audit log. SleekView reads both directly so marketers, ops and legal each get a sortable, filterable table over the embed surface.
♾️ Lifetime License available
Stop reading toggle screens to audit script coverage
The Wisepops WordPress plugin is a thin script bridge. It stores the Wisepops site ID, the inclusion rules (which post types load the tag, which pages are excluded) and the consent gating flag in wp_options. When the plugin's audit option is enabled, each front-end load that emitted the script writes a row to a small emission log with timestamp, post type, template and status flag.
The default plugin admin renders the site ID field, a few inclusion toggles and the consent flag. Useful for one-time setup. Limited for the ongoing question marketers, ops and legal ask: which pages are actually firing the script today, did a theme refresh drop coverage, is consent gating set correctly on production but on staging too. Each answer sits in the option store and emission log already.
SleekView reads the Wisepops plugin option and the emission log directly. The rules view shows post type, exclusion pattern and consent flag in row-level form. The emission log lands in its own view with timestamp, post type, template and status, sortable and filterable. Filter to one post type, save the view as a coverage audit. Same option store the plugin already maintains, surfaced as a workspace.
Workflow
How SleekView reads your Wisepops plugin storage
Connect the plugin storage
Compose your column set
Save and scope the view
Filter, export and share
Sample columns
A typical Wisepops for WordPress embed-rules view
wp_319_options (wisepops settings) + wisepops_emission_log
| Post type | Inclusion | Consent flag | Last seen | Emissions (7d) | Status |
|---|---|---|---|---|---|
| post | Included | On | May 14 | 12,408 | Active |
| page | Included | On | May 14 | 8,231 | Active |
| product | Included | On | May 14 | 21,094 | Active |
| docs | Excluded | On | — | 0 | Excluded |
| landing | Included | Off | May 11 | 0 | No emissions |
Comparison
Default Wisepops for WordPress admin vs SleekView
Default Wisepops WP plugin admin
- Settings screen renders toggles with no per-post-type coverage view
- No column control or sort on the inclusion rules list
- Emission audit log (when enabled) has no table UI beyond a raw dump
- Consent gating flag drift across staging and production is invisible
- No saved per-role views for marketing, ops and legal
SleekView
- Read directly from the Wisepops settings option in wp_options
- Join the emission audit log for last-seen and recent-count columns
- Filter rules by post type, inclusion state or consent flag
- Save filtered views per role ("No emissions in 7 days", "Consent off")
- Switch between rules view and emission log view in one tabbed page
Features
What SleekView gives you for Wisepops for WordPress
Rules as a row-level workspace
Combine post type, inclusion state and consent flag into a filterable table. Replace the toggle screen with a workspace that answers the coverage question on sight.
Compose precise filters
Combine post type, consent flag and last-seen window into one saved filter. A view like "Included, consent on, no emissions in 7 days" runs as one query.
Emission log as its own table
Render each script emission as a sortable row with timestamp, post type, template and status. The audit log stops being a flat dump and starts being usable.
Audience
Who uses SleekView for Wisepops for WordPress
Email marketers
Confirm the popup is firing on the post types the plan called for. Sort rules by recent-emission count to see real coverage, not a toggle that says the rule is active.
Privacy and legal
Filter the rules view by consent flag to confirm gating is on in production. Catch a staging-on, production-off drift the same day a deploy lands.
Integrations ops
Use the emission log view to spot a post type that stopped emitting after a theme refresh. Save the view as a recurring health check the team reruns weekly.
The bigger picture
Why the Wisepops embed surface deserves a table
Wisepops owns the campaign, the audience and the analytics on the SaaS side, where they belong. The WordPress plugin holds the embed surface: which post types include the script, which pages are excluded, whether consent gating is on, whether the footer hook still fires after a theme refresh. Treating that surface as a toggle screen makes routine audits manual and easy to skip.
Treating it as a sortable, filterable table makes a coverage review a one-minute job. Marketing sees the post types actually emitting. Legal sees the consent flag at a glance.
Ops catches a dropped hook the same week instead of waiting for the Wisepops impression curve to flatten. Same option store and audit log the plugin already maintains, surfaced as the workspace the data deserves.
Questions
Common questions about SleekView for Wisepops for WordPress
Yes. The Wisepops for WordPress plugin stores the site ID and inclusion rules in wp_options, and (when enabled) writes script emission rows to either an option array or a small custom table depending on the version. SleekView reads each storage path directly and pivots it into named columns.
Yes. SleekView treats the rules option and the emission log as two related datasets in one tabbed page. A join surfaces last-seen timestamp and recent emission count as columns on the rules table.
The rules view works regardless because it reads wp_options. Emission columns require the plugin's audit log to be enabled or a lightweight wp_footer hook SleekView samples. Without either source, the emission columns show a friendly empty state and the rules view keeps rendering.
No. Impressions, conversions and audience analytics stay in Wisepops where the campaign was composed. SleekView reads only the WP-side plugin storage: settings, inclusion rules and any emission audit log.
Yes. Post type is a first-class column on the rules view. Filter to one post type to scope every audit (consent flag, last-seen, recent count) to that slice, useful for a campaign scoped to one content area.
Yes. Any filtered table exports as CSV with the same columns shown. Marketing uses this for coverage reviews, legal uses it for consent audits, ops uses it for theme-refresh post-mortems.
No. SleekView reads the option store and emission log on demand inside wp-admin, and never touches the front-end emission path. Front-end script loading runs through the plugin's own runtime path unchanged.
No. The plugin's own settings screen and connection panel stay in place for setup. SleekView adds a row-level admin surface for the audit operations the toggle screen does not provide. The two coexist on the same option store without conflict.
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