What Mouse Tracking Measures
Mouse tracking captures the cursor's path — not just the final click — while a respondent answers a choice-based question. It's the standard technique behind decision-dynamics research: a cursor that curves toward an option before ultimately landing on a different one is evidence of competing pulls between choices, even when the final answer looks clean. Domandata records normalized x/y position samples over time and stores them separately from the answer itself, so enabling it never changes what the answer looks like to recodes, conditions, or exports.
Block Builder: Question Options
Mouse tracking is a per-question option, not a question type — it requires Standard plan or above, and once available you toggle it on individual questions.
Which Questions Support It
The toggle only appears on question types where answer options occupy distinct, fixed positions on screen — that spatial layout is what makes a cursor's path toward one option over another meaningful:
- Multiple Choice
- Dropdown
- Grid Matrix
- Conjoint
- MaxDiff
- Card Sort
- Heatmap, where the cursor path shows how the respondent explored the image before clicking
Slider and Drag to Order don't offer the toggle because mouse movement already is their answer — there's nothing separate to infer. Free-text, media, and display-only question types don't offer it because there's no spatial choice to track.
Enable It On A Question
Step 1: Open a supported question. Select a Multiple Choice, Dropdown, Grid Matrix, Conjoint, MaxDiff, Card Sort, or Heatmap question in Block Builder.
Step 1: Open Block Builder
Step 2: Turn on Track Mouse Movement. The toggle sits in the question's options panel, above the type-specific settings.
Step 3: Preview and move naturally. Confirm the survey still feels normal to answer — tracking is passive and adds no visible UI for respondents.
Step 3: Preview the question
What Gets Captured And Exported
Domandata samples cursor position at roughly 25 times per second while the pointer is over a tracked question, capped at 800 samples per question per response (about 32 seconds — far more than a typical decision takes). Samples are normalized to the question's own bounding box, the same convention used for Heatmap click coordinates, so trajectories are comparable regardless of screen size.
Each tracked question adds five summary columns to your export:
- Mouse Samples: how many positions were captured.
- Mouse Tracking Duration (ms): time from the first sample to the last.
- Mouse Path Length (normalized): total distance traveled, in fractions of the question's width/height — a longer path than a straight line to the answer suggests hesitation or redirection.
- Mouse Max Deviation (normalized): the largest distance the cursor strayed from a straight line between where it started and where it ended — the direct "curved toward the unchosen option" signal.
- Mouse Direction Reversals: how many times the cursor changed horizontal direction — a simple proxy for wavering between options.
These are summaries, not the raw path — a full trajectory can have hundreds of points, too many to usefully flatten into spreadsheet cells. If a survey has at least one mouse-tracked question, the Export tab's Responses card also shows a Raw Mouse Trajectories (JSON) button alongside CSV/XLSX/SPSS/Stata — it downloads every response's complete sample-by-sample path (keyed by each tracked question's export name), for analysts who want to plot or model the full path rather than the summary metrics. It follows the same include-preview/include-Silicon-Sample and quality-review filters as the other download buttons. The same data is also reachable via the raw response JSON (under each response's metadata) through API export.
Related Help
- Reaction Time Survey Questions for another millisecond-precision research measure
- Author-Defined Response Quality Rules
- Export Research Survey Responses