✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView for FullStory Pro: org IDs, blocklists & tracking overrides as tables

FullStory session data and product analytics live in FullStory's own platform, while the WordPress plugin keeps org ID, the blocklist, and per-post overrides in wp_options and wp_postmeta. SleekView reads that configuration and surfaces it as one inventory of which pages send sessions to FullStory.

♾️ Lifetime License available

SleekView table view for FullStory Pro

See exactly which pages send sessions to FullStory, and which do not

The FullStory WordPress plugin writes its org ID, snippet variant, and global blocklist to wp_options under fullstory_settings. Per-post overrides save into wp_postmeta as _fullstory_block, and any masked-field configuration lands under the same prefix. The default settings screen exposes the org ID and global toggle, plus a free-text blocklist textarea, but no inventory of which posts carry overrides.

SleekView reads the FullStory options row and every post carrying a _fullstory_* postmeta into one filterable grid. Tracking state, masked-field flag, and the consent-gate plugin become real columns. Compliance teams filter by blocklist membership, product teams filter by post type, and developers see the global config row next to the per-post overrides without writing SQL.

Session recordings, user journeys, funnels, and conversion metrics stay in the FullStory app, which is where product analytics teams already live. SleekView only handles the WordPress configuration: which pages are in the blocklist, which posts override the default, and how each override changed over time.

Workflow

From FullStory postmeta to one masking audit

1

Connect the FullStory sources

SleekView reads fullstory_settings from wp_options and every post carrying _fullstory_block or related keys. Global and per-post state surface together.
2

Build masking columns

Pick page, post type, tracking state, masking level, consent gate, and last edited. Privacy and product teams each get the row shape that matches their question.
3

Save scoped views

Save a Privacy view for compliance reviewers and an Analytics view for product teams. Scope each per role so each opens the grid that fits their work.
4

Inline edit and bulk apply

Tighten masking on sensitive sections, exclude pages from recording, or relax overrides on test pages in batches. Updates flow through update_post_meta.

Sample columns

A typical FullStory tracking inventory

Posts with explicit FullStory tracking overrides surfaced alongside the global fullstory_settings blocklist.
Source: wp_options (fullstory_settings) + wp_postmeta (_fullstory_block)
Page Post type Tracking Field masking Consent gate Last edited
/product/ page On default iubenda Apr 21
/account/profile/ page Masked strict iubenda Apr 09
/checkout/payment/ page Blocked strict iubenda Mar 16
/blog/launch-notes/ post On default - Apr 18

Comparison

Default FullStory Pro admin vs SleekView

Default FullStory Pro admin

  • Settings screen shows org ID, snippet toggle, and a textarea blocklist, no inventory of per-post overrides
  • _fullstory_block postmeta is invisible from any default screen
  • No way to filter pages by tracking state or masking level
  • Auditing the production blocklist against actual postmeta requires SQL
  • Bulk-applying a stricter mask to account pages needs WP-CLI

SleekView

  • Inventory every _fullstory_block postmeta override as a sortable row
  • Filter by post type, tracking state, mask level, or consent gate
  • Sort by last edited to find recent override changes
  • Bulk-mask sensitive sections with one inline edit
  • Cross-reference the fullstory_settings row with per-post overrides

Features

What SleekView gives you for FullStory Pro

Override inventory

Every post carrying a _fullstory_* postmeta becomes a row. The hidden override graveyard from past campaigns and compliance reviews finally becomes searchable.

Stacked filters

Combine post type, tracking state, masking level, and consent gate filters. Build a saved view of "every account page that should be masked" without writing SQL.

Bulk masking edits

Select rows and apply stricter masking or full blocking in batches. Updates route through update_post_meta and the FullStory snippet picks them up on the next request.

Audience

Who uses SleekView for FullStory Pro

Privacy and compliance

Verify that account, billing, and checkout pages have the right masking level. Filter _fullstory_block and the mask column to confirm policy before each privacy review.

Product analytics teams

Confirm the pages feeding FullStory funnels are tracked, masked correctly, and consent-gated where required. Filter by post type and tracking state to verify the data pipeline.

Implementation consultants

Diagnose why a journey is missing in FullStory by filtering for posts where tracking was disabled or fully masked. The audit grid replaces line-by-line postmeta inspection.

The bigger picture

Why FullStory's WordPress side needs an audit grid

FullStory is a product-analytics platform first, and its WordPress plugin is intentionally a thin loader: drop in the org ID, configure a blocklist textarea, and let the snippet handle the rest. That model works until a privacy review surfaces and the team needs to prove that account, billing, and checkout pages carry the right masking. By then dozens of _fullstory_block overrides and masking flags have accumulated across the site, with no inventory anywhere.

The blocklist in fullstory_settings tells one story, the per-post postmeta tells another, and reconciling them by hand takes an afternoon. SleekView treats the two as one queryable surface. Compliance reviewers verify masking policy in seconds.

Product analytics teams confirm the funnel pages are firing as expected. Implementation consultants diagnose missing journeys without falling back to SQL. FullStory's recordings and analytics keep working in the FullStory app where they belong.

SleekView just makes the WordPress configuration legible at the scale a real privacy review demands.

Questions

Common questions about SleekView for FullStory Pro

No. Session recordings, journeys, funnels, and product analytics live in FullStory's own platform and stay there. SleekView reads only the WordPress configuration in wp_options and _fullstory_* postmeta.

 

Yes. The plugin writes the same option name and postmeta keys regardless of FullStory plan tier. SleekView surfaces whatever the plugin has stored, free or paid.

 

Yes. Filter to the account post type or URL pattern, select matching rows, and bulk-set the masking level. Updates write through update_post_meta and the snippet applies stricter masking 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 registered. Direct DB writes are never used for editable columns.

 

Yes. Saved views are scoped per role, so a compliance reviewer can see tracking and masking state across all pages without access to org-level settings or other plugins.

 

FullStory's loader can be gated by Iubenda, Complianz, or other consent plugins. SleekView surfaces the current gate as a column so admins can verify the gate is wired up where expected; the consent decision itself stays client-side.

 

No. The grid paginates against the existing wp_postmeta meta_key index and queries only when opened. Saved views never preload and never run on the front end.

 

Yes. Each subsite has its own fullstory_settings option and its own wp_postmeta rows with the subsite's prefix. SleekView respects the active site context, so each subsite's FullStory audit stays 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.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

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