✨ 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 Contentsquare: tag IDs, masked zones & overrides as tables

Contentsquare runs its experience analytics in its own platform, but the WordPress plugin keeps the tag ID, the masked-zones map, and per-post overrides in wp_options and wp_postmeta. SleekView turns that configuration into one queryable inventory of which pages send sessions and which are masked.

♾️ Lifetime License available

SleekView table view for Contentsquare for WordPress

See your Contentsquare tag coverage across the site, in one grid

The Contentsquare WordPress plugin saves the tag ID, masked-zones JSON, and post-type allowlist to wp_options under contentsquare_settings. Per-post overrides land in wp_postmeta as _cs_track and _cs_mask_zone. The settings screen exposes the tag ID and a JSON textarea for masked zones, but no inventory of per-post overrides.

SleekView reads the Contentsquare options row and every post carrying a _cs_* postmeta into one sortable, filterable grid. Tag coverage state, masked-zone presence, and per-post overrides become first-class columns. Enterprise teams filter by post type and masked-zone definition to verify privacy posture; marketers verify tag coverage across landing pages.

Experience analytics, zone heatmaps, journey analysis, and conversion funnels stay in the Contentsquare app where the analysts work. SleekView focuses on the WordPress side: which pages send data, which are excluded, and which masked-zone rules apply per template.

Workflow

From Contentsquare postmeta to one privacy audit

1

Connect the Contentsquare sources

SleekView reads contentsquare_settings from wp_options and every post carrying a _cs_* key. Tag and masking state surface in one grid.
2

Compose masking columns

Pick page, post type, tracking state, masked-zone profile, consent gate, and last edited. Privacy and analytics teams each get the row shape that fits.
3

Save scoped views

Save an Enterprise Privacy view, a Tag Coverage view, and a Diagnostics view. Scope each per role so the right team opens the right grid.
4

Inline edit and bulk apply

Apply stricter masking, exclude pages, or adjust per-template overrides in batches. Updates flow through update_post_meta and apply on the next page load.

Sample columns

A typical Contentsquare tag coverage inventory

Posts with explicit Contentsquare overrides joined to the contentsquare_settings options row.
Source: wp_options (contentsquare_settings) + wp_postmeta (_cs_track, _cs_mask_zone)
Page Post type Tracking Masked zones Consent gate Last edited
/home/ page On default onetrust Apr 24
/account/profile/ page Masked pii_strict onetrust Apr 02
/checkout/payment/ page Blocked pii_strict onetrust Mar 10
/blog/product-update/ post On default - Apr 19

Comparison

Default Contentsquare admin vs SleekView

Default Contentsquare admin

  • Settings screen shows tag ID and a masked-zone JSON textarea, no per-post override inventory
  • _cs_track and _cs_mask_zone postmeta are invisible from any default dashboard view
  • No way to filter pages by masking level or tag coverage state
  • Auditing zone masking per template requires opening each post
  • Bulk-applying stricter masking to account pages needs WP-CLI

SleekView

  • Inventory every _cs_track and _cs_mask_zone override in one grid
  • Filter by post type, tracking state, masking level, or consent gate
  • Bulk-apply PII masking across account and billing sections
  • Sort by last edited to detect recent override changes
  • Cross-reference the contentsquare_settings row with per-post state

Features

What SleekView gives you for Contentsquare for WordPress

Tag and masking inventory

Every post carrying a _cs_* postmeta becomes a row. The override graveyard from past campaigns and privacy reviews finally becomes searchable from one screen.

Filter by mask level

Combine post type, masking level, tracking state, and consent gate. The exact slice ("every account page that should run strict masking") becomes a saved view.

Bulk masking edits

Apply stricter masking or exclude sensitive pages in batches. Updates route through update_post_meta and the Contentsquare loader picks them up on the next request.

Audience

Who uses SleekView for Contentsquare

Enterprise privacy

Verify that account, billing, and checkout pages run the right masking. Filter _cs_mask_zone to confirm policy across thousands of pages before the next privacy review.

Experience analytics teams

Confirm tag coverage across the customer journey. Filter by post type and tracking state to verify the funnel pages are firing into Contentsquare as expected.

Implementation consultants

Diagnose journey gaps by filtering for posts where tag coverage broke or masking changed. The audit grid replaces line-by-line postmeta inspection.

The bigger picture

Why enterprise Contentsquare rollouts need a real audit surface

Contentsquare is an enterprise experience-analytics platform, so the typical deployment spans thousands of pages, multiple brands, and a privacy team that reviews the masking posture quarterly. The WordPress plugin handles the tag ID, the masked-zone configuration, and per-post overrides, but the default settings screen is a JSON textarea and a global toggle. After a year, every site has dozens of _cs_track and _cs_mask_zone overrides scattered across templates, with no inventory anywhere.

Reconciling the masked-zone JSON with the per-post overrides by hand takes an afternoon, and that is the work compliance has to repeat every review cycle. SleekView treats the options row and the per-post postmeta as one queryable surface. Privacy teams verify masking in minutes.

Experience analytics teams confirm tag coverage across the customer journey. Implementation consultants diagnose gaps without falling back to SQL. Contentsquare's analytics stay in Contentsquare.

SleekView makes the WordPress side legible at the scale enterprise rollouts demand.

Questions

Common questions about SleekView for Contentsquare for WordPress

No. Experience analytics, zone heatmaps, journeys, and funnels live in Contentsquare's own platform. SleekView only reads the WordPress configuration in wp_options and per-post _cs_* postmeta.

 

No. The plugin writes the same option name and postmeta keys regardless of Contentsquare plan tier. SleekView surfaces whatever data the plugin has stored, free trial or enterprise.

 

Yes. Filter to the account post type or URL pattern, select matching rows, and bulk-set _cs_mask_zone to the strict profile. Updates write through update_post_meta and the loader applies the new masking immediately.

 

Yes. Meta updates flow through update_post_meta, firing updated_post_meta and any filter the plugin or your code has attached. Editable columns never bypass the standard meta API.

 

Yes. Saved views are scoped per role, so an enterprise compliance reviewer can see tracking and masking state across all pages without access to global Contentsquare settings or other plugins.

 

Contentsquare's loader is commonly gated by OneTrust, Cookiebot, or another CMP. SleekView surfaces the active 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. On sites with millions of postmeta rows, the grid still resolves at table-scan speed because it targets specific keys.

 

Yes. Each subsite has its own contentsquare_settings option and its own wp_postmeta rows. SleekView respects the active site, so each subsite's Contentsquare audit stays cleanly scoped.

 

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