No. Responses are cached for a configurable interval so you stay under your Pirsch API quota. A typical content dashboard refreshing daily makes a few API calls per day rather than one per pageload. The cache duration is set per view, so a real-time goal-tracking dashboard might use a 5-minute cache while a weekly content report uses a 24-hour cache.

Pages, referrers, devices, countries, and events are surfaced. Custom event filters work too. The Pirsch API exposes additional dimensions like screen resolution, OS, and browser, all of which can be added as columns. Goal completions and conversion funnels are accessible if your Pirsch plan includes them, since they share the same API surface.

Yes. Match Pirsch paths to WP post IDs to add author, category, or publish date as columns. The match runs on permalink comparison, so any post with a stable permalink can be enriched. Custom post types work the same way. Editorial teams use this to build content performance dashboards that show traffic by author or topic without leaving WordPress.

No. Pirsch is privacy-first by design and SleekView reads only aggregate metrics. The API never exposes individual visitor sessions, IPs, or identifying data. SleekView passes through the same aggregate-only model, so any view you build respects the same privacy guarantees Pirsch ships with. Even custom event reports operate at the aggregate level.

Yes. Frontend embedding plus role-based access lets non-admins view their dashboards. Editors get their content performance view, marketing leads get their campaign view, and ops gets the full picture, all gated by WordPress roles. No Pirsch login required for any of them, which removes the credential management overhead of giving every editor Pirsch access.

Yes. Configure multiple credentials and switch between sites or aggregate them into one report. Useful for agencies running ten or more client sites under one Pirsch account, or for operators with main and microsites. Each view picks which site to query, and reports can roll up across sites with site-name as a grouping column.

The view returns the cached data from the last successful API call and surfaces a warning that the cache is stale. This keeps the dashboard usable even during a quota issue, while making clear to viewers that the numbers are not live. Once the quota resets, the next refresh updates the cache and the warning clears. Configure cache duration generously to avoid hitting quota under normal use.

No, it complements it. The Pirsch dashboard is the source of truth and includes interactive features SleekView does not duplicate, like real-time visitor lists or detailed funnel breakdowns. SleekView is for the cases where Pirsch data needs to live inside WordPress: editor-facing reports, joined views with WP content, and role-scoped team dashboards. Most teams use both for different audiences.