You can easily download data for your maze results. In this article:
- Download the data from your entire maze as a CSV file
- Download mission outcome results
- Save an image of a tester’s full session
- Export question results
- Available data
Other relevant exports:
Download the data from your entire maze as a CSV file
To export the data of your entire maze as a CSV file:
- Open the maze you want to export the data for.
- Click the gear icon at the top right corner to reveal the Settings (
) menu.
- Next to 'CSV export', click the Export button.
When the export is ready, you will receive it via email with the subject line "Your data is ready". See which data is included in the CSV in this section.
Download mission outcome results
To export a CSV file of the outcome results of each mission block:
- Open the Results dashboard of the maze you want to export the data for, and select the relevant mission.
- Click the More (•••) menu and select Export as CSV file from the drop-down.
Save an image of a tester’s full session
To save an image of each tester’s session from beginning to end:
- Open the Results dashboard of the maze you want to export the data for, and select the relevant mission.
- Open the Testers tab.
- Select a tester.
- Click the More (•••) menu, and select Save as image from the drop-down.
Export question results
For Multiple Choice, Opinion Scale, Yes/No, and Open questions, you can save a CSV file or an image containing all the answers data.
- Open the Results dashboard of the maze you want to export the data for, and select the relevant question block.
- Click the More (•••) menu, and select Export as CSV file or Export as image from the drop-down.
Available data
Here’s the data available in the CSV file:
- missionId- unique mission identifier.
- missionTitle - the mission's title you define in Maze.
- path - the path the user took to complete/or not this mission.
- testerId - the tester's order when completing the mission (identified by mission Id/title).
- feedback - the qualitative feedback submitted by testers at the end of the Maze.
- screenId - screen identifier generated from the prototype.
- duration - the time in milliseconds it took this tester (identified by testerId) to go to the next screen.
- totalDuration - the time in milliseconds it took this tester (identified by testerId) to complete this particular mission (identified by missionTitle/Id).
- misclick - true if the tester misclicks; false if the tester doesn't misclick. A misclick is a click outside pre-defined hotspots on a screen.
- directSuccess- true if the tester completes the mission via the expected path; false if the tester completes the mission via an alternate path or if the tester abandons/stops the task without reaching the final screen. The expected path for each mission is defined by you when you create your Maze.
- indirectSuccess - true if the tester completes the mission via an alternate path; false if the tester completes the mission via direct success (identified by directSuccess) or abandons/stops the task without reaching the final screen.
- giveup - true if the tester gives up on this mission (i.e. abandons/stops the task without reaching the final screen); false if the tester doesn't. Give up happens when the tester clicks on "Stop task" during a mission or closes the window browser, leaving the mission and Maze incomplete.
- x - the position in percent (%) on the x axis from the top left
- y - the position in percent (%) on the y axis from the top left
Next follows the metadata captured automatically by Maze or the Custom metadata that you can record with the maze URL.
- guerilla - true if the session was tested in guerilla mode; false if guerilla wasn't enabled. Guerilla can be switched on in _Your link options _on a Live Maze screen from Unique session.
- os - the operating system of the tester (identified by testerId) used to complete the mission (identified by missionId/Title).
- browserVersion - the browser version of the tester (identified by testerId).
- browser - the browser type used by the tester (identified by testerId).
- lang - the language of the device used by the tester (identified by testerId).
The screenId is the one created by the prototype provider (InVision, Marvel, Sketch). Here's how the screenId is identified in Maze based on the prototype type:
InVision
InVision's screen URL looks like this:
https://projects.invisionapp.com/share/{projectId}#/screens/{screenId}
That means that the screen at https://projects.invisionapp.com/share/SP74A7XC2#/screens/128221282 has screenId equal to 128221282
.
Marvel
Marvel's screen URL looks like this:
https://marvelapp.com/{projectId}/screen/{screenId}
That means that the screen at https://marvelapp.com/5bhi08b/screen/45283270 has screenId equal to 45283270
.
Sketch
The screenId in the case of a Sketch prototype is created using the slug name of a screen.
Other relevant exports
Download click heatmaps
To save image files of every click heatmap, hover over the heatmap and click Save as image. Learn more
Export Clips recordings
You can download individual Clips from the Results page. Learn more in this article: Exporting Clips recordings
Download reports
You can easily share public links to your maze report and, if you’re on a paid plan, you can also download a PDF copy of the report for offline viewing. Learn more
Still need help?
If you have any questions or concerns, please let our Support team know — we'll be happy to help!