> For the complete documentation index, see [llms.txt](https://docs.instruqt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.instruqt.com/reporting/activity-report.md).

# Activity

The Activity report shows how users engage with your tracks and labs over a period. This page explains what each metric means and how it is calculated.

To open it, select **Reporting** in the left navigation, then select **Activity**.

### What counts as a play

A play is one run of one track or lab. Restarts count as new plays.

* A play counts in the period in which it ended, not when it started.
* Plays that are still in progress are not counted until they end.
* Internal and invalid plays are always excluded.

The play type filter controls which plays are included:

* **All plays** (default) – all plays, including plays by the content's authors.
* **Normal plays** – excludes plays by the content's authors. For tracks, authors are the track's developers. For labs, the author is the person who created or last edited the lab.
* **Developer plays** – only plays by the content's authors.

### The metrics

The summary cards at the top cover the selected period. Each card shows the change compared with the previous period of the same length.

* **Plays** – the total number of plays in the date range, including restarts.
* **Unique users reached** – the number of different people who played, each counted once. This can be lower than the sum of the bars in the chart, because one user can play on several days.
* **Avg. time spent per play** – the average time users spend in the content per play. Paused time is shown separately.
* **Users completed** – the number of unique users who completed, divided by the number of unique users who played. Retries don't lower it.

The table shows the metrics per track or lab, plus these columns:

* **Time paused** – the time plays were paused. Shown only when pausing is enabled for your team. Contact support to enable it.
* **Completion rate** – completed plays divided by total plays. Retries and restarts lower it.
* **Happiness** – the average feedback rating users gave the content in the period. For labs, select the score to open the Lab feedback report.

Completion rate and Users completed can differ. Completion rate counts plays, so a user who restarts and then finishes lowers it. Users completed counts people, so that same user counts as completed.

### What counts as a completion

* **Tracks** – a play is complete when the user finishes the last challenge. Skipped challenges still count toward completion.
* **Labs** – a play is complete when all chapters are done. A chapter is done when all its pages are done. A page is done when every task and quiz on it is completed or skipped. A page without tasks or quizzes is done once the user opens it and scrolls to the end. Plays of draft labs are excluded from Completion rate and Users completed.

Each play is marked complete only once.

### Common questions

**What happens when a user restarts?** Restarts add to Plays, but not to Unique users reached. They can lower Completion rate. Users completed is not affected if the user completes at least one play.

**How are anonymous users counted?** Anonymous users, for example from an embed, are counted as unique users per browser session. A returning visitor can appear as a new user.

**Are my own team's plays included?** With **All plays** selected, yes. Select **Normal plays** to exclude plays by the content's authors. Team members who are not authors always count as regular users.

### Exporting

Select **Download CSV** to export the selected period and filters. The file includes both tracks and labs.

{% hint style="info" %}
**Note:** In the CSV export, `time_spent` (average time spent per play) and `time_spent_previous_period` are in seconds, not hours. To convert to hours, divide by 3,600.
{% endhint %}