✨ 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 AB Tasty WP: campaign mappings and segment configs as tables

AB Tasty WP integrations store account IDs, campaign mappings, and segment overrides as options and postmeta. SleekView joins those records into one grid so growth teams can see every campaign, its segment, and its targeting in one place.

♾️ Lifetime License available

SleekView table view for AB Tasty WP

Audit every AB Tasty campaign and segment override in one grid

AB Tasty WP integrations typically write the account identifier and snippet configuration to wp_options under keys like abtasty_account_id and abtasty_settings. Per-page campaign overrides and segment mappings live in wp_postmeta under keys like _abtasty_campaign_id and _abtasty_segment_id. Heavier integrations write a log table such as wp_abtasty_log for snippet load and goal-fire events.

The default WordPress admin shows AB Tasty configuration through the integration's own settings panel, which lists the account ID and a handful of flags. Per-page campaign overrides and segment mappings live in wp_postmeta and never surface on the page list table. Auditing which pages carry overrides for which campaigns or segments requires opening each post.

SleekView reads the AB Tasty-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, segment, last log entry, and override status all appear in one row. Edits route through the integration's save hooks so any cached segment rules refresh as expected.

Workflow

From AB Tasty meta keys to a queryable audit

1

Pick the meta and options patterns

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

Compose your columns

Pick page, account, campaign 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 campaign-scoped view, and QA gets a segment-mapping validation grid.
4

Edit inline or bulk update

Swap campaign IDs, change segment overrides, and clear stale assignments inline. Bulk migrate pages between AB Tasty accounts when consolidating after an organizational change.

Sample columns

A typical AB Tasty WP campaign view

Pages with AB Tasty campaign IDs, segment overrides, and last log status, joined to wp_options account config.
Source: wp_postmeta (key LIKE '_abtasty_%') + wp_options (key LIKE 'abtasty_%') + wp_abtasty_log
Page Account Campaign ID Segment Last log Status
/pricing/ acc_77110 camp_4471 seg_returning Apr 25 14:02 OK
/signup/ acc_77110 camp_4488 seg_new Apr 25 09:11 OK
/enterprise/ acc_77110 camp_4501 seg_b2b Apr 22 18:11 Slow
/old-promo/ acc_77110 camp_4302 seg_archived Jan 03 11:00 Segment gone

Comparison

Default AB Tasty WP admin vs SleekView

Default AB Tasty WP integration

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

SleekView

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

Features

What SleekView gives you for AB Tasty WP

Pages, campaigns, and segments joined

Each row shows the WordPress page, the AB Tasty campaign and segment IDs from wp_postmeta, and the account ID from wp_options in one grid.

Filter by segment

Stack filters on segment, campaign ID, and account. Find every page mapped to the returning visitor segment or every page tied to a retired campaign in one click.

Bulk migrate campaigns

Select pages and bulk update _abtasty_campaign_id when consolidating campaigns or moving to a new AB Tasty account. The save hook fires so segment caches refresh.

Audience

Who uses SleekView for AB Tasty WP

Growth analysts

Audit every page-level AB Tasty override in one grid. Catch pages still bound to retired campaigns or segments 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 campaign IDs and segment mappings match the latest AB Tasty setup before release.

Marketing leads

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

The bigger picture

Why AB Tasty on WordPress needs an audit surface

AB Tasty is a strong fit for teams that want experimentation and personalization in the same platform. The cost of that combination is configuration sprawl on the WordPress side. The account ID lives in options, per-page segment overrides live in postmeta, and personalization bindings end up scattered across whichever templates the team has touched.

The integration plugin's settings panel surfaces the account ID and a few flags, which makes it impossible to answer questions like which pages still target a retired segment, which campaigns 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, campaign IDs, segments, account IDs, and log entries become joinable columns.

Growth analysts catch stale segments before the next cycle, QA validates campaign mappings after every release, and marketing leads scope views per campaign for stakeholder reviews. The result is an AB Tasty deployment whose WordPress configuration stays aligned with the live site as the experimentation program scales.

Questions

Common questions about SleekView for AB Tasty WP

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

 

Yes. Segment mappings stored in _abtasty_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 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.

 

Yes when the integration stores them in wp_postmeta. AB Tasty supports both experimentation 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 campaigns.

 

Yes. Growth analysts get the full audit, marketing gets a campaign-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 AB Tasty 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