Different Figma prototype triggers should usually work when setting up paths and testing prototypes, as long as they lead to a screen or overlay transition .
However, click tracking is a cornerstone of how success is measured in Maze. As a result, non-click interactions aren’t recorded consistently in the results/heatmaps, even if they do result in a screen change.
As a result, at the moment, Maze only supports Click / Tap interactions. Non-click triggers aren’t formally supported.
The only exception is if interactive components are enabled in the maze. In that case, you have the option to register variant changes brought on by non-click triggers (e.g. hovers) as a screen change. Learn more about using interactive components in Maze
Otherwise, depending on how your test is set up, it might be possible to build a functional mission. But it’s important to keep in mind that, when using a trigger that isn’t formally supported in Maze, you and/or your testers may encounter unexpected issues, and you won’t see meaningful results data (i.e. heatmaps, misclicks, etc.) related to those interactions.
Trigger | Supported by Maze? |
On Click / On Tap | Yes |
On Drag | Not formally supported |
While Hovering | Not formally supported |
While Pressing | Not formally supported |
Key[board]/Gamepad | Not formally supported |
Mouse Enter / Mouse Leave | Not formally supported |
Mouse Down / Touch Press | Not formally supported |
Mouse Up / Touch Release | Not formally supported |
After Delay | Not formally supported |
When video hits / When video ends | Not formally supported |
Still need help?
If you have any questions or concerns, please let our Support team know — we'll be happy to help!