Skip to main content
Exports are granular on purpose. Take the datasets you need from Results, the artifacts you need from a session, and leave the rest. Everything here is also available programmatically.

What you need first

  • The playtest whose data you want, and a sense of which parts you actually need.
  • Your retention window, if a deadline is what brought you here. Session data is removed permanently when it closes.

The playbook

1

Export the playtest datasets

Open Results, then Export in the header.
  • Pick the datasets you want in Export results data.
  • Confirm to download them as JSON.
Only datasets that hold data are offered, so a playtest with no survey will not offer Responses.

Exports

Every dataset and artifact format, and when each is available.

Results overview

Which tabs your playtest earned, and so which datasets exist.
2

Choose the right dataset for the question

Overview carries the summary metrics, Responses the survey results by question, Players the demographic breakdowns, Individual responses every player’s answers, and Screening responses the eligible and ineligible answers.
3

Take a single chart if that is all you need

Any chart on the results pages carries its own Export chart menu.This is quicker than a full dataset when you want one number for a deck.
4

Export a session's artifacts

Open a session and export from there. Each artifact comes out in its own format: video as MP4, audio as WebM, events, highlights, and transcripts as JSON, and responses as CSV.
Video files are prepared on demand, so a recording that has just finished may need a moment before it downloads.

Sessions overview

Every artifact a finished session produces, and the states it can be in.

Transcripts

What comes out in the transcript file, and what does not.
5

Do it before the retention window closes

Check your studio’s retention period in Settings > Studio.Once a session passes it, the recording and its artifacts are gone for good, and no export can bring them back.

Data retention

The deadline on all of this, and how to change it.

Decide how long to keep recordings

Playbook: pick a window you can actually work inside.
6

Automate it if this is a routine

Create an access key in Account > Developer, then pull the same datasets over the REST API or the CLI.This is the right route for a reporting pipeline or a scheduled backup.

API keys

Create the access key a scheduled pull authenticates with.

Exports

Every export command, argument, and flag.

How you know it worked

  • The export modal lists only the datasets your playtest actually produced.
  • Each file downloads as JSON, or in the artifact format listed above for a session.
  • A session that produced nothing exportable offers you nothing, rather than an empty file.
  • An API call with your access key returns the same data as the download.

Exports

Every dataset and artifact format, and when each is available.

Data retention

The deadline on all of this, and how to change it.

Automate with the API

Playbook: an access key, the endpoints, and scheduled pulls.

Work out what to fix next

Playbook: for when you want conclusions rather than files.