✨ 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 VWO WP: campaign embeds and integration logs as tables

VWO WP integrations store account IDs, campaign mappings, and goal tracking flags as options and postmeta. SleekView turns those records into a sortable grid so growth teams can see every campaign, its targeting, and its status.

♾️ Lifetime License available

SleekView table view for VWO WP

See every VWO campaign embed and goal mapping in one grid

VWO WP integrations typically write account configuration to wp_options (under keys like vwo_account_id and vwo_settings) and per-page targeting overrides or goal mappings to wp_postmeta under keys like _vwo_campaign_id and _vwo_goal_id. Integration logs (initialization errors, goal-fire confirmations) land in a log table such as wp_vwo_log on heavier integrations.

The default WordPress admin surfaces VWO settings through the integration plugin's own panel, which lists the account ID and a few global flags. Per-page targeting overrides and per-post goal mappings live in wp_postmeta and never appear on the page list. Auditing which pages carry per-page overrides, or which goal IDs are mapped to which WordPress events, requires inspecting each post.

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

Workflow

From VWO meta keys to a campaign audit grid

1

Pick the meta and options patterns

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

Compose your columns

Pick page, account ID, campaign ID, goal mapping, last log entry, and override status. Save the column set as a named view.
3

Save and scope per role

Assign saved views to roles. Growth gets the full audit, marketing gets a campaign-scoped slice, and QA gets a goal-mapping validation view.
4

Edit inline or bulk update

Swap campaign IDs, change goal mappings, and clear stale overrides inline. Bulk migrate pages between VWO accounts when consolidating after an acquisition.

Sample columns

A typical VWO WP campaign mapping view

Pages with VWO campaign IDs, goal mappings, and last log status, joined to wp_options account config.
Source: wp_postmeta (key LIKE '_vwo_%') + wp_options (key LIKE 'vwo_%') + wp_vwo_log
Page Account Campaign ID Goal mapping Last log Status
/pricing/ acc_29401 camp_771 purchase Apr 25 14:02 OK
/signup/ acc_29401 camp_882 signup_complete Apr 25 09:11 OK
/blog/cta-test/ acc_29401 camp_413 newsletter_optin Apr 22 18:11 Stale
/old-promo/ acc_29401 camp_201 purchase Feb 11 11:00 Goal missing

Comparison

Default VWO WP admin vs SleekView

Default VWO WP integration admin

  • The integration's settings panel surfaces global account config only, not per-page overrides
  • _vwo_campaign_id and _vwo_goal_id meta keys are hidden in custom fields
  • Goal mapping for a page is invisible without opening the post and inspecting meta
  • Integration log entries in wp_vwo_log are not joined to the pages they reference
  • Bulk swapping a campaign ID across many pages requires WP-CLI or SQL

SleekView

  • One grid joining pages with their VWO wp_postmeta keys and the global VWO wp_options account
  • Filter pages by campaign ID, goal mapping, or override status
  • Sort by last log entry to spot pages where the goal stopped firing
  • Bulk swap campaign IDs and goal mappings when migrating between VWO accounts
  • Export a per-account campaign audit to CSV for stakeholder reviews

Features

What SleekView gives you for VWO WP

Pages, campaigns, and goals joined

Each row shows the WordPress page, the VWO campaign ID and goal mapping from wp_postmeta, and the relevant account ID from wp_options in one grid.

Filter by goal mapping

Stack filters on goal mapping, campaign ID, and override status. Find every page mapped to the purchase goal in one click, or every page still mapped to a retired goal.

Bulk migrate campaigns

Select pages and bulk update _vwo_campaign_id when consolidating campaigns or moving to a new VWO account. The integration's save hooks fire so rule caches refresh.

Audience

Who uses SleekView for VWO WP

Growth analysts

Audit every page-level VWO override in one grid. Spot pages still mapped to retired campaigns 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 refactor. Confirm goal IDs match the latest VWO setup before the next release.

Marketing leads

Group pages by campaign and account to see which marketing initiatives carry which WordPress assets. Save a per-campaign view and share it read-only with the team.

The bigger picture

Why VWO on WordPress needs an audit surface

VWO sits in two places at once. The campaign definitions, audience rules, and statistical models all live in the VWO dashboard, but the WordPress side of the integration carries per-page overrides, goal mappings, and account configuration that decay quietly. A campaign retired in VWO leaves its campaign ID in wp_postmeta on the pages it targeted.

A goal renamed in VWO leaves the old name mapped on dozens of WordPress posts. A test that fired correctly in Q1 stops firing in Q3 because a checkout refactor moved the goal trigger. None of this shows up in the integration's settings panel, which surfaces account ID and a handful of flags.

SleekView treats the integration's records as the structured data they actually are. Pages, campaign IDs, goal mappings, account configuration, and log entries become joinable columns. Growth analysts catch stale campaigns before the next cycle, QA validates goal mappings after every release, and marketing scopes views per campaign for stakeholder reviews.

The result is a VWO deployment that stays aligned with the live site instead of drifting silently.

Questions

Common questions about SleekView for VWO WP

Any VWO integration that stores account configuration in wp_options and per-page overrides in wp_postmeta. SleekView is schema-agnostic and reads whatever keys the integration writes.

 

No. SleekView only reads and writes the WordPress records that the integration uses. VWO campaigns themselves are managed in the VWO dashboard and snippets continue to run as configured.

 

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

 

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

 

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

 

No. SleekView paginates against the existing indexes on wp_postmeta and wp_options. Log joins use a bounded subquery so large sites with many campaigns stay responsive.

 

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

 

Yes. Each subsite has its own wp_postmeta and wp_options, and SleekView respects that scoping. Network admins can audit each subsite's VWO 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