Kissmetrics WP integrations typically write tracked event definitions to a custom post type such as kissmetrics_event or to wp_options entries when the plugin is lightweight. Identity aliasing rules (mapping logged-in user IDs to Kissmetrics person IDs) often live in wp_postmeta, and per-user identity state is stored in wp_usermeta under a key like _km_person_id.

The default admin for these integrations shows tracked events as a basic list with title and trigger type. Critical context like the property payload mapping, the conditions under which the event fires, the WordPress hook it listens to, and how many times it has actually been recorded since release lives in meta and never surfaces as a column. Identity mapping rules are usually editable only one record at a time.

SleekView reads the Kissmetrics integration's custom post type plus the supporting wp_postmeta and wp_usermeta rows. Event name, trigger hook, conditions, property mapping, last fire timestamp, and identity-alias status all appear in one row. Edits route through the integration's own save hooks so any required cache or queue invalidation continues to run.

Event tracking decays. The first version of a Kissmetrics integration is set up carefully, every event matches the spec, and the funnel reports cleanly for a quarter. Then a theme update changes the checkout hook, a Woo refactor reorders the order-status flow, a content team adds a new opt-in form with no events, and the analytics person who knew the system leaves.

A year later the funnel reports look fine until someone notices that no signup events have fired since the last release, or that authenticated users are silently being counted as new visitors because the identity alias hook stopped running. Most Kissmetrics WP integrations expose their event configuration as a basic admin list with no way to see fire counts, trigger hooks, or identity coverage at a glance. SleekView treats the integration's records as the structured data they actually are.

Event posts, property mappings, trigger conditions, fire counts, and identity aliases become joinable columns. Product analysts catch dead trackers before the next funnel review, QA validates every relevant trigger in a single grid, and growth teams audit identity stitching across the user base. The result is event tracking that stays honest as the site evolves.