SleekView for Segment WP Pro: event source and destination mapping tables
Segment WP Pro stores source and destination mapping in wp_options and decorates identified users with wp_usermeta anonymous IDs. SleekView surfaces both so audits stop requiring a Segment Functions deploy.
♾️ Lifetime License available
Audit Segment mapping where it actually lives
Segment WP Pro is the WordPress bridge for Segment's CDP. The plugin stores its source-write-key, event-mapping, and destination filter configuration in wp_options under keys like segment_event_map and segment_destination_filters. Every identified user gets a Segment anonymousId and userId mirrored into wp_usermeta.
The settings page lists each mapping one at a time, and any audit, which destination receives which event, which event is sampled, which users never got identified, happens in Segment's hosted product behind another login. Operators end up writing Segment Functions or running Personas queries to answer questions that are really WordPress configuration questions.
SleekView reads the wp_options mapping and the wp_usermeta identification rows as two coordinated grids. Mapping rows expose source hook, target Segment event, destination filter, and last-fired timestamp. User rows expose anonymousId, userId, last-seen, and any trait property mirrored locally. Inline edits route through the Segment WP Pro settings API so nothing rogue is written to wp_options.
Workflow
From wp_options mappings to a working audit grid
Register the Segment sources
segment_event_map and any destination filter mirror from wp_options, plus per-user anonymousId and userId from wp_usermeta.
Compose audit columns
Save audit views
Edit inline
Sample columns
A typical Segment WP Pro mapping view
wp_options (segment_event_map) + wp_usermeta (_segment_anonymous_id)
| Source hook | Segment event | Destinations | Last fired | Sampling | Status |
|---|---|---|---|---|---|
| woocommerce_order_status_completed | Order Completed | GA4, Braze | 12s ago | 100% | Active |
| user_register | Signup | GA4, Mailchimp | 3m ago | 100% | Active |
| wpforms_process_complete | Form Submitted | Braze | 1d ago | 50% | Sampled |
| comment_post | Comment Posted | — | — | 0% | Disabled |
Comparison
Default Segment WP Pro admin vs SleekView
Default Segment WP Pro admin
- Mapping settings page lists events one at a time
- Destination filters live in Segment's hosted product, outside WordPress
- User identification audits require Segment Personas or a JQL-style query
-
Failed identifies log to
wp-content/debug.lograther than a queryable list - Cannot share a curated mapping view with a non-admin role
SleekView
-
Every source-to-Segment-event mapping from
wp_optionsin one grid -
Every identified user with
anonymousIdanduserIdfromwp_usermeta - Filter Disabled mappings or Sampled below 100% in one query
- Inline edits route through the Segment WP Pro settings API
- Per-role scoped views so engineers, analysts, and ops audit the same data
Features
What SleekView gives you for Segment WP Pro
Source-to-destination map
Each row shows a WordPress hook, the Segment event it becomes, the destinations it routes to, and the sampling rate. Disabled mappings, sampled mappings, and active mappings all surface in one view.
Identification audit
Filter wp_users to the ones without a Segment anonymousId in wp_usermeta. The gap between WordPress accounts and Segment profiles becomes a saved view.
Settings-API writes
Edit mapping config and sampling rates inline. Writes go through Segment WP Pro's options API so validation and cache invalidation match the native settings screen.
Audience
Who uses SleekView for Segment WP Pro
Data engineering
Audit every event mapping and every destination filter from one grid. Disabled mappings, low sampling rates, and stale identifies surface as filterable rows.
Product analysts
Confirm the events powering a Personas audience are mapped and active. Filter the mapping grid to the audience's events and verify last-fired timestamps.
Customer success
Check whether a specific customer ever got identified into Segment. anonymousId and userId sit on the user row, so the answer is one filter away.
The bigger picture
Why CDP configuration needs a local query interface
Segment's whole value is being the CDP layer between data producers (WordPress events, app events, server events) and destinations (analytics warehouses, email tools, ad platforms). The WordPress-side of that contract lives in two places: a mapping configuration in wp_options and an identification record in wp_usermeta. Both are the source of truth for what Segment sees, but neither is queryable from the plugin's settings page.
Audits and gap analyses happen in Segment Personas or in a Segment Function, even when the question, which WordPress event is mapped to which Segment event, is a WordPress question. SleekView treats those wp_options and wp_usermeta rows as queryable grids inside WP Admin. The mapping grid shows source, target, destinations, sampling, and last fired.
The user grid shows anonymous and user IDs alongside last seen. Inline edits route through the plugin's settings API. The configuration that powers Segment finally has a workable UI exactly where it actually lives.
Questions
Common questions about SleekView for Segment WP Pro
No. Segment remains the CDP. SleekView covers the WordPress-side configuration audit: source mapping in wp_options and identification in wp_usermeta.
When Segment WP Pro mirrors destination filters into wp_options, yes. Filters defined only in Segment's hosted UI cannot be read locally because the data does not live in WordPress.
Yes. Writes route through the Segment WP Pro settings API so validation, sanitisation, and cache invalidation match the native screen.
No. Queries paginate against existing indexes on wp_options and wp_usermeta, the same way the plugin's own admin does.
Yes. WooCommerce events like woocommerce_order_status_completed are first-class source hooks. The mapping grid lists them with their target Segment event and destination filter.
Yes. A view of users with no _segment_anonymous_id postmeta surfaces the identification gap. Engineering teams use that view to triage identify-call failures.
Yes. Both grids export with active filters and visible columns. Engineers use the export for dataops tickets and product reviews.
Yes. anonymousId and userId 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
- Flexible Shipping
- Automatewoo
- Woocommerce Paymongo
- Yith Woocommerce Points And Rewards
- Edd Fes Frontend Submissions
- Woocommerce Invoice System
- Woocommerce Grouped Products Pro
- Payu Money Woocommerce
- Woocommerce Advanced Flat Rate Shipping
- Woocommerce Distance Rate Shipping
- Woocommerce Tiktok Pixel
- Woocommerce Cybersource
- Woocommerce Follow Up Emails
- Woocommerce Services
- Woocommerce Rewards Points