Listener joins
How often the audience connected.
Observed joins can include return visits. They are not a count of distinct people.
Audience reports
Understand how your multilingual audience joined, which languages they needed and when participation was strongest. Bring a clear account of the event back to your team.
Open Reports in the consoleFrom activity to understanding
Open Reports → Statistics for audience participation. Choose a date range, timezone and available event filters within your permissions.
Explore daily and hourly patterns, compare language demand and review event breakdowns. Use Activity & costs separately for translation usage and billing.
Understand the measurements ↓Audience report
Executive summary first. The detail behind it.
Joins · unique browsers · peak presence
Languages · events · daily and hourly patterns
Coverage · estimates · measurement notes
Four useful perspectives
How often the audience connected.
Observed joins can include return visits. They are not a count of distinct people.
Identified browsers across the period.
A saved anonymous browser identifier groups repeat activity. Different devices or cleared storage can count again; a shared browser can represent several people.
The busiest observed moment.
Presence is sampled. The highest observed concurrent audience is an estimate, not a verified headcount.
A view of listening presence over time.
Minutes are estimated from observations. They do not prove anyone heard the audio and are separate from billed translation time.
Go beyond a total
Review which audience languages were used and how demand changed over the selected period. Event breakdowns help put the observations in context.
Unique Listeners Only deduplicates identified browsers across the selected period, including repeat language and event activity. Unidentified observations and older aggregate records are excluded from this view.
Daily and hourly views help identify busy periods. Supported details include observed days, average presence, daily changes, busiest periods and language reach.
Ready for the follow-up
Choose the reporting dates, timezone and event filters. Review the coverage notes before interpreting the result.
Create a Salam.AI-branded report with an executive summary, key figures, breakdowns and measurement notes. Add optional event name, date, purpose and location labels.
Use your browser’s print dialog and Save as PDF for the executive report. Export CSV for all rows returned in the currently loaded report.
Detailed sections are optional. Each detailed table in the on-screen and PDF views previews up to 200 rows. CSV includes all rows returned in the loaded report, rather than only that preview. Optional event fields label the report; they do not change its data filters.
Detailed audience attendance began on 8 October 2026. Older saved broadcast records may contribute visits, runs, minutes and language or daily totals, but cannot reconstruct browser-level uniqueness or historical concurrency. They may also lack a named event. Unique Listeners Only omits those older aggregate records.
No. The report describes observed browser activity. Unidentified observations are excluded from unique-browser counts, with the exclusion disclosed. Shared devices, private browsing, cleared storage and multiple devices affect the totals. Presence and minutes are estimates, not proof of attendance or attention.
The next event starts here
Review language demand and participation patterns alongside your event plan. Then set up the audience links, station access and welcome experience for the next gathering.
Explore event operationsLet everyone be part of it
Already part of a team? Sign in to start a session.
Explore plans for your organisation →