Users report
The Users report shows activity from the user’s perspective – one row per person, aggregated across all their plays of all your content. Use it to answer “who are my users and how are they doing?”, where the Sessions report answers “what happened in each individual play?”.
To open it, go to Content Reporting in the left navigation and select Users.
The table
Section titled “The table”Each row is one user. The columns:
Plays – how many plays this person finished in the selected period, counting every replay separately. Like everywhere in reporting, plays still in progress appear once they end.
Completion – of the different content items they played, the share they finished at least once. This is content-based: replaying something they already completed doesn’t change it, and an unfinished retry doesn’t lower it. (Note the contrast with the Activity report: Completion rate there is play-based.)
Avg. Progress – the average progress across their plays. For a track, progress means completed challenges out of total challenges; for a lab, it means completed or skipped items across the lab’s chapters, pages, and activities.
Avg. Time spent – the average length of one play.
Last active – the most recent activity across their plays.
Filters at the top narrow the list: date range, play type, tracks, labs, invites, pages, users, and tags/groups. The Include anonymous toggle controls whether anonymous users appear in the list – useful when embeds or open invites generate many anonymous accounts.
User details
Section titled “User details”Click a user to open their details panel: a summary based on your current filters and the list of their individual plays.
Exporting
Section titled “Exporting”Download CSV exports one row per user: their identity, plays, content started and completed, completion rate, completed items out of total, average progress, time spent, and last activity. Because each row aggregates one person across all their content, the Users export has no per-content-type split – use the Sessions export when you need per-type rows.
