Heap's auto-capture model trades upfront tracking-plan work for retrospective definition: capture everything, define events later. That trade only works if the snippet is actually present on the right surfaces. The Heap WordPress plugin stores an app ID, a role exclusion list, and a small set of toggles for which front-end templates skip the snippet. The settings screen confirms the plugin is wired up. It does not list every published URL with its auto-capture status, excluded role, and template.

SleekView turns the same plugin options into a table. Each published post or page is a row with auto-capture status, excluded role, post type, the template that rendered it, and the option-modified timestamp. Sort by status, filter to one excluded role, or scope to a post type and the table updates without leaving WP Admin.

The same dataset powers the SleekView Charts rollout dashboard for Heap, so filters carry between row-level audit and chart-level coverage on one shared source.

Heap's auto-capture model is generous: capture every click and pageview the snippet sees, define events later. The cost of a coverage gap is high, because an entire surface goes missing, not just one event. The Heap WordPress plugin keeps installation simple, which is correct, and keeps coverage invisible, which is the part that breaks quietly on real WordPress installs.

A new post type ships without the snippet allowed. A staging copy keeps the wrong app ID live in production for a day. A role-based exclusion expands and removes auto-capture for half the editorial team.

SleekView turns the same plugin options into a table where every published URL is a row, with auto-capture status, excluded role, template, and the last change in plain view. Same options, same WordPress hooks, but a list that catches a coverage gap before it shows up as a hole in a Heap funnel.