Only the WordPress-side data the Customer.io plugin already writes: identify and event rows from the local log, form-to-campaign mappings from wp_postmeta and settings from wp_options. Customer.io people and journey definitions are not duplicated into WordPress.

No. People, journeys and campaigns stay in Customer.io, which is exactly where lifecycle logic should live. SleekView surfaces the WordPress half of the bridge: which event was sent, by which form, to which campaign and from which page.

Yes. The plugin writes bridge mappings to each form plugin's standard postmeta location, and SleekView reads all of them. A mixed-form site still produces one clean dataset with a source_plugin column for grouping.

Yes. Save a view scoped to campaign_id and the table narrows to a single campaign. The view can be shared with the lifecycle owner for that campaign so they open straight into the right slice.

No. SleekView queries the option store and postmeta on read, never on write. Identify calls and form bridges continue to flow through the Customer.io plugin's runtime path with no added work, so visitor-facing latency stays unchanged.

Yes. The tracking flag is a boolean in the Customer.io settings option. SleekView surfaces it as a column, which makes mismatches between staging and production visible on a multisite roll-up without leaving the table.

Some Customer.io plugin versions disable local logging by default. SleekView shows an empty state on the event rows in that case, and the mapping columns over wp_options and wp_postmeta keep rendering so the view stays useful for audit work.

Yes. Each saved view is scoped by WordPress capability. Lifecycle sees campaign_id and event_name while ops sees the tracking-flag column, with each role saving its own filter presets on the Customer.io dataset.