Salam.AI

Audience reports

The event ends.
The insight stays.

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 console

From activity to understanding

A story your team
can act on.

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 ↓
Salam.AIReport structure

Audience report

The whole event.
A clearer picture.

Executive summary first. The detail behind it.

  1. 01
    Reach at a glance

    Joins · unique browsers · peak presence

  2. 02
    What your audience needed

    Languages · events · daily and hourly patterns

  3. 03
    How to read the results

    Coverage · estimates · measurement notes

Four useful perspectives

Read the numbers.
Know what they mean.

01

Listener joins

How often the audience connected.

Observed joins can include return visits. They are not a count of distinct people.

02

Unique listeners

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.

03

Peak concurrency

The busiest observed moment.

Presence is sampled. The highest observed concurrent audience is an estimate, not a verified headcount.

04

Listener minutes

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

Find the patterns behind participation.

01

Plan around language demand

Review which audience languages were used and how demand changed over the selected period. Event breakdowns help put the observations in context.

02

Choose a unique-browser view

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.

03

See how participation changed

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

An executive report.
The detail when you need it.

01

Set the scope

Choose the reporting dates, timezone and event filters. Review the coverage notes before interpreting the result.

02

Tell the event story

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.

03

Share or explore

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.

What is included in the PDF and CSV?

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.

How far back does detailed attendance go?

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.

Can this verify attendance or identify individual people?

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

Use the insight to prepare.

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 operations

Let everyone be part of it

Your next conversation.
A little more connected.

Open Salam.AI console

Already part of a team? Sign in to start a session.

Explore plans for your organisation →