You can easily export results from each maze. Follow the steps here to save the results from your maze tests.
Download the data from your entire maze as .csv files
You can export the data of your entire maze as a .csv file. Open the maze and in the Settings page, found by clicking the gear in the top right, and click Download next to CSV Export:
Download mission outcome results
You can export an image file of the outcome results of each mission. Open the maze and on the Results page, select the mission. Click Save as image from the drop-down.
Save an image of a tester’s full session
You can save an image of each tester’s session from beginning to end. Open the maze and on the Testers page, select the tester’s full session. Click Save as image from the drop-down.
Export question results
For Multiple Choice, Opinion Scale, and Yes/No questions, you can save an image of the aggregated results of the question. Open the maze and on the Results page, select the question. Click on Save as image from the drop-down.
You can also download a CSV with all the responses you got for the question. In the Responses tab, click Download as CSV from the drop-down.
Download a CSV with all sessions data
You can also export a CSV with all raw data from tester sessions. This is available from the Tester paths tab in mission results.
Here’s the data available in CSV:
- 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 it took this tester (identified by testerId) to go to the next screen.
- totalDuration - the time 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 gives up / bounces. 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 gives up / bounces.
- giveup - true if the tester gives up on this mission; false if the tester doesn't. Give up happens when the tester clicks on "Give up" 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's screen URL looks like this:
That means that the screen at https://projects.invisionapp.com/share/SP74A7XC2#/screens/128221282 has screenId equal to
Marvel's screen URL looks like this:
That means that the screen at https://marvelapp.com/5bhi08b/screen/45283270 has screenId equal to
The screenId in the case of a Sketch prototype is created using the slug name of a screen.