Activity report

The Activity report shows how users engage with your content. This page explains what each metric means and how it is calculated, so you can interpret the numbers with confidence.

To open it, go to Content Reporting in the left navigation and select Activity.

What counts as a play

A play is a single run of one piece of content. When a user launches the same lab three times, that is three plays.

A few rules apply to every metric:

A play is counted in the period in which it ended, not when it started. A play that starts on 31 January and ends on 1 February appears in February.
Plays that are still in progress are not counted yet. They appear once they end.
By default, the report shows Normal plays: plays by the content’s authors are excluded. Use the play type filter to include them. For tracks, authors means the track’s developers; for labs, it means who created or last edited the lab.
Internal and invalid plays are excluded automatically.

The metrics

The cards at the top summarize the selected period – Plays, Unique users reached, Avg. time spent per play, and Users completed – each with the change compared to the previous period of the same length. The table below breaks the numbers down per piece of content, adding Time paused, Completion rate, and Happiness (the average feedback rating). Which columns appear can depend on the features enabled for your team.

Plays – the total number of runs in the selected date range. Every run counts, including restarts. One person running a lab five times adds five plays.

Unique users reached – the number of different people who played in the selected date range. Each person counts once, no matter how many times they played. Because the headline number is deduplicated across your whole selected range, it can be smaller than the sum of the individual bars in the chart – that is expected.

Avg. time spent per play – how long users spend in the content on average, per play. Paused time is shown separately, in the table’s Time paused column.

Completion rate – the share of plays that reached the end of the content: completed plays divided by total plays. Because this is play-based, retries and restarts lower it.

Users completed – the share of people who reached the end at least once: unique users who completed divided by unique users who played. Because this is people-based, retries do not lower it.

What counts as a completion

For tracks, a play is marked complete the moment the user finishes the last challenge. Skipped challenges count: a user who skips ahead and reaches the end of the last challenge is recorded as having completed the track.

For labs, a play is marked complete when every chapter is done. A chapter is done when all of its pages are done, and a page is done when every task and quiz on it is completed or skipped. A page with no tasks or quizzes counts as done once the user has opened it and scrolled to the end. Skipping is possible at every level – task, quiz, page, or chapter – and skipped items count toward completion.

A play is marked complete only once, and completing sets its progress to 100%.

Plays of draft (unpublished) labs are not part of the completion metrics – they don’t count toward Completion rate or Users completed.

Common questions

A user restarted – what happens to the numbers? A restart creates a new play. It adds to Plays, does not add to Unique users reached, and lowers Completion rate if the earlier play was unfinished. Users completed is unaffected as long as the user completes at least once.

How do anonymous users appear? Users who play without logging in are counted as unique users like anyone else. Anonymous users are identified per browser session, so a returning visitor may occasionally appear as a new user.

Do my own team’s plays count? Plays by the content’s authors are excluded by default. Other team members count as ordinary users.

Exporting

Download CSV exports the report for the period and filters you selected, covering both content types in one file.