> 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 report

The Track activity dashboard shows how users engage with your tracks. 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 **Reporting** in the left navigation and select **Activity**.

### What counts as a play

A **play** is a single launch of a track. When a user launches the same track three times, that is three plays.

A few rules apply to every metric on the dashboard:

* 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 dashboard shows **Normal plays**: plays by the developers of the track are excluded. Use the play type filter to view developer plays or all plays instead.
* 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 track, adding **Time paused**, **Completion rate**, and **Happiness** (the average feedback rating users gave the track).

**Plays** – the total number of launches in the selected date range. Every launch counts, including restarts. One person launching a track 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 track on average, per play. 

**Paused time** is shown separately, in the table's Time paused column. Note - Pausing is an extra functionality that can be activated for your account. Contact our support team for details.

**Completion rate** – the share of *plays* that reached the end of the track: completed plays divided by total plays. Because this is play-based, retries and restarts lower it: a user who restarts twice and completes on the third play contributes one completion out of three plays.

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

> **Why the two completion metrics can differ:** a track where a few determined users retry often will show a low completion rate but a high users completed figure. Both numbers are correct – they answer different questions. Completion rate tells you how often a play attempt succeeds; users completed tells you how many people eventually get there.

### What counts as a completion

A play is marked complete the moment the user finishes the **last challenge** in the track.

* **Skipped challenges count.** A user who skips ahead and reaches the end of the last challenge is recorded as having completed the track. There is no requirement that every individual challenge was solved.
* A play is marked complete only once, even if the user keeps the track open afterwards.

### Common questions

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

**How do anonymous users appear?** Users who play without logging in (for example through an embed) 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 developers of the track are excluded by default (see the play type filter above). Other team members who are not developers of that track count as ordinary users.

### Exporting

**Download CSV** exports the report for the period and filters you selected.