Only the WordPress-side data the Iterable plugin already writes: identify and event rows from the local log, form-to-list mappings from wp_postmeta and settings from wp_options. Iterable users, templates and workflow definitions are not duplicated into WordPress.

No. Users, templates and workflows stay in Iterable, which is exactly where cross-channel logic should live. SleekView surfaces the WordPress half of the bridge: which event was sent, by which form, to which workflow and from which page.

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

Yes. Save a view scoped to workflow_id and the table narrows to a single workflow. The view can be shared with the lifecycle owner for that workflow 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 run through the Iterable plugin's runtime path with no added work, so visitor-facing latency stays unchanged.

Yes. The tracking flag is a boolean in the Iterable 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 Iterable plugin versions disable local event 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 workflow_id and event_name while ops sees the tracking-flag column, with each role saving its own filter presets on the Iterable dataset.