Analytics tell you whether your audience could follow your event in a language they understand: how many people listened, in which language, how, and for how long. They count people, never name them.
A session's analytics
On the session's page, open Analytics. You need a role that can read analytics.
- The top line sums up the session, for example how long it ran, how many people listened and across how many languages.
- What to show switches the chart between Listening (people on each channel over the session), Arrivals (when people first opened a channel) and Captions (what each channel published, minute by minute; a gap is a channel that went quiet).
- How people listened splits each channel's audience into Room audio (the floor, an interpreter or the AI voice), Browser voice (the listener's own browser reading captions aloud) and Captions only.
- People counts distinct browsers that opened a channel; one browser counts once however often it reconnected. Connections counts every connection, each time.
- Languages published counts the languages that actually produced captions, whatever was planned.
Select How we count next to a figure for the exact rule.
Your portal's audience
For everything listed on one portal, go to Portals, open the portal and select Audience. Choose a Period to see:
- People who listened, compared with the period before.
- Time spent listening, and how long people typically stay.
- Languages chosen, out of those you offered, and Which language people chose. A language nobody chose is one you could stop offering.
- When people join, in minutes from the start. If many arrive late, the page suggests opening the channels five minutes early.
- Every event on this portal, with who listened, the typical stay and the languages chosen.
