No. The Loops account stays authoritative for deliverability, IP reputation and account-wide analytics. SleekView Charts adds the WordPress-side send and engagement dashboard the connector itself does not provide, focused on per-template and per-stream activity rolled up neatly.

Yes. The Loopify webhook listener writes opens, clicks, bounces and complaints to a sibling events table. SleekView reads it and pairs the events with the send log to produce open-rate and click-rate cards per template across any chosen time window cleanly.

Yes. Bounce events arrive via webhook into the events table with bounce_type (soft, hard) and timestamp. A Pie card grouped by bounce_type shows the bounce-mix, and a Line card grouped by created_at day surfaces creeping deliverability issues before they affect sending reputation badly.

Yes. Each send-log row carries audience_id reflecting the Loops audience the contact belongs to. Dashboard-level filters apply to every card, so a single "VIP audience only" filter recasts the entire dashboard for a focused per-audience capacity and engagement audit run.

Yes. The send-log and events tables are indexed on created_at, template_id and status. Sites pushing tens of thousands of sends per day render the four-card dashboard in seconds without scanning meta or rebuilding any database indexes after the dataset is configured.

Yes. Each chart card exposes its underlying row set, which exports to CSV with the active filters applied. That gives marketing and ops a clean handoff for board reports without round-tripping through the Loops account-side export tools every time a review report is due.

Yes. The send-log and events tables are per-subsite by default. SleekView Charts reads the current subsite, and network-wide dashboards can be configured explicitly when reporting must span multiple subsites pointing at the same Loops account for cross-site totals reliably.

Yes. SleekView joins user_id from the send-log table to wc_orders.customer_id. A Sum card on order total grouped by template_id shows which Loops template drove the most downstream revenue, closing the loop between email send and order value cleanly across the trailing window.