Analytics suite

Simple terms

Analytics shows what visitors and tests are doing across the store: realtime events, traffic, funnels, flow, visitors, revenue, and measurement quality.

Store-wide and experiment-aware reporting across visitors, conversions, revenue, ecommerce, traffic, funnels, journey flow, realtime events, and measurement quality.

Routes

• /analytics
• /analytics/audience
• /analytics/traffic
• /analytics/visitors
• /analytics/realtime
• /analytics/funnels
• /analytics/funnels/new
• /analytics/flow

Implementation behavior

• The SDK and Worker send normalized events into the Tinybird events datasource.
• Dashboard APIs proxy Tinybird pipes and combine them with Prisma context for shop, experiment, and goal names.
• Realtime views query recent events to verify install, pageview, custom event, and QA traffic.
• Funnels use detected pages or saved funnel steps to compute conversion and drop-off.
• Visitor explorer reads sessions and event trails for individual debugging.

How to use it

• Use Overview for business-level health and experiment summaries.
• Use Realtime immediately after installation or QA.
• Use Traffic and Audience to understand quality and targeting context.
• Use Funnels and Flow when the question is journey movement rather than one metric.
• Use Visitors to debug one visitor, session, or identifier.

When not to use it

• Do not use store-wide analytics to make a variant decision without opening the experiment-level report.
• Do not use Realtime as long-term reporting; it is mainly for debugging fresh events.
• Do not trust funnel results until page detection and URL normalization are checked.

Implementation source

• Pages live under src/app/(dashboard)/analytics and its child routes.
• Handlers live under /api/analytics/*, including /api/analytics/realtime and /api/analytics/semantic/*; detected pages are read from the Tinybird detected_pages pipe.
• Tinybird pipes and datasource definitions live under packages/tinybird.

Data and API

• Tinybird datasource: events with shop, visitor, session, user, event type, experiment, variation, URL, properties, device, country, timestamp.
• Pipes include dashboard_stats, experiment_visitors, experiment_conversions, experiment_timeseries, and detected_pages.
• APIs under /api/analytics/*, including /api/analytics/realtime and /api/analytics/semantic/*.

Failure modes

• Realtime empty: SDK not installed, wrong shop ID, Worker error, or blocked network call.
• Funnels incomplete: detected pages have not accumulated enough events or URL normalization differs.
• Experiment report blank: experiment IDs or variation IDs are missing from tracked events.