Yes. Icegram stores impression and click counts in meta on each message (or, on some versions, a separate stats source). SleekView reads those keys directly and uses them as the source for the chart cards. No parallel tracking, no shadow tables.

Yes. CTR is a computed column derived from clicks and impressions at query time. Add it to a Bar grouped by message or message type and the ranking sorts on the derived value the same way it does on a raw column.

Cards read live from the Icegram tables on each dashboard load. New impressions and clicks reflect within minutes of the message firing. There's no scheduled rollup or aggregation between Icegram recording a counter and the chart moving.

SleekView reads what's in your install. Pro features (A/B variants, advanced targeting, additional message types) store data alongside the core post types. They become more rows and more dimensions to chart. Free-tier installs have less data; the same dashboard pattern works against either.

Yes. Click any chart slice and the SleekView messages table opens filtered to that segment. A low-CTR row becomes an inline-pause; a high-volume message becomes a promotion-queue candidate. Strategic surface and row-level ops on the same screen.

No. SleekView runs in wp-admin or a frontend embed surface, separate from Icegram's runtime. Chart queries hit indexed columns on posts and postmeta. For installs with hundreds of historical messages, scope the default to active or last-90-days to keep things lean.

Yes. SleekView dashboards are gated by WordPress capability. A marketing role sees the performance dashboard without holding broader plugin admin. Frontend embed works for stakeholder views without the wp-admin chrome.

No. The editor remains the place to design messages and configure rich display rules. SleekView Charts is the strategic dashboard over the data Icegram already produces. Inline pause and meta edits live on the SleekView table; design changes still belong in Icegram.