✨ 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 Kameleoon WP: experiment configs and segment mappings as tables

Kameleoon WP integrations store site code, experiment mappings, and segment overrides as options and postmeta. SleekView joins those records into one grid so growth teams can see every experiment, its segment, and its targeting in one place.

♾️ Lifetime License available

SleekView table view for Kameleoon WP

See every Kameleoon experiment and segment override in one grid

Kameleoon WP integrations typically write the site code and account configuration to wp_options under keys like kameleoon_site_code. Per-page experiment overrides and segment mappings live in wp_postmeta under keys like _kameleoon_experiment_id and _kameleoon_segment_id. Heavier integrations write a log table such as wp_kameleoon_log for snippet load and event fire confirmations.

The default WordPress admin shows Kameleoon configuration as a single settings panel with the site code and a handful of global flags. Per-page experiment overrides and segment mappings live in wp_postmeta and never surface on the page list table. Auditing which pages carry overrides for which experiments or segments requires opening each post individually.

SleekView reads the Kameleoon-related wp_postmeta keys plus the global settings from wp_options and joins them with the log table when present. Page, site code, experiment ID, segment ID, goal mapping, last log entry, and override status all appear in one row. Edits route through the integration's save hooks so segment caches and rule sets refresh as expected.

Workflow

From Kameleoon meta keys to a queryable audit

1

Pick the meta and options patterns

Configure SleekView to scan wp_postmeta for keys matching _kameleoon_% and wp_options for kameleoon_% keys. Each surfaced key becomes a column.
2

Compose your columns

Pick page, site code, experiment ID, segment, last log entry, and override status. Save the column set as a named view.
3

Save and scope per role

Assign views to roles. Growth gets the full audit, marketing gets a segment-scoped view, and QA gets a segment-mapping validation grid.
4

Edit inline or bulk update

Swap segment IDs, change experiment IDs, and clear stale overrides inline. Bulk migrate pages between Kameleoon accounts when consolidating after an organizational change.

Sample columns

A typical Kameleoon WP experiment view

Pages with Kameleoon experiment IDs, segment mappings, and last log status, joined to wp_options site config.
Source: wp_postmeta (key LIKE '_kameleoon_%') + wp_options (key LIKE 'kameleoon_%') + wp_kameleoon_log
Page Site code Experiment ID Segment Last log Status
/pricing/ site_aaa1 exp_8821 seg_returning Apr 25 14:02 OK
/signup/ site_aaa1 exp_8835 seg_new Apr 25 09:11 OK
/enterprise/ site_aaa1 exp_8842 seg_b2b Apr 22 18:11 Slow
/old-funnel/ site_aaa1 exp_8001 seg_legacy Jan 12 11:00 Segment gone

Comparison

Default Kameleoon WP admin vs SleekView

Default Kameleoon WP integration

  • The integration's settings panel shows the site code and global flags only
  • _kameleoon_experiment_id and _kameleoon_segment_id meta keys are hidden in custom fields
  • Segment overrides per page require opening each post and inspecting meta one by one
  • Log entries in wp_kameleoon_log are not joined to the pages they reference
  • Bulk reassigning segments across pages requires WP-CLI or direct SQL

SleekView

  • One grid joining pages with their Kameleoon wp_postmeta keys and the global wp_options site config
  • Filter pages by experiment ID, segment, or override status
  • Sort by last log entry to find pages where the experiment stopped firing
  • Bulk swap segment mappings when consolidating segments or migrating accounts
  • Export a per-segment experiment audit to CSV for stakeholder reviews

Features

What SleekView gives you for Kameleoon WP

Pages, experiments, and segments joined

Each row shows the WordPress page, the Kameleoon experiment and segment IDs from wp_postmeta, and the site code from wp_options in one grid.

Filter by segment

Stack filters on segment, experiment ID, and last log timestamp. Find every page mapped to the returning visitor segment or every page tied to a retired segment in one click.

Bulk migrate segments

Select pages and bulk update _kameleoon_segment_id when consolidating segments or moving to a new Kameleoon account. The integration's save hook fires so segment caches refresh.

Audience

Who uses SleekView for Kameleoon WP

Growth analysts

Audit every page-level Kameleoon override in one grid. Catch pages still bound to retired segments or experiments and re-point them in bulk before the next growth cycle.

QA engineers

Filter by segment to validate every page targeting the B2B audience after a CMS change. Confirm experiment IDs and segment mappings match the latest Kameleoon configuration before release.

Marketing leads

Group pages by segment and experiment to see which campaigns carry which WordPress assets. Save a per-segment view and share it read-only with the team.

The bigger picture

Why Kameleoon on WordPress needs an audit surface

Kameleoon is a strong fit for sites that need rich segmentation and feature flags in the same platform. The cost of that flexibility is configuration sprawl on the WordPress side. The site code lives in options, per-page segment overrides live in postmeta, and feature flag bindings end up scattered across whichever templates the team has touched.

The integration plugin's settings panel surfaces the site code and a few flags, which makes it impossible to answer questions like which pages still target a retired segment, which experiments stopped firing after a theme update, or which segments are most heavily bound across the site. SleekView treats the integration's records as the structured data they actually are. Pages, experiment IDs, segments, site codes, and log entries become joinable columns.

Growth analysts catch stale segments before the next cycle, QA validates segment mappings after every release, and marketing leads scope views per segment for stakeholder reviews. The result is a Kameleoon deployment that stays aligned with the live site as the experimentation program scales.

Questions

Common questions about SleekView for Kameleoon WP

No. SleekView only reads and writes the WordPress records that the integration uses. Kameleoon experiments and segments themselves are managed in the Kameleoon dashboard and the snippet continues to run as configured.

 

Yes. Segment mappings stored in _kameleoon_segment_id become a column with inline editing. Filter by segment to find every page targeting a specific audience.

 

Yes when the integration writes a log table. SleekView joins the latest row per page or experiment so initialization errors and event fire confirmations sit alongside the configuration.

 

Yes. Select rows and bulk update the segment ID meta key. The integration's save hook fires per row so cached segment rules refresh and the next page render picks up the new segment.

 

Yes when the integration stores them in wp_postmeta or wp_options. Kameleoon supports both AB and feature flag use cases, and SleekView surfaces whichever keys the integration writes.

 

No. Pagination uses existing indexes on wp_postmeta and wp_options. Log joins are bounded so the grid stays responsive at hundreds of experiments.

 

Yes. Growth analysts get the full audit, marketing gets a segment-scoped view, and QA gets a segment-mapping validation grid. Role checks happen before the query.

 

Yes. Each subsite has its own wp_postmeta and wp_options, and SleekView respects that scoping. Network admins can audit each subsite's Kameleoon footprint independently.

 

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