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

No. Contacts, journeys and analytics stay in the Freshworks SaaS, which is exactly where they belong. SleekView surfaces the WordPress half of the bridge: which event was sent, by which form, to which journey 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 produces one clean dataset with a source_plugin column for grouping.

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

No. SleekView queries options and postmeta on read, never on write. Identify calls and form bridges continue to flow through the Freshmarketer plugin's runtime path with no added work, which keeps visitor-facing latency unchanged.

Yes. The tracking flag is a boolean in the Freshmarketer 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 Freshmarketer 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 journey_id and event_name while ops sees the tracking-flag column, with each role saving its own filter presets on the Freshmarketer dataset.