The Amplitude Events plugin embeds the Amplitude Browser SDK and lets editors define which events fire on which pages. The configuration sits in option rows like amplitude_events_options and amplitude_events_map, with per-post overrides in postmeta keys like _amplitude_events_extra and _amplitude_events_disable. Amplitude itself owns the recording and the charting in its own analytics workspace.

SleekView Charts reads the WordPress side and lets you build chart cards on top: a Number for posts where the Amplitude tag is disabled, a Donut for event type spread in the event map, a Bar for event coverage by post type, an Area for the rate of new event overrides added per month. Each card is a saved query against the live Amplitude option rows and postmeta, so the dashboard reflects today's event picture.

The SDK keeps firing the way it was configured. Amplitude still records the events, the analyst still runs queries in the Amplitude UI, and SleekView simply gives the WordPress team a way to see how the event integration is actually deployed across the site without scrolling through plugin settings.

Amplitude is excellent at querying events once they arrive, but it cannot see whether the event you defined is actually firing on the right pages. That picture lives in WordPress: option rows that hold the event map, postmeta keys that opt pages in or out. Without a dashboard those rows are invisible until something breaks.

SleekView Charts closes that gap by treating the Amplitude plugin option rows and override postmeta as a real dataset. Analysts see event coverage and override drift in one view, editors get a quick read of which post types carry events, and agencies hand product clients a saved coverage dashboard scoped to a client role. The SDK keeps shipping events to Amplitude, and the WordPress side finally has its own view of what is being shipped.