vTilt
By roleFoundersKnow what to fix firstMarketersSee what happens after the clickCMOsSee what your budget really buys
By businessSaaSTurn signups into active usersEcommerceSee why shoppers abandon cartsAgenciesProve your work to clientsEnterpriseOne customer record for every team
MeasureWeb AnalyticsFind where buyers leaveSession ReplaySee why they left, not just that they didAdsKnow what paid visitors do nextIntegrationsOne snippet feeds your stack
ThinkPeopleOne profile per customerCustomer MemoryvTilt remembers every visitorSite KnowledgeAnswers and audits from your own pages
ActAsk AIAnswers from real behaviorAI ChatChat that knows the visitorEmail CampaignsEmail from real visits
PricingWhy vTiltDocs
Docs / Realtime Dashboard
Getting Started
OverviewInstallInitializeIdentify usersTrack eventsLogout & resetVerify eventsCommon mistakes
Guides
Event forwardingReverse proxyRealtime dashboardSite knowledge
Frontend frameworks
Next.jsNuxt.jsVue.jsReactReact RouterRemixGatsbySvelte / SvelteKitAstroAngularTanStack StartDocusaurus
Backend frameworks
NestJSHonoCloudflare WorkersDjangoFlaskLaravelPhoenixRuby on Rails
Backend languages
PythonPHPRubyElixirGoJava.NET / C#Rust
Stack guides
Vue + PHP
API Reference
Browser SDK
Script bundlesAutocaptureWeb VitalsSession recordingChat widgetFeature readinessRemote configurationDebug logging
Node SDK
Install & setupCapture, identify & aliasContext & shutdownGlobal properties & opt-outError tracking
MCP server
Guides
OverviewAuthenticationOAuthAgent skills (prompts)AI intelligenceSite knowledgeGoogle AdsMeta Ads
Client setup
CursorClaude DesktopVS CodeCodex

Getting Started

OverviewInstallInitializeIdentify usersTrack eventsLogout & resetVerify eventsCommon mistakes

Guides

Event forwardingReverse proxyRealtime dashboardSite knowledge

API Reference

MCP server

On this page

On this page

  • Metrics
  • How it works
  • Debug View vs Realtime Dashboard
  • Access
DocsGuidesRealtime dashboard

Realtime Dashboard

Last updated July 22, 2026

Aggregated metrics for the last 30 minutes — active users, events per minute, top events, top pages.

The Realtime Dashboard shows aggregated metrics for your site in the last 30 minutes. Unlike the Debug View, which streams individual events, this dashboard focuses on high-level activity: active users, events per minute, top events, and top pages.

#Metrics

The dashboard provides four key metrics, updated every 5 seconds by polling ClickHouse.

MetricDescription
Active UsersUnique visitors active in the last 5 minutes, based on distinct IDs seen in recent events.
Events per MinuteA 30-minute chart showing the number of events ingested in each 1-minute bucket.
Top EventsThe 10 most common event names in the last 30 minutes, ranked by count with a visual bar.
Top PagesThe 10 most visited pages (by pathname) in the last 30 minutes, ranked by count.

#How it works

The Realtime Dashboard uses a different data pipeline than the Debug View.

  1. Events are stored in ClickHouse as they arrive (standard pipeline).
  2. Dashboard polls /api/analytics/realtime every 5 seconds via SWR.
  3. The API runs four parallel ClickHouse aggregation queries (active users, events/min, top events, top pages).
  4. Results are rendered as live-updating cards and charts.

#Debug View vs Realtime Dashboard

Debug ViewRealtime Dashboard
GranularityIndividual eventsAggregated metrics
Latency~1 second (SSE stream)~5 seconds (polling)
Data sourceRedis bufferClickHouse queries
Use caseDebugging & verifying integrationMonitoring site activity
Forwarding statusPer-event, per-destinationNot included

#Access

Both views are available in the project sidebar under the Realtime section. Any organisation member with project access can view them — no additional configuration is needed.

Note

The debug stream buffers events for 30 minutes. Events older than 30 minutes are automatically cleaned up. The Realtime Dashboard queries the last 30 minutes of ClickHouse data on every poll.

PreviousReverse proxyGuidesNextSite knowledgeGuides