No. Icegram Express per-campaign reports stay in place and remain the right place for individual broadcast analytics. SleekView Charts adds the cross-cutting weekly dashboard the default screens do not assemble, so the two layers complement each other rather than competing.

Yes. The source column in ig_contacts records where each subscriber came from (WPForms, manual import, WooCommerce checkout, comment opt-in). A Bar card grouped by source ranks acquisition channels across any time window for direct comparison of where signups actually originate.

Yes. The ig_actions table logs each open, click, unsubscribe and bounce event with subscriber_id, campaign_id and created_at. Build per-campaign opens-over-time Area cards and overall clicks-by-day Line cards alongside the subscriber-growth cards on the same dashboard.

Yes. A dashboard-level filter on list_id applies to every chart card. A single "Newsletter list only" or "Customer list only" filter recasts the entire dashboard for a per-list health check, useful for sites managing several distinct audiences in one install.

Yes. Aggregations run on the indexed columns ig_contacts and ig_actions already maintain. Sites with hundreds of thousands of subscribers and millions of action rows render the four-card dashboard in seconds without scanning meta or rebuilding any indexes.

Yes. Each chart card exposes its underlying row set, which exports to CSV with the active filters applied. That gives marketing a clean handoff to ad platforms or board reports without round-tripping through a manual export from the Icegram Express admin screens.

Yes. Each subsite has its own Icegram Express tables, and SleekView Charts reads the current subsite's data by default. Network-wide dashboards can be configured explicitly when reporting needs to span multiple subsites, with the join layer joining per-site tables in one view.

Yes. The WooCommerce integration links orders to subscribers via the email column, and SleekView joins on that key. Build a Sum card on order total grouped by ig_lists.name to see which subscriber list is contributing the most downstream revenue across the trailing time window cleanly.