Translation analytics
Understand live-stream sessions, listening demand, translation pipeline health, recordings, and restream usage.
Video placeholder
Add a localized screen recording here: select a range, read the session table, distinguish streaming data from pending listener instrumentation, and inspect pipeline latency.
Open /analytics/translation. This view combines completed streaming-session records with event-based translation and audience instrumentation.
Session KPIs
- Sessions: completed streaming sessions started in the selected range.
- Streaming minutes: the sum of recorded session durations in the selected range.
- Average length: total streaming minutes divided by sessions, rounded to a whole minute.
- Peak listeners: the highest recorded peak listener count among sessions in the selected range.
- Recording minutes: recording usage from the latest current billing-period usage row.
- Restream minutes: restream usage from the latest current billing-period usage row.
The recording and restream cards are usage context, not historical totals for the selected analytics range.
Streaming calendar and recent sessions
The streaming calendar always covers one year and shows minutes per day. The recent-sessions table reads sessions from the selected range, orders them newest first, and displays up to ten rows in the dashboard. Each row contains the room, start time, duration, and peak listeners.
The peak-listener chart uses the sessions returned for the selected range. With fewer than two sessions, the dashboard shows the no-data state instead of a trend.
Language demand
Language demand is event-based. It reports:
- Listeners: unique listener identifiers per translation language.
- Subscriptions: the number of language-subscription events.
The dashboard can show up to twenty language entries. A language name here is the value recorded by the translation listener event; it is not a promise that the language is currently enabled for every plan or room.
Listener activity and audience curve
The listener punchcard counts stream-viewer joins by weekday and hour. The latest-session audience chart shows joins and leaves minute by minute for the most recent session found in the last seven days.
These panels depend on event instrumentation. They can remain empty even when the completed-session KPIs contain data.
Pipeline health
Pipeline health reports:
- Translation agent sessions started.
- Translation sessions that failed.
- Average latency in milliseconds.
- p95 latency in milliseconds.
Latency values come from completed translation-session events. They describe the observed translation pipeline, not the network latency of every listener.