SleekView for Mixpanel
Read the Mixpanel WordPress plugin's project token, event toggles, and super-property mappings directly. Each tracked event becomes a row with status, hook source, post type, and the last config change.
♾️ Lifetime License available
A project token in a field is not a tracking plan you can audit
The Mixpanel WordPress plugin stores a project token and a set of toggles for which WordPress events to forward: post published, user registered, comment posted, WooCommerce purchase, and similar hooks. The settings tabs confirm the plugin is wired up. They do not list every configured event, the hook each one fires on, or when the configuration was last touched.
SleekView reads the same plugin options and joins them with the WordPress posts and users tables. Each row is a tracked event, with status, hook source, post type the hook applies to, the super property attached, and the last option-modified timestamp. Filter by event name, hook source, or status, and the table updates without leaving WP Admin.
The same dataset powers the SleekView Charts coverage dashboard for Mixpanel, so a filter in the table view carries straight into the chart cards. Mixpanel keeps receiving events exactly as before, on the same hooks, with no extra front-end script.
Workflow
How SleekView reads Mixpanel plugin data
Pick the source
wp_posts and user-role data as one joinable source.
Compose the column set
Save and scope the view
Filter, sort, and export
Sample columns
A typical Mixpanel event coverage table
wp_options (Mixpanel plugin options) + wp_posts + wp_usermeta
| Event name | Status | Hook source | Post type | Super property | Last change |
|---|---|---|---|---|---|
| Post Published | Active | wp_insert_post | post | author_role | Apr 24 |
| Signed Up | Active | user_register | — | signup_source | Apr 22 |
| Purchased | Active | woocommerce_order_status_completed | shop_order | order_total | Apr 20 |
| Comment Posted | Disabled | comment_post | post | — | Apr 11 |
| Login | Unconfigured | wp_login | — | — | — |
Comparison
Default Mixpanel plugin settings vs SleekView
Default Mixpanel plugin settings
- Settings tabs confirm tracked events are enabled but do not list them as one set
- Hook source and post type are not surfaced per event in the admin UI
- Super-property and user-property mappings live on separate screens
- Configuration changes are invisible without an external audit log
- No way to export the active event set without writing custom SQL
SleekView
- Read directly from the Mixpanel plugin's project token and event toggles
- Per-event status, hook source, post type, and super property in one row
- Saved views per WordPress role for growth, analytics, and engineering
- Shared filters with the SleekView Charts coverage dashboard
- CSV export of the tracking-plan audit without leaving WP Admin
Features
What SleekView gives you for Mixpanel
Tracking plan as a list
Build one saved view per stakeholder: a growth view of active events, an engineering view of hook sources, a WooCommerce view of purchase mappings. Same plugin data, separate columns.
Precise event filters
Combine event name, hook source, status, and post type. Save the filter as a named view your team reuses every sprint review or tracking-plan audit.
Same data, two surfaces
The table view and the SleekView Charts coverage dashboard read the same Mixpanel plugin options. A filter in one applies to the other with no rebuild step.
Audience
Who uses SleekView for Mixpanel
Growth teams
Filter to active events and confirm every step of the tracking plan is wired up before opening a funnel report in Mixpanel. Catch a disabled event before the chart looks empty.
WooCommerce analytics
Filter to WooCommerce hook sources to see which purchase, add-to-cart, and checkout events are mapped and which are still unconfigured before launching a paid campaign.
Implementation engineers
Sort by last configuration change and trace a sudden drop in a Mixpanel event back to the plugin option that flipped, using the shared table view.
The bigger picture
Why Mixpanel implementations need an event list, not a settings tab
A Mixpanel project is only useful if the events arriving in it match the tracking plan, and a WordPress install is famously easy to drift from that plan. A plugin update toggles a default off. A staging clone keeps the dev project token live in production for a day.
An editor changes a custom post type slug and the matching event no longer fires. The Mixpanel plugin settings tabs cannot answer those questions in one screen, because they store configuration rather than coverage. SleekView turns the same plugin options into a table where each tracked event is a row, with hook source, post type, super property, and the last change in plain view.
Same options, same WordPress hooks, but an audit list a growth team or implementation engineer can actually act on.
Questions
Common questions about SleekView for Mixpanel
It reads the Mixpanel WordPress plugin's options (project token, event toggles, super-property mappings), the wp_posts table for post_type and post_status, and the option revision history. No Mixpanel service-account token is required for the table view.
No. SleekView reports on what the WordPress plugin is doing locally: which events are enabled, which hooks they fire on, and how the configuration has changed. Funnel and retention counts stay in Mixpanel, which is where they belong.
Yes. If your install adds custom event-to-hook mappings, SleekView lists them in the column picker so the audit table can show them alongside the Mixpanel plugin's defaults.
Yes. The table view and the SleekView Charts coverage dashboard share one dataset. A filter for one event name, one hook source, or one post type applies to both surfaces without a rebuild.
Yes. The Mixpanel plugin maps WooCommerce hooks (purchase, add to cart, checkout) to Mixpanel events, and those mappings live in the plugin options. SleekView reads them the same way it reads the core WordPress event toggles.
No. SleekView reads existing options and posts and never writes to the Mixpanel plugin's configuration. The plugin keeps forwarding events on the same hooks, with no change to identity, sampling, or session handling.
Yes. Each subsite stores its own Mixpanel project token and event mappings in its own options table. Network admins can build per-subsite tables or a network view scoped to specific blog IDs.
Yes. Any filtered set in the table exports to CSV with the visible columns. Implementation engineers use the export to attach a tracking-plan audit to a sprint review or release checklist.
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 checkout