ConvertBox Pro embeds personalised opt-in boxes via a WordPress integration that stores embed campaigns as a custom post type with rich wp_postmeta targeting rules: URL filters, visitor segments, device, source, and goal. Account-level configuration lives in wp_options. Local conversion logging (when enabled) writes to a separate CPT with referrer, segment, and timestamp meta. The authoritative conversion analytics live on ConvertBox's upstream dashboard.

The default plugin admin renders one campaign at a time. Cross-cutting questions like "which campaigns target the pricing page" or "which segments fire most often" require opening each campaign to inspect its targeting meta. Bulk pause, audience swap, and per-segment audit live outside the default screens. Per-page conversion attribution (when local logging is on) needs SQL because the join between the log CPT and the campaign CPT isn't a default view.

SleekView reads the campaign CPT, the log CPT, and the relevant wp_options keys, and pivots their wp_postmeta values into named columns: URL filter, segment, device, goal, status. Targeting audits become saved views; bulk pause becomes inline; per-page attribution becomes a join that updates as the log grows.

Conversion personalisation lives or dies by targeting precision. ConvertBox Pro stores targeting in wp_postmeta on a CPT and renders one campaign at a time, which works well for editing but leaves teams without a workspace for the cross-campaign questions optimisation work actually requires. The data sits there: URL filter, segment, device, goal, status, all as filterable meta.

SleekView promotes those keys to columns so optimisation leads see overlap and gaps at a glance. Marketing ops gets bulk pause and audience swap without opening campaigns one at a time. Growth analysts get per-page attribution by joining the log CPT with the campaign CPT on campaign id.

The runtime engine continues to operate exactly as before; only the audit and cleanup workflows change. Teams running dozens of campaigns across pricing, blog, and product pages stop losing conversions to overlapping or stale targeting because the workspace makes the configuration legible at a glance instead of buried inside per-campaign edit screens.