Reading analytics

Every play, stop, CTA click, form, and completion streams back from the player. Analytics turns those into answers.

Range and lane

Pick 7, 30, or 90 days and optionally one lane. The filters live in the URL, so a view can be pasted into Slack. The Free plan shows the last 7 days; Growth keeps everything.

KPIs

Plays (drives started), viewers (distinct people), completions, and leads, each with a sparkline and the change against the previous period of the same length. Click one to chart it.

The funnel — where people park

One bar per stop, in lane order, showing how many drives reached it. The biggest drop between two bars is where people park: that stop is too long, too early to ask for an email, or its hotspot is hard to find. Fix the stop, watch the bar next week.

Heatmap

Day × hour of plays. Useful for timing a send or a launch, and for spotting a bot (every hour, every day, identical counts).

Breakdowns

Sources, referrers, devices, countries, and accounts (from prospect links and lead companies). Per-lane totals when no lane is selected.

Prospects and recent drives

The prospect table shows each personalized link with its plays, depth, and outcome. Recent drives roll each session up into one row with an outcome chip — completed, CTA, lead, parked at stop n. The driving now chip counts sessions active in the last 30 seconds.

Export

Export CSV writes every series on the page for the current range and lane. For raw events use the API, or a workspace export under Settings → Workspace.

What can't be counted

Ad-blockers and very short drives can keep the player from reporting. Treat numbers as a floor, not a census.