Sessions report
The Sessions report lists every individual play across your content – who ran what, when, and how it ended. Open a play to see its details and the user’s step-by-step activity log.
To open it, go to Content Reporting in the left navigation and select Sessions.
The table
Section titled “The table”Each row is one play, with the Content column showing which track or lab it was (the content type appears under the name), followed by the user, their progress, time spent, and when it started.
Filters at the top narrow the list: date range, play type, tracks, labs, invites, pages, users, tags/groups, and custom parameters.
Play details
Section titled “Play details”Click a play to open its details panel, with up to three tabs: Overview, User details (shown when the play carries user information), and Activity log.
The Overview tab shows the play’s statistics (progress, time spent, started time) and its context: where the play came from (invite, landing page, embed, test, or direct), the referrer, the play type (normal or developer play), and why the play ended – the user completed the content, stopped it themselves, an idle timeout, or the time limit ran out. It also shows the user’s feedback rating and any custom parameters.
Some details apply to one content type only, and appear only on the content type they apply to.
The activity log
Section titled “The activity log”The activity log shows what the user did inside the play, entry by entry, in chronological order. Each entry shows the action, its timestamp, and where it happened.
For tracks, the entries are:
| Entry | What it means |
|---|---|
| Track started | The play began. |
| Challenge #N started | The user entered that challenge. |
| Challenge #N attempt: M | The user’s Mth check attempt on that challenge. |
| Challenge #N completed | The challenge was marked done. |
| Challenge #N skipped | The challenge was skipped rather than solved. |
| Track completed | The user reached the end of the track. |
| Track stopped | The play ended. |
Challenge entries show the challenge underneath the action.
For labs, the log shows the user’s progress through the lab’s tasks and quizzes:
| Entry | What it means |
|---|---|
| Lab started | The play began. |
| Task #N started | The task became available to the user. |
| Task #N attempt: M | The user’s Mth attempt at the task. |
| Task #N completed | The task was passed. |
| Task #N failed | A task attempt failed. |
| Task #N skipped | The task was skipped – it still counts toward completion. |
| Quiz #N started / attempt: M / completed / failed / skipped | The same actions for quizzes. |
| Lab completed | The user finished the lab – every chapter completed or skipped. |
| Lab stopped | The play ended. |
Task and quiz entries show the title of the page they sit on underneath the action. Chapters and pages don’t produce entries of their own – they organize the lab, and the log follows what the user actually did inside them.
Tasks and quizzes are numbered in two separate sequences that run across the whole lab in its outline order – so a single page can show both Task #1 and Quiz #1, and numbering doesn’t restart per page or chapter.
Exporting
Section titled “Exporting”Download CSV exports one row per play, covering both content types in one file. The export includes the play’s identifiers, content details, timing, progress (including completed items out of total), how it ended, the user’s details and feedback, and any custom parameters.