Encharge Pro is the paid tier of the Encharge WordPress plugin. It adds event-forwarding logs, richer per-form mappings to flows, and tag/segment writebacks. The extra surface area means more local state: the API token and capture script settings sit in wp_options as a serialized array, per-form flow mappings and tag rules live in wp_postmeta, and a rolling event log writes to an Encharge-managed log option keyed by request ID.

The default Pro UI shows event history one page at a time with a fixed filter set. There is no joined view that combines event rows with the form that triggered them, no filter for events whose flow target was archived in Encharge, and no way to spot consent-text drift across forms in a single screen. Multisite operators have no portfolio view, every subsite has to be checked separately even when the plugin is wired identically across the network.

SleekView reads each storage path directly and renders Encharge Pro as one workspace. Settings rows, form-bridge rows, and recent event rows live in the same table with joined columns for the form name, the target flow, the consent text and a status pill. Edits route through the plugin's options API where supported so existing Encharge webhooks and WordPress hooks continue to fire.

Encharge Pro is one of the more capable third-party WordPress integrations in the lifecycle category because it actually logs what it does locally. That log is the difference between debugging a delivery problem in minutes and debugging it in days, but only if it's accessible. The default Pro UI exposes the log behind paginated screens with a fixed filter set, which works for casual lookup and falls over the moment ops needs to answer a cross-cutting question like "which forms are still posting into the archived onboarding flow" or "how many events failed last week and what's the retry status".

Those answers are right there in wp_options and wp_postmeta, but only as serialized blobs that the plugin's own UI doesn't pivot into a workspace. SleekView's contribution is the pivot. Once the log and the form bridges and the settings row all share one table, every debugging question becomes a filter and every fix becomes a bulk edit.

For lifecycle teams that own the Encharge-side flows, the table doubles as a launch runbook. For agencies running Encharge Pro across multisite networks, the network roll-up makes portfolio audits a screenshot.