✨ 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 Convert AB Testing: project mappings and goal configs as tables

Convert AB Testing integrations store project IDs, experience mappings, and goal configurations as options and postmeta. SleekView joins those records into one grid so growth teams can see every experience and its targeting in one place.

♾️ Lifetime License available

SleekView table view for Convert AB Testing

Audit every Convert experience and goal mapping in one grid

Convert AB Testing integrations typically write the project ID and account configuration to wp_options under keys like convert_project_id and convert_settings. Per-page experience overrides and goal mappings live in wp_postmeta under keys like _convert_experience_id and _convert_goal_id. Heavier integrations also write a log table such as wp_convert_log for snippet load and goal-fire events.

The default WordPress admin gives no consolidated view of where Convert experiences are configured. The project ID and account-level settings live in the integration plugin's own panel, the per-page meta keys never appear on the page list table, and goal mappings are not searchable from the admin. Auditing which pages carry per-page overrides means inspecting each post individually.

SleekView reads the Convert-related wp_postmeta keys plus the global settings from wp_options and joins them with the log table when present. Page, project, experience ID, goal mapping, last log entry, and override status all appear in one row. Edits route through the integration's save hooks so any audience cache or rule reload continues to fire.

Workflow

From Convert meta keys to a queryable audit

1

Pick the meta and options patterns

Configure SleekView to scan wp_postmeta for keys matching _convert_% and wp_options for convert_% keys. Each surfaced key becomes an available column.
2

Compose your columns

Pick page, project, experience ID, goal mapping, 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 project-scoped view, and QA gets a goal-mapping validation grid.
4

Edit inline or bulk update

Swap experience IDs, change goal mappings, and clear stale overrides inline. Bulk migrate pages between projects when consolidating after an organizational change.

Sample columns

A typical Convert AB Testing experience view

Pages with Convert experience IDs, goal mappings, and last log status, joined to wp_options project config.
Source: wp_postmeta (key LIKE '_convert_%') + wp_options (key LIKE 'convert_%') + wp_convert_log
Page Project Experience ID Goal mapping Last log Status
/pricing/ proj_8821 exp_4471 purchase Apr 25 14:02 OK
/signup/ proj_8821 exp_4488 signup_complete Apr 25 09:11 OK
/blog/banner-test/ proj_8821 exp_4501 newsletter_optin Apr 22 18:11 Stale
/legacy-promo/ proj_8821 exp_4302 purchase Jan 03 11:00 Goal missing

Comparison

Default Convert AB Testing admin vs SleekView

Default Convert AB Testing integration

  • The integration's settings panel shows only the project ID and global flags
  • _convert_experience_id and _convert_goal_id meta keys are hidden in custom fields
  • Per-page experience overrides require opening each post one by one to inspect
  • Log entries in wp_convert_log are not joined to the pages they reference
  • Bulk reassigning experiences across pages requires WP-CLI or direct SQL

SleekView

  • One grid joining pages with their Convert wp_postmeta keys and the global wp_options project config
  • Filter pages by experience ID, goal mapping, or project
  • Sort by last log entry to find pages where the goal stopped firing
  • Bulk swap experience IDs when consolidating campaigns or migrating projects
  • Export a per-project experience audit to CSV for stakeholder reviews

Features

What SleekView gives you for Convert AB Testing

Pages, experiences, and goals joined

Each row shows the WordPress page, the Convert experience ID and goal mapping from wp_postmeta, and the project context from wp_options in one grid.

Filter by goal mapping

Stack filters on goal mapping, experience ID, and project. Find every page mapped to the purchase goal or every page still tied to a retired experience in one click.

Bulk migrate experiences

Select pages and bulk update _convert_experience_id when consolidating projects or moving to a new Convert account. The save hook fires so audience caches refresh.

Audience

Who uses SleekView for Convert AB Testing

Growth teams

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

QA engineers

Filter by goal mapping to validate every page that should fire purchase after a checkout change. Confirm experience IDs match the latest Convert configuration before release.

Marketing leads

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

The bigger picture

Why Convert on WordPress needs an audit surface

Convert's strength is enterprise-grade experimentation with strong audience and segmentation rules. The trade-off is configuration sprawl. Account-level settings sit in WordPress options, project assignments and per-page experience overrides sit in postmeta, and goal mappings are scattered across whichever pages the marketing team has touched.

Over time the integration plugin's settings panel becomes a poor map of the actual deployment. Retired experiences leave dead IDs on pages, goal names change in the Convert dashboard and break their WordPress bindings, and acquisitions consolidate projects without anyone catching which pages still reference the old project. The default WordPress admin surfaces none of this.

SleekView treats the integration's records as the structured data they actually are. Pages, projects, experience IDs, goal mappings, and log entries become joinable columns. Growth teams catch stale experiences before the next cycle, QA validates goal mappings after every release, and marketing leads scope views per project for stakeholder reviews.

The result is a Convert deployment whose WordPress configuration stays legible as the program scales.

Questions

Common questions about SleekView for Convert AB Testing

No. SleekView only reads and writes the WordPress records that the integration uses. Convert experiences and audiences are managed in the Convert dashboard and the snippet continues to run as configured.

 

Yes. Goal mappings stored in _convert_goal_id or similar meta keys become a column with inline editing. Filter by goal to find every page tied to a specific conversion.

 

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

 

Yes. Select rows and bulk update the experience ID meta key. The integration's save hook fires per row so cached audiences and rule sets refresh.

 

Yes when the integration supports multi-project configuration. SleekView reads the wp_options project list and surfaces each project as a filter, letting you scope views per project.

 

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

 

Yes. Growth gets the full audit, marketing gets a project-scoped view, and QA gets a goal-mapping validation grid. Role checks happen before the query so unauthorized columns never load.

 

Yes. Each subsite's wp_postmeta and wp_options are scoped per blog. Network admins can audit each subsite's Convert 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