No. The per-newsletter Tribulant analytics stay in place and continue to power individual campaign reviews. SleekView Charts adds the list-wide weekly dashboard that the default screens do not assemble on a single surface with shared filters.

Yes. newsletter_clicks records every link click with newsletter_id, subscriber_id, and URL. Group by newsletter_id for top campaigns or by URL for top-clicked links across the whole sending history.

Yes. Bounce and unsubscribe events land in newsletter_history with action codes. Group by date and filter by action to plot a rising bounce line before it affects placement on engaged subscribers.

Yes. Dashboard-level filters apply to every chart card. A single list filter scopes the whole dashboard via the subscriber-list pivot, so per-list dashboards become one-click switches rather than per-card reconfiguration.

Yes. Aggregations run on indexed columns Tribulant maintains, and the Charts engine uses pagination and indexed joins rather than scanning meta. Hundreds of thousands of subscribers and click rows render charts in seconds.

Yes. Each chart card exposes its underlying row set, which exports to CSV with active filters applied. The export feeds board reports, attribution dashboards, and ad platforms without spreadsheet round-trips.

Yes. Each subsite has its own newsletter_ tables and SleekView Charts reads the current subsite by default. Network-wide dashboards can be configured explicitly when reporting spans multiple subsites or brands.

Yes. Both editions use the same newsletter_ tables, so SleekView Charts works on either. Pro features simply add more columns and dimensions. The dashboard adapts to whichever edition is active without requiring a specific tier.