> 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/invite-activity-report.md).

# Invite activity report

Every track invite has an activity report showing what each user did after receiving the invite – from opening the invite link to completing a track. Use it to see who engaged, how far they got, and where they stopped.

To open it, go to the invite's details page and click **View activity report**.

### Reading the report

The report shows one expandable row per user, with their track starts, completion %, duration, when they were last active, when they accessed the invite, and their status. Expanding a row reveals that user's activity log: one entry per event, in chronological order. The **Participant** column identifies which play an entry belongs to.

#### The report columns

<table><thead><tr><th width="149.4765625">Column</th><th>What it shows</th></tr></thead><tbody><tr><td><strong>Track starts</strong></td><td>How many runs of a track the user started under this invite.</td></tr><tr><td><strong>Completion %</strong></td><td>The share of challenges the user completed out of the total available to them.</td></tr><tr><td><strong>Duration</strong></td><td>Time spent, measured between the user's recorded progress events – the same events that drive <strong>Last active</strong>. It reflects time spent progressing through the content, rather than total time with the track open.</td></tr><tr><td><strong>Last active</strong></td><td>The time of the user's most recent recorded progress event: starting, completing, failing, or skipping a challenge, a failed check, or a play being created, started, completed, or stopped. It does not track presence – a user can be actively working on content, without this parameter moving.</td></tr><tr><td><strong>Accessed</strong></td><td>When the user opened the invite link and claimed the invite – the same moment as the <em>Accessed</em> entry in their activity log.</td></tr><tr><td><strong>Status</strong></td><td>The user's overall state under this invite.</td></tr></tbody></table>

{% hint style="info" %}
**Reading this alongside the Live dashboard for Live Event:** the live event dashboard and this report answer complementary questions. The dashboard shows presence – who is in the lab right now – which is what you need while running a session.&#x20;

**Last active column** shows progress – each learner's most recent recorded progress event – which is what you need when reviewing results. Presence = who is there; Last active = how recently they moved forward. A learner who is reading or working towards their next check appears on the dashboard as present, and their Last active updates the moment they reach their next milestone.
{% endhint %}

### Form submissions

If the invite uses a form (users fill it in before they get access), the report gains a second tab: **Form submissions**, next to **User activity**. Each submission shows when it was submitted, the user's name and email, and after that the columns are your own: every field you added in the invite's form settings gets its own column, such as company, job title, or a consent checkbox. Invites without a form show the activity report directly, with no tabs.

### The activity entries

| Entry                               | What it means                                                                                                                                                                            |
| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Accessed**                        | The user opened the invite link and claimed the invite. This is always the first entry – it does not mean a track was launched yet.                                                      |
| **Play N: created (Hot Start)**     | The user's Nth run of a track under this invite began, from a pre-warmed environment. The timestamp is when they claimed it, not when the environment was built.                         |
| **Play N: created**                 | The user's Nth run of a track under this invite began.                                                                                                                                   |
| **Play N: stopped**                 | That run's environment ended – the user stopped or finished it, the time limit ran out, or it timed out from inactivity. A completed run shows both a *stopped* and a *completed* entry. |
| **Play N: completed**               | The user reached the end of the track in that run.                                                                                                                                       |
| **Play N / Challenge M: started**   | The user entered that challenge.                                                                                                                                                         |
| **Play N / Challenge M: completed** | That challenge was marked done.                                                                                                                                                          |
| **Play N / Challenge M: skipped**   | The challenge was skipped rather than solved.                                                                                                                                            |
| **Play N / Challenge M: attempt L** | The user's Lth *failed* check on that challenge. Solving a challenge on the first try produces no attempt entries.                                                                       |
| **Play paused**                     | The user's environment was suspended – they paused it, or it went idle. These entries carry no play number; use the Participant column to match them to a play.                          |
| **Play resumed**                    | The user returned to a paused environment.                                                                                                                                               |

> **A common misreading:** "Accessed" does not mean the user pressed launch, and "Play 1: created" does not mean the sandbox finished provisioning. Accessed = claimed the invite; created = started a run. The time between the two is the user deciding to start.

### How restarts and play numbers work

Each restart creates a new play with its own full set of challenge entries, starting again from Challenge 1. Play numbers are positional: Play 1 is that user's earliest run under this invite, Play 2 the next, and so on.

Two things worth knowing:

* **Numbering is per user per invite, not per track.** If the invite contains multiple tracks, Play 1 and Play 2 can be different tracks rather than a restart – check the Track column.
* **A date-filtered view can show Play 2 and Play 3 with no Play 1** – the numbering was assigned before the filter was applied. That's expected, not missing data.

### Anonymous users

Users who play without signing in appear as **Anonymous** with no email. When the invite allows anonymous access, the Email column is hidden entirely. The Participant column is the only way to tell two anonymous users apart.

If an anonymous user later signs in, their plays and progress move onto their real account – their history reappears under their name rather than being lost.

### Exporting

Three downloads are available from the report:

* **Activity CSV** – a summary with one row per play: who played, when they started and finished, time spent, challenges completed out of total, failed attempts, and any form fields the user submitted. The per-event timeline shown on screen is not included in the export – it is viewable on screen only.
* **Form submissions CSV** – all form submissions with your form's fields, from the Form submissions tab.
* **Chat History** – for invites used in a live event where chat was used: all messages, including direct messages, with the sender's name and timestamp. Chat history is available for 30 days after the session. See Live event reports.