Trial columns

The trial table has one row per completed trial. Each row starts with rowNo, echoes your trial file’s columns unchanged, and then carries the generated columns below. Conditional columns appear only when the run used the matching feature.

Position and identity

Column	Meaning
rowNo	The trial-file row this trial came from. The first column of the table; use it to join results back to your trial file.
Your trial-file columns	Every column of the trial file is echoed with the values you authored, so each results row is self-contained.

Response

Column	Meaning
response	The recorded response: the key token as written in keyboard, the button label, the clicked option, the typed text, or the form answer. Timeouts are recorded as a timeout marker.
responseText	The display text of the chosen option when it differs from the stored response value.
responseCode	The code attached to the chosen response option, when your project defines response codes.
timestamp	Milliseconds since the experiment started when the response was recorded.
RT	Response time in milliseconds, measured from the start of the response period to the response.
RTkeys	One response time per keypress, separated by semicolons, when several keys are pressed within one trial.

Scoring

Column	Meaning
correct	1 when the response matched the key scoring rule, 0 when it did not. Present when key is used, or when form questions are scored.
responseScore	The per-trial score, when scoring is used.
tallies	The running tally counts after this trial, when tallies are used.
staircaseResult	Marks the final trial of each staircase run with 1.

Microphone recordings

Trials that record audio (responseType=mic with saving enabled) add these columns:

Column	Meaning
audioFile	The saved recording’s file name for this trial.
recOnset	When the recording started, in milliseconds relative to the trial.
voiceOnset	When the participant’s voice was first detected, in milliseconds.
recDuration	The length of the saved recording in milliseconds.
voiceDuration	How long the detected voice lasted, in milliseconds.
recDropped	Capture-health diagnostic: how many milliseconds of audio were lost on trials where capture dropped. The column appears only when some trial actually lost audio, so clean runs keep their usual format.

What was actually shown

Randomisation, lists, and wildcards mean the participant may see something the trial file only describes indirectly. These columns record the concrete outcome:

Column	Meaning
stim_actual	The concrete stimuli used when a trial drew from a stimulus list, separated by semicolons.
stimOrder_actual	The order in which the stimuli were shown, after any stimulus randomisation. A stimOptions shuffle draws it fresh at every display; a stimOrder spec draws it once per session.
stimPos_actual	The rendered position of each stimulus (horizontal and vertical, semicolon-separated per stimulus).
responseRows_actual	The response rows actually displayed, when responseRows are randomised.
<column>_actual	For each dynamic-list placeholder in your trial file, the value that was drawn, in a column named after the source column (for example stim1_actual).
Custom variables	Every variable you set from a script gets its own column with its value at each trial.

Tip

When an analysis needs to know exactly what a participant saw, prefer the _actual columns over reconstructing it from the trial file: they record the outcome after every layer of randomisation.