Exporting a report as CSV or PDF

Download the play sessions of a forked game for your own analysis, or a PDF report to share.

Admins2 min read

From the report of a forked game, Export CSV downloads one line per play session of the selected period (and group, if any). Owners, admins, editors and analysts can export.

Columns

Column Content
started_at Start of the session (ISO 8601, UTC)
player Pseudonym or name, according to the reporting mode; anonymous for a player without an account on a public fork
status completed, active (not finished) or abandoned
score_percent Score recalculated by the server, in % (empty if not completed)
passed true if the score reaches the passing score of the game
duration_seconds Duration of the session

Test sessions (preview) are never exported. Sessions older than 13 months are deleted (retention), so they no longer appear in an export of an older period.

Security

  • Every export is recorded in the organisation's audit log (who, when, which period, which mode).
  • The file follows the reporting mode: no name leaves the platform in pseudonymous mode.
  • A group under the k-anonymity threshold exports the header row only.
  • Cells that a spreadsheet could run as a formula (starting with =, +, - or @) are prefixed with an apostrophe, so opening the file in Excel or Google Sheets is safe.
  • Exports are limited to 10 per minute per user.

PDF report

Export PDF (next to Export CSV) downloads a ready-to-share report of the same period and group, in the language of the site: summary, key indicators, plays over time, mastery by skill and the players table. The fork title is shown in that language when the fork is translated into it, otherwise in its source language. It follows the same rules as the CSV: reporting mode (pseudonyms by default), k-anonymity (a group that is too small gives a report without any figure), audit log entry with the format, 10 exports per minute. The PDF report is included in the Plus, Pro and Enterprise plans.

To send results to a training platform instead, see LMS exports (SCORM and xAPI).

Treat the file as personal data: store it in a protected place and delete it when you no longer need it.

Edit this page on GitHub (opens in a new tab)