The Lucky Orange WordPress plugin saves its site ID, post-type allowlist, and trigger rules to wp_options under lo_options. Per-post exclusions write to wp_postmeta as _lo_exclude, and the survey-attachment override saves as _lo_survey_id. The settings screen exposes only the global toggle and the site ID, leaving the per-post overrides invisible.

SleekView reads both the lo_options row and every post with a _lo_* override into one sortable grid. Tracking state, attached survey ID, and consent-gate plugin become real columns. Filters stack across post type, exclusion state, and survey ID, and bulk edits flow through update_post_meta so the script picks up the change on the next request.

Heatmaps, session recordings, surveys responses, and chat transcripts stay in Lucky Orange's cloud, which is where the analysts work. SleekView focuses on the WordPress configuration: who excluded which page, which survey runs where, and when each override last changed.

Lucky Orange's strength is its breadth: recordings, heatmaps, surveys, and live chat all in one cloud product. The WordPress plugin handles the front-end loader and a few per-post overrides, intentionally minimal. The trade-off is that the settings page never grows into an audit surface as the override decisions pile up across campaigns and compliance reviews.

A year in, the typical site carries dozens of _lo_exclude entries, a handful of orphaned _lo_survey_id attachments on retired landing pages, and a consent-gate setting nobody remembers configuring. SleekView treats the options row and the per-post postmeta as one queryable surface. Compliance reviewers can verify billing and account pages remain excluded.

Growth marketers can confirm campaign surveys live on the pages they were built for. Implementation consultants can answer diagnostic questions in seconds. Lucky Orange's analytics stay where they belong.

SleekView only makes the WordPress side of the integration legible at scale.