No. The free tables (views, sessions, referrers, devices, geo) are fully supported as soon as Independent Analytics is active. Pro features like UTM campaigns, custom events, and click tracking become available in SleekView when Pro is active. SleekView itself doesn't gate any column behind an upgrade; it surfaces whatever Independent Analytics has recorded.

Yes. SleekView assigns saved column sets and filter presets per role. An editor can be given a read-only view of their own author's posts, and a client can see a curated set of pages without any access to settings, plugin lists, or other data sources. The role check happens before the table query, so unauthorized columns are never even loaded.

No. SleekView reads existing rows from the iawp tables but never writes to them. Independent Analytics keeps recording visits exactly as it did before, on the same schedule and the same indexes. There is no extra script in the front end and no change to how sessions are stitched together.

Yes. Independent Analytics records to per-subsite tables when installed network-wide, and SleekView respects that boundary. Each subsite shows only its own analytics data, and a network admin can build views for individual sites or use a network-level view scoped to specific blog IDs.

Yes. Any saved view exports to CSV directly from the table header. The export honors the active filters, sort order, and visible columns, which makes it useful for monthly reports, slide decks, or further analysis in a spreadsheet without leaving the WordPress admin.

No. SleekView paginates against the existing iawp indexes and never loads more rows than the visible page. Heavy filters resolve in the database the same way Independent Analytics' own tabs do, and saved views don't pre-fetch anything until they're opened.

Yes when Independent Analytics Pro is active. Pro records UTM source, medium, and campaign on each session row, and SleekView pivots those into columns next to the page and post type. Filter to a single campaign and group by post to see which content the campaign actually drove sessions to.

SleekView reads from whatever Independent Analytics already filtered out. The plugin's bot exclusion list and IP exclusions still apply at the recording layer. If you want to inspect filtered traffic, you can build a view directly against the raw views table, but the default sources match the dashboard's clean numbers.