Rover Analytics
Read what Rover does for your visitors — visits, outcomes, goals, and feedback — starting the moment it's installed, with no tagging plan.
Measured out of the box
Once Rover is installed, measurement is on. Sessions, pages, navigation, engagement, Core Web Vitals, attribution, Rover activity, and AI traffic need no custom setup.
- Website activity — sessions, page views, engagement, acquisition channels, and Core Web Vitals (shown only for route/device groups with at least 10 samples).
- Rover activity — opens, prompts, completed runs, success rate, and friction signals inside the Rover UI.
- Guided visits — chapters completed, the outcome, blockers, and human handoffs, recorded when each guided visit ends. Every visit is one of four kinds: demo, onboarding, support, or task.
- Feedback — ratings visitors left after Rover helped them, interview answers, discussions, and notes.
The privacy boundary
Rover Analytics collects bounded semantic events, and only after the consent state you provide. It does not collect replay, DOM snapshots, selectors, form contents, keystrokes, raw identifiers, or IP fingerprints. Raw analytics events expire after 30 days; only bounded aggregates and scrubbed snapshots last longer. Optional conversation memory is a separate Audience setting and can retain short visitor-request excerpts under its own consent and retention policy.The tabs
Open Workspace → your site → Analytics. Ten tabs, one question each:
| Tab | What it answers |
|---|---|
| Overview | People, sessions, page views, goals, AI traffic — and the last 7 days of Rover activity. |
| Product | Adoption of your registered events: feature usage, DAU/WAU/MAU, activation, retention, account signals. |
| Funnels & journeys | Your saved funnels step by step, plus every journey's started → finished counts. |
| People & intent | On-demand visitor intelligence: personas, intent, buyer stage, objections, next steps. |
| Insights | Anomalies, conversion drivers, and segment changes — only when evidence clears a bar. |
| Data quality | Accepted vs. rejected events, freshness, coverage, and the privacy boundary. |
| Activity | Who interacted (human vs. AI), what visitors asked, top pages and tools, conversions, credits used. |
| Journeys | How each journey went — visit by visit, with blockers and handoffs, over a rolling window of the last 50 guided visits. |
| Visits | A visit log for 24h to all-time ranges. Pick a visit to see its steps. |
| Feedback | Reviews, interviews, discussions, and notes. |
Add goals and product events
Everything above works with zero tagging. The one thing worth adding is the business outcomes unique to your product. Open Data settings (top right of Analytics) → Measurement.
- Goals — the outcomes your team already names, such as booking a demo or completing checkout. Each goal is a tracking ID, a label, and an optional description.
- Product events — named actions, not raw clicks. Each event has an ID, a label, and a category: activation, feature, workflow, success, friction, error, revenue, or custom.
- Typed properties — an event can carry a short list of properties, each typed as boolean, integer, number, duration, currency, or enum (up to 50 allowed values). Free-form text is rejected on purpose.
You don't have to design this catalog yourself. Describe what matters in up to 2,000 characters and Rover drafts the measurement plan, or choose Suggest from my site. Drafts land in the same review fields — nothing is live until you save.
Funnels and retention
- Funnels — two to eight ordered steps, measured by person, session, or account, over a 1–90 day window. A toggle allows alternate paths. Account-scope funnels may complete across different people in one account.
- Activation — the first set of steps that means a person reached initial value, inside a 1–90 day window.
- Retention — the action that starts a cohort and the action that means someone returned, reported daily, weekly, or monthly.
- Annotations — dated markers (a launch, a campaign) your team may use to interpret trends, never to claim causation.
Every step in these reports must reference a registered goal or product event ID — Data settings refuses to save an unknown one.
Insights — and why they wait
The Insights tab reports only what the evidence supports. Thin data stays labeled as thin data; it is never dressed up as a finding.
- Anomalies start after 28 full days of history, and show only clear outliers: at least 20 expected events and a 20% swing.
- Conversion drivers require 50 people overall and 10 per comparison cell. Every result is labeled correlation, not causation.
- Segment contribution ranks changes across plan, lifecycle, channel, landing route, device, and product events — each segment needs at least 10 observations.
Send your own signals
Any page that has the Rover embed can report an outcome with one line:
rover('trackGoal', { goalId: 'demo_booked' })
rover('trackConversion', { label: 'signup', value: 49, currency: 'USD' })
rover('trackEvent', { eventId: 'report_created', properties: { pages: 3 } })- Goal IDs allow letters, digits, and
. _ : -, up to 80 characters. - Event IDs start with a lowercase letter and allow lowercase letters, digits, and underscores, up to 64 characters. Properties are boolean, number, or string.
- Each call returns
trueorfalse—falsemeans the call was a no-op: analytics is off, not attached yet, or the ID didn't pass the rules above.
Analytics counts registered goals and events only, so add the IDs in Data settings first.
Traffic that never runs JavaScript
AI crawlers and agents often fetch pages without executing scripts, so the browser collector never sees them. Optional server middleware covers them: in Data settings → Collection, create a server-only credential and install @rtrvr-ai/rover/analytics/server. It records bounded GET/HEAD metadata and never forwards raw IPs, cookies, request bodies, or arbitrary query values.
The credential is shown once
Store it when you create it — Rover will not show it again. You can rotate or revoke it at any time. Managed platforms without server middleware cover JavaScript-capable traffic only.What needs Rover Enterprise
The Product, People & intent, and Insights tabs — plus the funnel insight cards — run on on-demand visitor intelligence: personas, intent, buyer stage, objections, gaps, and recommended next steps, generated when you open an intelligence view or press Update now. This analysis is available for direct Rover Enterprise workspaces — an Enterprise subscription bought from Rover and bound to the site. Platform-billed and AppSumo workspaces are not eligible.
- Collection is unaffected — website analytics, goals, product measurement, and operational data continue under their existing settings on every plan.
- Deterministic rules run first; only scrubbed ambiguous signals go to managed text classification, and segments below 10 people are suppressed rather than guessed.
- Optional emergent clustering starts only once a site has at least 200 people.
- Account-level analysis starts once your site sends an anonymized account id with its events — see Audience for identity setup.