---
title: Export event data
description: Collect the event data export, analytics reports, player writeups, and feedback.
---

One archive holds everything your event produced, and it is created for you when the event ends. Anything beyond that archive (analytics reports, writeup files, feedback) comes from pages inside the event dashboard, which stays reachable only until teardown begins.

:::warning[The archive can wait; the file downloads cannot]
The **Data exports** page lives in your organization dashboard, so the archive stays downloadable after the event has ended. Everything else on this page lives inside the event dashboard, which goes away with the event's site and database when teardown begins. See [The event lifecycle](/organizers/explanation/event-lifecycle).
:::

## Collect the event data export

Open **Data exports** in your organization dashboard. Each row is one archive: the event it covers, when it was created, whether it was automatic or on demand, its status, its size, and how long it stays available. **Download** gives you a `.zip`. Listing and downloading exports is limited to organization **owners** and **admins**, since an archive can carry participant email addresses.

An archive is produced automatically when an event ends. To take a snapshot before then, use **Export now** on that page (or **Export event data** on the event's own **Exports** page) while the event is running. The archive is built from the event's live database, so on-demand exports stop being possible once it has ended. Your plan sets how many of these you can start per event per day, and only that many are kept per event; the automatic one is never limited or replaced. See [Plans and limits](/organizers/reference/plans-and-limits).

The archive holds one file per kind of data (spreadsheet-friendly CSV for the flat sets, JSON where a record has nested structure) plus a `manifest.json` naming the event, its start, freeze and end times, and the row count of every file so you can tell an empty section from a missing one:

- **Participants and teams**: players by username, teams by handle, team membership and roles
- **Results**: the final scoreboard with ranks, every solve, every flag attempt, and the full score ledger, which is what explains a total that moved after the freeze
- **Challenges**: the challenge set with its categories, difficulties, hints, prerequisites, file metadata, and the answer key you authored
- **Player-facing records**: hint unlocks, writeup metadata, feedback, report threads and their replies, announcements, issued certificates
- **Integrity**: the anti-cheat runs, signals and findings, with each finding's review decision and who made it, plus the accounts you excluded
- **Audit trail**: every organizer action recorded during the event
- **Event settings**: the configuration the event finished with

What is deliberately absent: passwords, session tokens and sign-in credentials of any kind; API keys; and the network address, browser user-agent and session identifier recorded against submissions and challenge activity. Integrity findings do carry a short fragment of the one-way device-profile hash where that fragment *is* the finding; the [event rules](/organizers/reference/event-settings) tell players this profile is recorded. Players are identified by username, and their email addresses are included only if you turn on **Include participant email addresses** in the **Data export** section of the event's [Settings page](/organizers/reference/event-settings) before the archive is built.

:::note[Retention is per plan, and it is not a backup]
Your plan sets how long each archive stays downloadable: 7 days on Hobby, 30 on every paid plan. See [Plans and limits](/organizers/reference/plans-and-limits). The clock starts when the archive is ready, and moving to another plan does not change the deadline on archives you already have. Once an archive expires the row stays on the page, marked **Expired**, as a record that it existed. Download what you need and keep your own copy.
:::

Challenge attachment files and player writeup files are not inside the archive; the archive carries their names and sizes. Download the files themselves from the event's **Files** and **Writeups** pages while the event is still running.

## Export analytics reports

The **Event analytics** page shows statistics for the full event window: stat cards for teams, challenges, submissions, and success rate, submission analytics with daily counts and an attempt-distribution chart, and a per-challenge statistics table (submissions, solves, teams solved, average attempts).

The two rate figures on this page measure different things. The per-challenge **Teams solved** column is the share of *teams* that solved the challenge: a challenge solved by half your teams reads 50% however many wrong attempts it absorbed, and teams hidden from the scoreboard are left out of both sides of that calculation. The **Success rate** card at the top of the page is submission accuracy: the share of flag attempts that were correct.

Two buttons at the top, **Export JSON** and **Export CSV**, export the report. Both carry the same data:

- Summary totals: teams, challenges, submissions, correct/incorrect counts, success rate (the key is `solveRate`)
- Daily submission counts and averages across the event window
- Per-team and per-user attempt counts (identified by ID)
- Per-challenge statistics: submissions, solves, teams solved (again `solveRate`), average attempts

The two rate figures keep the key `solveRate` in the export even though the page labels them **Success rate** and **Teams solved**, so match them by position rather than by name: the one in the summary object is submission accuracy; the one on each challenge row is team coverage.

The report is aggregated statistics; it doesn't contain individual submission rows. The CSV is a long-format table (`section, type, key, value`) where some rows hold JSON in the value column, so expect to process it rather than read it as a flat spreadsheet.

## Download writeups

The **Writeups** page collects challenge writeups uploaded by teams after the scoreboard freeze. Each row shows the team, challenge, file (name and size), who uploaded it, and when, with a download button per row. Search by team, challenge, or filename, or filter by challenge.

Players can upload `.pdf`, `.md`, `.txt`, or `.zip` files up to 10 MB, one writeup per team per challenge, and only once the scoreboard has frozen; before then the page shows *"No writeups uploaded yet"*.

## Review feedback

The **Feedback** page gathers participant feedback collected after the scoreboard freeze: an **Average rating** card (mean star rating out of 5), a **Responses** count, and a **Rating distribution** chart, above a table of each response with the user, their 1–5 star rating, comments, and submission time. Search, rating filters, and sorting help you dig through larger sets.

Like writeups, feedback opens to participants only after the freeze; see it as your post-event report card while [the scoreboard winds down](/organizers/how-to/monitor-a-live-event).
