SleekView for RudderStack WP: source mapping and destination tables
RudderStack WP stores source-mapping config in wp_options and writes user anonymousId values into wp_usermeta. SleekView reads both so warehouse-first CDP audits live inside WP Admin.
♾️ Lifetime License available
Audit warehouse-first CDP wiring without leaving WordPress
RudderStack is the warehouse-first alternative to Segment, and its WordPress integration writes the same kind of state to the same kind of places: source-to-event mapping in wp_options under rudderstack_event_map, identified-user anonymousId values in wp_usermeta as _rudderstack_anonymous_id, and destination filter mirrors in wp_options when the team has them enabled.
The plugin's settings page lists each mapping one at a time and any cross-cutting audit, which destination receives which event, which users are missing an anonymousId, what the sampling rates look like, requires a RudderStack SQL query against the warehouse or a CSV pulled from the RudderStack control plane.
SleekView reads the wp_options mapping and wp_usermeta identification rows as coordinated grids. Mapping rows expose source hook, target RudderStack event, destination filter, and last-fired timestamp. User rows expose anonymousId, userId, and last seen. Inline edits route through the RudderStack WP settings API so writes stay safe.
Workflow
From wp_options mappings to a working warehouse audit
Register the RudderStack sources
rudderstack_event_map and the destination filter mirror from wp_options, plus per-user _rudderstack_anonymous_id from wp_usermeta.
Compose audit columns
Save audit views
Edit inline
Sample columns
A typical RudderStack WP mapping view
wp_options (rudderstack_event_map) + wp_usermeta (_rudderstack_anonymous_id)
| Source hook | RudderStack event | Destinations | Warehouse | Last fired | Status |
|---|---|---|---|---|---|
| woocommerce_order_status_completed | Order Completed | BigQuery, Braze | Yes | 8s ago | Active |
| user_register | Signup | BigQuery, Customer.io | Yes | 3m ago | Active |
| wpforms_process_complete | Form Submitted | Braze | Partial | 1d ago | Sampled |
| comment_post | Comment Posted | — | No | — | Disabled |
Comparison
Default RudderStack WP admin vs SleekView
Default RudderStack WP admin
- Mapping settings page lists events one at a time
- Destination filters and warehouse status live in RudderStack's control plane
-
User identification audits require warehouse SQL against the
trackstable -
Failed identifies log to
wp-content/debug.lograther than a queryable list - Cannot expose a curated mapping view to a non-admin role
SleekView
-
Mapping config from
wp_optionsas a sortable, filterable grid -
Identified-user audit from
wp_usermetain the same UI - Filter Disabled mappings, Sampled mappings, or No warehouse in one query
- Inline edits route through the RudderStack WP settings API
- Per-role scoped views so engineering and analytics audit the same dataset
Features
What SleekView gives you for RudderStack WP
Warehouse-first audit
Each mapping row shows whether the event syncs to the warehouse, which destinations it routes to, and the last-fired timestamp. Find events excluded from BigQuery or Snowflake in one query.
Identification audit
Filter wp_users to the ones without a RudderStack anonymousId. The gap between WordPress accounts and RudderStack profiles becomes a saved view.
Settings-API writes
Edit mapping config, sampling, and destination filters inline. Writes go through the RudderStack WP options layer so validation and cache invalidation behave as designed.
Audience
Who uses SleekView for RudderStack WP
Data engineering
Audit every mapping and warehouse sync flag from one grid. Disabled mappings and broken warehouse routes surface as filterable rows.
Product analysts
Confirm warehouse-bound events match the analytics roadmap. Filter to Warehouse: No and surface events that should be syncing but are not.
Customer success
Verify a specific customer's anonymousId and userId from the user grid. Speeds up tickets about missing data in downstream tools.
The bigger picture
Why warehouse-first CDPs need a local audit grid
RudderStack's warehouse-first model is excellent when it works: every event lands in BigQuery or Snowflake, downstream destinations subscribe, and the same data powers analytics and activation. The catch is that auditing whether it works requires running SQL against the warehouse, which is a great tool for data engineers and a terrible tool for support reps, customer success, and most product analysts who just want to know whether a specific WordPress hook actually mapped to a specific RudderStack event last hour. The configuration that controls all of that lives in wp_options on the WordPress side, and the identification metadata lives in wp_usermeta.
SleekView treats both as queryable grids inside WP Admin. The mapping grid shows every hook, target event, destination list, and warehouse sync flag. The user grid shows every identified user with anonymous and user IDs.
Inline edits route through the plugin's settings API. The warehouse remains the warehouse, and the WordPress configuration finally has a UI worth using.
Questions
Common questions about SleekView for RudderStack WP
No. RudderStack remains the CDP and warehouse pipeline. SleekView covers the WordPress-side configuration audit: source mapping in wp_options and identification in wp_usermeta.
When RudderStack WP mirrors destination warehouse status into wp_options, yes. Status that lives only in the control plane cannot be read locally.
Yes. Writes route through the RudderStack WP settings API so validation, sanitisation, and cache invalidation match the native screen.
No. Queries paginate against existing indexes on wp_options and wp_usermeta. There is no background sync.
Yes. WooCommerce hooks like woocommerce_order_status_completed appear as first-class source hooks with their RudderStack event and destination list.
Yes. A view of wp_users joined to wp_usermeta on missing _rudderstack_anonymous_id surfaces the gap.
Yes. Both grids export with active filters and visible columns. Engineers use the export for dataops tickets and warehouse pipeline reviews.
Yes. Anonymous IDs and user IDs stored in wp_usermeta are subject to WordPress's privacy erase tools. Erasure clears the row from both grids.
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
- Woocommerce Wholesale Lead Capture
- Woocommerce Dynamic Pricing
- Woocommerce Taxify
- Woocommerce Hermes Shipping
- Woocommerce Side Cart
- Variation Swatches
- Woocommerce Recently Viewed
- Bigcommerce Bridge
- Authorize Net
- Currency Switcher
- Woocommerce Cart Abandonment Recovery
- Printify Integration
- Woocommerce Extra Options
- Woocommerce Low Stock Alerts
- Woocommerce Product Vendors