No. Icegram's editor remains the place to design messages and configure detailed display rules. SleekView is a list-and-edit surface over the data Icegram stores — campaigns, messages, meta, counters. It's faster for review, monitoring, and toggling state; rich design changes still belong in the Icegram editor.

Icegram registers custom post types for campaigns and messages, with display rules in postmeta and counters either in meta or a separate stats source depending on version. SleekView reads each like any database source, joining campaigns to messages on the post-parent relationship and exposing meta as columns.

Yes. Click-through rate is a derived column computed from impressions and clicks at query time. SleekView lets you define computed columns once and use them in sort, filter, and group operations across the whole view — no need to bake the rate into a meta key.

Yes — that's the point. Toggling status writes through Icegram's update flow so the message's display logic reads the new state on the next page load. Any caching layer that listens for post updates invalidates relevant pages; manual flushes aren't required for the change to propagate.

Yes. Display rule serialised meta is parsed by SleekView into a targeting-type column (page, post type, URL pattern, traffic source). Use it as a filter to see all messages targeting the pricing page, all that fire only on logged-out visitors, or all that scope to mobile only.

SleekView reads what's in your install. Pro features — A/B variants, advanced targeting, additional message types — store their data alongside the core post types. Those become more rows and more columns to choose from. Free-tier installs simply have less; the same SleekView config works against either.

Yes. SleekView is gated by WordPress capability. Define a marketing role with permission to view and toggle status on Icegram messages but not to access full plugin admin. They get a focused view to pause underperformers and promote winners without holding broader admin rights.

No. SleekView runs in wp-admin, not on the front-end. Icegram's runtime continues unchanged. Admin-side queries hit indexed columns on posts and postmeta; for installs with hundreds of historical messages, scope the default view to active or last-90-days to keep queries lean.