Amplitude WP Pro is a thin integration: it stores its event-mapping configuration in wp_options under keys like amplitude_event_map, and it decorates each shop_order with relay metadata in wp_postmeta (event ID, user ID, relay status). The actual events live in Amplitude's hosted product, but every decision about which WordPress action becomes which Amplitude event lives locally.

The plugin's settings page lists the mappings one at a time. To audit whether all WooCommerce events relay, or to find orders whose conversion event did not fire, operators export Amplitude data and manually join to wp_posts (post_type=shop_order) in a spreadsheet.

SleekView treats the wp_options mapping rows and the WooCommerce postmeta as two coordinated sources. A mapping grid shows each WordPress hook, the target Amplitude event, the user property mapping, and a last-relay timestamp. A conversion grid shows orders with relay status, event ID, and source. Edits to mapping options route through the Amplitude WP Pro settings API, so no rogue option writes occur.

Amplitude WP Pro is the kind of integration where every event sent to Amplitude depends on a row of configuration sitting quietly in wp_options. The settings page renders that configuration one mapping at a time, which works for setup but fails for audit: there is no way to see at a glance whether the Order Completed mapping has fired in the last hour, which mappings are sampled, which are disabled, or which conversions never relayed at all. Data engineers and product analysts end up exporting from Amplitude, joining to wp_posts in a spreadsheet, and reverse-engineering the mapping.

SleekView treats the wp_options configuration and the wp_postmeta relay metadata as a coordinated dataset. The mapping grid surfaces every hook and target; the conversion grid surfaces every order with its relay status. Inline edits route through the plugin's own settings API, so nothing rogue is written.

The black-box feel of a thin tracking integration becomes a queryable surface, and the audit work that used to live in a spreadsheet lives in WP Admin where the team already works.