User Studies Overview
A User Study brings product research into one place. UX Research and A/B Studies run Personas through your product, while Surveys can collect answers from real people, simulated Personas, or both.
User Studies live on the User Studies page, scoped to the Application you’re working in. Survey questionnaires and responses are part of User Studies rather than a separate product.
The three study types
Section titled “The three study types”Every study is one of three types.
| Type | You provide | You get back |
|---|---|---|
| UX Research | A research question | Where Personas felt clear versus confused, as findings backed by their own words |
| A/B Study | A description of the two pages you’re comparing | Which variant converts better, and why |
| Survey | An internal questionnaire or external survey link | Organic and simulated responses, with per-question reports |
Creating a study
Section titled “Creating a study”Choose the study type, name it, and configure what that type needs — see UX Research, A/B Study, or Surveys for what each one asks for.
Two settings shape how simulated runs are grounded, and you can change either before launching:
- Add context — attach Knowledge files from this Application so Marketrix works from what it has read about your product.
- Respondent transcripts — when on, each persona answers from its own transcripts, the real words of the people it stands for, rather than its trait summary alone. Personas with no transcripts are unaffected either way.
A third option, Screenshots, controls how Marketrix sees each page during a browser run. On, it studies a screenshot of every page for the best results; off, runs are faster with slightly less detail. It applies to A/B Studies and simulated Survey runs — UX Research always studies screenshots, so turning it off there changes nothing.
How a run works
Section titled “How a run works”Each time you run a study with Personas it produces a run, and a study keeps its run history so you can compare results over time. A run moves through a shared lifecycle — running → finalizing → completed (or failed / stopped) — and while it runs you can watch the simulations replay live. It pauses and resumes under your Billing Cycle’s credit allowance rather than failing — see Billing and Credits.
Respondent, Persona Reaction, and Context Outcome
Section titled “Respondent, Persona Reaction, and Context Outcome”A Respondent is whoever answered — an organic person at the Survey link, or a persona standing in for one during a simulated run. Every simulation produces a Persona Reaction: what that Persona made of each step and how it felt about it. Once every Persona has finished, Marketrix folds those reactions — plus each Persona’s own answers — into per-Persona findings and a run-level summary. Survey responses from real people arrive independently and are labeled Organic.
Behind the finished/stopped counts below, Marketrix derives a Context Outcome for each task or A/B variant every time you view a run. It covers the finished and stopped rates, the step where stopping was most common, respondents’ own certainty, and the top themed reasons behind each outcome. It’s never stored — always recomputed from respondent answers on read — so what you see can’t drift from the underlying data.
From a study you can:
- Switch runs — Compare the current run against earlier runs of the same study.
- Read per-persona results — See each persona’s reactions and the type-specific output.
- Replay — Follow the linked simulation replays and jump to the moment tied to a persona’s reaction.
- Export — Generate a PDF report of a completed run, or export the responses as CSV.