Mixpanel Pro for WordPress stores its event-mapping configuration in wp_options under keys like mixpanel_event_map and mixpanel_super_properties. Every identified user gets Mixpanel-side metadata mirrored into wp_usermeta, including the distinct ID, last-seen timestamp, and any super properties the integration tracks.

The plugin's settings page lists each mapping individually and there is no way to see which mappings recently fired, which user properties are stale, or which identified users never received an event. Most audits happen in Mixpanel JQL or in a spreadsheet built from a Mixpanel CSV export.

SleekView reads the wp_options mapping rows and the wp_usermeta user-property rows as two coordinated grids. Mapping rows expose source hook, target Mixpanel event, super property mapping, and last-fired timestamp. User rows expose distinct ID, last seen, identified flag, and any custom super property. Inline edits to mapping config route through the Mixpanel Pro settings API, never through raw wp_options writes.

Mixpanel Pro for WordPress works because two pieces of state live in WP itself: the event mapping in wp_options and the identified-user metadata in wp_usermeta. Both pieces are the source of truth for what Mixpanel actually sees, but neither is queryable from the plugin's settings page. The mapping screen shows events one at a time, the user audit happens in Mixpanel JQL, and any drift between WordPress accounts and Mixpanel profiles surfaces only when someone notices a missing person in a funnel.

SleekView treats the wp_options mapping and the wp_usermeta user properties as queryable grids inside WP Admin. The mapping grid shows every hook and target; the user grid shows every identified user with their plan, distinct ID, and last seen. Inline edits route through the plugin's settings API, so no rogue option writes occur.

The audit that used to mean opening a Mixpanel JQL panel becomes a saved view in WP Admin, which is exactly where the data lives anyway.