Snowplow is one of the few CDPs where schema is a first-class citizen. Every event is self-describing against an Iglu schema, every entity context is versioned, and the Snowplow WP integration stores its schema-to-event mapping in wp_options under snowplow_schema_map. WooCommerce orders, form submissions, and content interactions each get an _snowplow_event_id and _snowplow_schema row in wp_postmeta after relay.

The integration's settings page lists each schema mapping one at a time. To audit which schemas are pinned to which version, which events fired against a deprecated schema, or which orders never got a Snowplow event, operators end up running SQL against the Snowplow enriched events table.

SleekView reads the wp_options schema mapping and the per-row wp_postmeta as two coordinated grids. Mapping rows expose source hook, Iglu schema URI, version, and last-fired timestamp. Event rows expose the parent post or order, Snowplow event ID, schema, and version. Inline edits route through the Snowplow WP settings API so version pins stay validated.

Snowplow's defining feature is that schema is enforced at collection time: every event carries a self-describing Iglu URI, every entity context is versioned, and downstream consumers can trust the shape of the data they receive. That contract is only as strong as the schema configuration on the WordPress side, which lives in wp_options as a mapping between hooks and Iglu schema URIs plus version pins. Right now that configuration is opaque to anyone who is not a data engineer.

The settings page lists schemas one at a time, deprecated versions surface as debug.log warnings, and a per-order audit requires SQL against the Snowplow enriched events table. SleekView treats the wp_options schema mapping and the wp_postmeta event metadata as coordinated, queryable grids inside WP Admin. The schema audit, deprecated, stale, missing events, becomes a saved view.

Version pins stay validated by the plugin's own Iglu helper. The schema contract becomes legible to product analysts and compliance leads, not just to the engineer who deployed it.