Analytics

Analytics Overview

A tour of TestInvite's three analytics reports and how the numbers behind them are built.

Updated 2026/07/21

Analytics turns completed test sessions into performance signal — how a test scores across everyone who took it, and how each question performs across every place it was asked. It's built from finished sessions only, so the numbers describe what candidates actually experienced rather than what's currently configured in the editor.

Three reports, one data source

All analytics screens read from the same underlying dataset, just at different scopes:

  • Test Analytics — one row per test: submissions, average/min/max score, standard deviation, and (when opened from a specific test) a pass/fail split and score-frequency histogram.
  • Question Analytics — one row per question, across all the tests and tasks it's been used in: how often it was asked, how often it was answered, its average score, and its P-index and D-index.
  • Per-Question Analytics — the deep-dive on a single question, opened from the Question Bank editor: the same scores plus a breakdown of which choices or match options candidates actually picked.

Where each report lives

Test Analytics and Question Analytics are both standalone pages under Analytics in the left navigation, and are also embedded in context: open a test in the Test Editor and its Analytics tab shows that one test's numbers; open a task and its Analytics tab shows the questions asked within that task. Per-Question Analytics has no standalone page — it opens from the question's own editor in the Question Bank.

Filtering

Every report can be narrowed by task, test, and date range; Question Analytics additionally filters by folder. Selecting a task narrows the tests you can pick (and vice versa), since the two are linked through the sessions that actually ran. Filters are the main way to compare — for example, filtering Question Analytics down to a single test turns on D-index, a comparison that only makes sense within one test's population (see Question Analytics for why).

* * *

In this section

  • Test Analytics — how test-level scores, pass/fail, and score distribution are reported.
  • Question Analytics — how question-level performance (P-index, D-index) is reported across a folder, test, or task.
  • Per-Question Analytics — the single-question deep dive, including choice and match distributions.

What happens to Test Analytics, Question Analytics, and Per-Question Analytics when a question, test, task, step, or session gets deleted.

Analytics isn't computed live from the transactional database — it reads from a separate reporting database that's kept in sync with your organization's tests, tasks, questions, and sessions on a regular schedule. A change is usually reflected within a few minutes, but not the instant you make it.

This matters most right after you finish a session, edit a test, delete a question, or restructure a task — the report you're looking at may still reflect the old state for a short window. The refresh button on each report re-fetches the latest available data; it does not force an immediate recount. If you refresh right after a change and the number hasn't moved yet, that's expected — wait a short while and refresh again rather than assuming something's wrong.

Good to know: give the data a little time to catch up before assuming a report is wrong right after deleting or restructuring something.