Generally, we recommend installing the Maze snippet so that you can take full advantage of the features of the Website Test block.
However, in some cases where the website test block can’t be used, there’s a workaround using Clips screen recordings. It gives you additional flexibility to test websites or desktop applications.
When can I use this workaround?
| Website Testing block (using the Maze snippet) | Website testing with Clips (workaround) | |
| Advantages | - Full results, including usability metrics, heatmaps, and path analysis. Learn more about website testing results |
- Possible to test any type of website - Possible to test desktop applications |
| Drawbacks |
- Only allows you to test your own websites (i.e. websites where you can install the snippet) - Certain website setups aren’t supported (e.g. single-page applications) |
- Instructions must be extremely clear for participants, otherwise you risk not capturing any meaningful results data - Only works on desktop, since Clips doesn’t support screen recording on mobile. Learn more about this limitation - Risk of exposing participants’ personal information in the recordings - You'll only get qualitative results —i.e. no usability metrics. Learn more in the results section below |
Before you start
- We recommend making it very clear to participants that any actions they take during the task are real, and not part of a simulated test environment. For example, if you’re testing an e-commerce website, remind your participants not to purchase items during the test: any purchases would indeed be real, not simulated.
- Likewise, we recommend not asking for personally identifiable information (PII) during the task, as it would be visible in the results. There isn’t a way to mask data in Clips recordings.
- This workaround only works with tests taken on a desktop, since Clips doesn’t support screen recording on mobile devices. Learn more about this limitation
Creating the test
For this workaround, you’ll need to create a maze with the following elements:
-
Screen, audio, and video recordings must be enabled in the Clips settings. We also recommend making these settings required, to filter out participants who don’t grant the necessary permissions.
-
A custom message in the Welcome Screen explaining to participants that they must share their entire screen, and not just the browser tab or window
-
After the start screen, a Screener block and/or a Yes/No question confirming that the participant has indeed enabled their entire screen. Participants who reply ‘No’ should be routed out.
If using the panel, you must use a Screener block. Otherwise, you’ll be charged for all panel participants, even if they’re excluded from the test. Learn more about panel hiring -
A context screen with high-level instructions for the upcoming task(s).
-
An additional context screen containing the test URL. Add a separate context screen for each one of the tasks.
Interacting with the test
As a part of the task, participants will be asked to navigate away from the maze page, and into a different page or application.
This means that participants must share their entire screen, not just the tab or window. Without this prerequisite, you wouldn’t be able to follow them along as they go through the task(s), and the test results won’t be usable.
Learn more about the permissions that participants are prompted to accept
Analyzing results
To analyze test results, review the Clips recordings associated with the tasks and questions.
Because this workaround relies solely on Clips recordings, it doesn’t give you a way to capture click data, path success, or other usability metrics. If this is a requirement, using a Website Test block may be a better fit.