SleekView for Amplitude Experiments: flag assignments, variants & targeting as tables
Amplitude Experiments runs feature flags and A/B tests from Amplitude's platform, while the WordPress plugin keeps the deployment key, per-post flag mappings, and exclusion overrides in wp_options and wp_postmeta. SleekView turns that configuration into one inventory of which pages evaluate which experiments.
♾️ Lifetime License available
Audit which Amplitude flags fire on which pages, without SQL
The Amplitude Experiments plugin writes its deployment key, identity-bridge, and global flag allowlist to wp_options under amplitude_experiments_settings. Per-post overrides save into wp_postmeta as _amplitude_flag_keys and _amplitude_exclude. The default settings screen exposes the deployment key and a comma-separated flag list, but no inventory of which posts override defaults.
SleekView reads the experiments options row and every post carrying an _amplitude_* postmeta into one sortable grid. Attached flag keys become real filterable columns, exclusion state becomes a status, and the identity bridge field surfaces next to the flag-evaluation context. Growth teams filter by flag key to verify experiment coverage; analytics ops verify exclusions across non-experiment URLs.
Experiment design, variant allocation, results dashboards, and statistical analysis stay in the Amplitude Experiments app, where data scientists already work. SleekView only manages the WordPress side: which page evaluates which flags, which page is excluded, and how the per-post overrides have changed.
Workflow
From Amplitude postmeta to one flag-coverage audit
Connect the Amplitude sources
amplitude_experiments_settings from wp_options and every post carrying an _amplitude_* key. Deployment-level config and per-post overrides surface together.
Compose flag-coverage columns
Save scoped views
Inline edit and bulk update
update_post_meta and the SDK picks them up on the next page load.
Sample columns
A typical Amplitude Experiments coverage view
wp_options (amplitude_experiments_settings) + wp_postmeta (_amplitude_flag_keys, _amplitude_exclude)
| Page | Post type | Tracking | Flag keys | Identity bridge | Last edited |
|---|---|---|---|---|---|
| /pricing/ | page | On | pricing_v3, hero_cta | user_id | Apr 25 |
| /checkout/ | page | On | checkout_flow_v2 | user_id | Apr 17 |
| /account/ | page | Excluded | - | user_id | Apr 03 |
| /legal/terms/ | page | Blocked | - | - | Feb 15 |
Comparison
Default Amplitude Experiments admin vs SleekView
Default Amplitude Experiments admin
- Settings screen exposes deployment key and a comma-separated flag list, no per-post override inventory
-
_amplitude_flag_keyspostmeta is invisible from any default screen - No way to filter pages by attached flag key or exclusion state
- Auditing flag coverage across a funnel requires opening each post
- Bulk-detaching a retired flag key needs WP-CLI or SQL
SleekView
-
Inventory every
_amplitude_flag_keysoverride as a sortable row - Filter pages by attached flag key, exclusion state, or identity bridge
- Sort by last edited to detect override changes from a recent release
- Bulk-detach retired flag keys across an old funnel in one motion
-
Cross-reference the
amplitude_experiments_settingsrow with per-post state
Features
What SleekView gives you for Amplitude Experiments for WordPress
Flag coverage inventory
Every post carrying an _amplitude_flag_keys postmeta becomes a row. Verify the production flag set on a real funnel page without opening the post editor.
Filter by flag key
Stack filters across post type, flag key, exclusion state, and identity bridge. Build a saved view of "every checkout-funnel page evaluating the new checkout flag" in seconds.
Bulk flag-key edits
Detach a retired flag, swap a flag key, or exclude a section in batches. Updates route through update_post_meta and the Amplitude SDK picks up the new evaluation context immediately.
Audience
Who uses SleekView for Amplitude Experiments
Growth and experimentation teams
Verify each experiment evaluates on the right pages. Filter by flag key to confirm the new pricing test runs on every variation of /pricing/ and nothing else.
Analytics ops and compliance
Confirm account, billing, and legal pages stay excluded from experiment evaluation. Filter _amplitude_exclude to verify policy across the site.
Implementation engineers
Diagnose flag-misfire bugs by filtering for posts where the flag key was attached or removed recently. The grid replaces SQL-based investigation when an experiment behaves unexpectedly.
The bigger picture
Why feature-flag coverage needs a real query surface
Amplitude Experiments is built for high-velocity teams that ship multiple concurrent experiments and feature flags. The WordPress plugin handles the deployment key, identity bridging, and per-post flag assignments, which is the right scope. The unstated cost is that flag assignments never stop accumulating across releases.
A year in, the site carries dozens of _amplitude_flag_keys overrides, some retired flags still pinned to legacy URLs, and a handful of exclusions on account and legal pages with no documentation. The default plugin admin doesn't surface any of that, and reconciling production flag state with intended coverage requires SQL. SleekView treats the experiments options row and the per-post postmeta as one queryable surface.
Growth teams verify experiment coverage on real funnel pages. Ops teams confirm exclusions hold. Engineers diagnose flag-misfire bugs in seconds instead of hours.
Amplitude's experiment analytics and variant allocation stay in the Amplitude app where they belong. SleekView only makes the WordPress configuration legible at the scale a velocity-focused team actually runs.
Questions
Common questions about SleekView for Amplitude Experiments for WordPress
No. Flag evaluation happens in the Amplitude Experiments SDK on the client (or server SDK if configured). SleekView only reads the WordPress configuration in wp_options and per-post _amplitude_* postmeta, which controls which flags the SDK is told to evaluate on which pages.
No. The plugin writes the same option name and postmeta keys regardless of Amplitude Experiments plan tier. SleekView surfaces whatever the plugin has stored, free trial or enterprise.
Yes. Filter to the funnel post type or URL pattern, select matching rows, and bulk-edit _amplitude_flag_keys to remove the retired key. Updates write through update_post_meta and the SDK stops evaluating the flag on those pages.
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 a growth analyst can see flag coverage across all pages without access to the global Amplitude settings or other plugin areas.
Amplitude Experiments needs a stable identifier to bucket users into variants. The plugin bridges identity from a configured field (often user_id or device_id). SleekView surfaces the active bridge field as a column so engineers can verify the bridge is consistent across pages.
No. The grid paginates against the existing wp_postmeta meta_key index and only queries when opened. Saved views never preload, and the SDK's flag evaluation continues to run independently on the front end.
Yes. Each subsite has its own amplitude_experiments_settings option and its own per-post overrides. SleekView respects the active site context, so per-subsite experiment audits stay self-contained.
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.
Lifetime ♾️
Most popular
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
€749
Continue to checkoutBrowse more
- Surecart Checkout
- Wcfm Vendor Verification
- Paystack Woocommerce
- Edd Software Bundles
- Woocommerce Wishlists
- Linnworks Wp
- Woocommerce Ebay Integration
- Woocommerce Order Status Control
- Woocommerce Correos
- Woocommerce Gocardless
- Razorpay For Woocommerce
- Woocommerce Splitit
- Aelia Currencyswitcher
- Woocommerce Bambora
- Woocommerce Marketplace Stripe Connect