Unique visitors, sessions, page views, bounce rate, device and browser breakdowns — collected by the same recorder script you already install. No second SDK, no cookie banner gymnastics, no sampling.
Visitor identification uses a rotating, anonymous fingerprint — no third-party cookies, no consent banner required for the basic plan in most jurisdictions.
Every counted session links to the actual recording. See not just that page views dropped on a route — see what users did before they bounced.
Sessions and page views update in the dashboard within seconds. Filter by URL, country, device, browser, or any custom metadata you've tagged.
Most teams stitch together two tools: Google Analytics for page-view counts and a separate session-replay tool to figure out why those numbers move. The result is two SDKs, two dashboards, two consent flows, and no way to jump from a metric drop straight into the recordings of the users who caused it.
Nevision counts visitors, sessions, page views, bounce rate, average session duration, and device/browser/country breakdowns out of the same script that powers replay, error tracking, and Core Web Vitals. One install, one bill, one dashboard — and every metric is one click away from the underlying sessions.
Plans scale with page views: 50,000/month on the free tier, 500,000 on Lite ($12/mo), 2.5M on Pro ($39/mo), and 15M on Business ($99/mo). Retention follows the same ladder as replay — 7, 60, 90, and 365 days. No sampling. No row-level surprises.
Visitor identification uses a daily-rotating anonymous fingerprint that doesn't cross sites and doesn't persist beyond 24 hours. That means no consent banner is required for analytics in most EU jurisdictions on the basic plan, while unique-visitor counts stay within a few percentage points of cookie-based tools like Google Analytics.
For teams that need stricter accuracy on returning visitors, set window.nevisionMeta = { user_id: "..." } after your own auth completes — every subsequent session from that user is tagged and counted as a return visit, with full session correlation across replay, errors, and logs.
One script tag in your <head>. If you've already installed Nevision for replay or errors, you're already done — analytics ships in the same bundle.
Every page view, session start, device, browser, country, and referrer is recorded automatically. Bounce rate and average session duration update in real time.
Filter the dashboard by any dimension. Drill from a metric into the underlying sessions, then jump straight into the replay of any individual visitor.
| Feature | Nevision | Plausible | Fathom | Google Analytics |
|---|---|---|---|---|
| Free plan page views/month | 50,000 | — | — | 10M |
| Starting price | $0 | $9/mo | $15/mo | $0 |
| Includes session replay | — | — | — | |
| Cookie-less by default | — | |||
| EU hosted | — | |||
| Bounce rate + session duration | ||||
| Device + browser breakdown | ||||
| Real-time hourly chart | ||||
| Data retention (paid) | 365 days | Unlimited | Unlimited | 14 months |
Comparison based on publicly listed pricing and features as of April 2026.
For most product teams, yes — for the metrics that matter (visitors, sessions, page views, devices, browsers, countries, bounce rate, session duration). Nevision doesn't try to replicate GA's marketing-attribution and goal-funnel features. If you need multi-touch attribution or e-commerce funnel analytics, keep GA alongside; otherwise, the recorder script alone is enough.
By default, no. Nevision uses a rotating, anonymous, non-persistent fingerprint to count unique visitors — no third-party cookies, no cross-site identifiers, no PII. This satisfies GDPR's 'strictly necessary' analytics carve-out in most EU jurisdictions. If you set a persistent user_id via nevisionMeta, that becomes a first-party identifier and you should disclose it in your privacy policy.
We hash a combination of IP, user-agent, and a daily salt to generate an anonymous visitor ID that resets every 24 hours. This counts a returning visitor on the same day as one unique, but a returning visitor a week later as a new one — accurate enough for trend analysis, never invasive.
Yes. Pro and Business plans expose a CSV export per dashboard view (sessions, page views, top pages, device breakdown, etc.) and a read-only API for piping aggregated metrics into your own data warehouse.
No. Nevision filters known bot user-agents and headless-browser fingerprints (Googlebot, Bingbot, Lighthouse, Puppeteer, Playwright, etc.) automatically. Your dashboards reflect real human visitors only.
Free: 50,000/month. Lite: 500,000. Pro: 2,500,000. Business: 15,000,000. Overage stops counting at the cap rather than billing surprise — you can upgrade mid-cycle with prorated pricing.
Yes. Call nevision.recordEvent('event_name', { ...metadata }) from your client code to log a custom event into the same session. Filter the analytics dashboard by event name to see which features drive engagement.