Leads route to Monster Leads (OptinMonster's cloud lead store) or directly to integrated ESPs like Mailchimp, ConvertKit, or ActiveCampaign. They are not stored in your WordPress database — SleekView is honest about that and does not pretend to mirror cloud lead data.

The WordPress plugin caches campaign metadata, last-sync timestamps, and integration state in wp_options and plugin-specific cache structures. SleekView turns that into a filterable inventory of your campaigns, their sync health, and where their leads route — the WordPress half of the story.

SleekView reads what the OptinMonster plugin already stores locally. If you want to see Monster Leads contents directly, that's the OptinMonster app — we don't re-implement it. Adding a separate API integration would create a stale mirror without solving the actual ops problem.

If campaigns are tagged or named per page, you can filter the campaign view by name and see which campaigns target which URLs. The opt-in records themselves live in Monster Leads. The local view answers "which campaigns target this URL" without answering "who opted in" — that question lives in the cloud.

Inline edits in SleekView only touch the WordPress-side cache (e.g. a local note column or a local-only tagging system). Campaign settings still need to be edited in OptinMonster's app. We do not pretend to be an OptinMonster editor — that path leads to broken state.

Because most teams need to inventory and audit which campaigns are live, where they route, and when they last synced — without opening another app every time. That's exactly what the local cache view solves. It also catches sync staleness that the cloud UI cannot, because the staleness is on the WordPress side.

Yes. OptinMonster stores exclusion rules and post-targeting rules locally as part of the campaign cache. SleekView surfaces those as columns or as a separate joinable view, so the question "which campaigns are excluded from /checkout" becomes a one-screen filter.

Save a view filtered to last_sync older than 48 hours. Campaigns deleted in OptinMonster's app stop receiving sync updates and become stale on the WordPress side. The filter surfaces them — that triggers a manual cleanup of the WordPress cache to avoid showing a campaign that no longer exists in the cloud.