Glossary

This page is the one home for what each term means. Every other page uses these terms without redefining them — follow the link for the full picture.

Studies and Personas

User Study — a study that runs on Personas, real people, or both: UX Research, A/B Study, or Survey. See User Studies.
UX Research — a User Study where Personas attempt a goal you describe, so you can watch how they navigate it. See UX Research.
A/B Study — a User Study that compares two versions by running the same Personas through both. See A/B Study.
Survey — the one asking surface: one questionnaire put in front of real people, simulated Personas, or both. See Surveys.
Respondent — whoever answered: an organic person at the Survey link, or a Persona standing in for one during a simulated run. See User Studies.
Persona Reaction — what a Persona made of each step in a run and how it felt about it. See User Studies.
Survey Answer — the value a Respondent gave to one Survey question, plus which question it answers. See Surveys.
Context Outcome — a run’s pass/fail-style result, computed fresh each time you view it rather than stored. See User Studies.
Persona — a modeled user type Marketrix tests with, built from your product Knowledge, a description, or by hand. See Personas.
Persona Chat — a one-on-one conversation with a Persona, outside of a run. See Persona Details.
Grounding Round — a persona import that carries a set of questions for real people to answer, so their responses become the persona’s evidence. See Persona Details.
Riders — the seats in a run that observe and react without steering; the counterpart to Driver. See Creating Simulations.
Driver — the seat in a run that calls the shots and takes each step. See Creating Simulations.

QA

QA Flow — a saved set of Journeys you run against your Application to check it still works. See QA Flows.
Journey — one scripted path through your Application, written once and reused across every Persona and viewport it’s bound to. See QA Flows.
QA Run — a single execution of a QA Flow, producing one outcome per Persona (or Generic) × Journey × viewport combination. See QA Runs.

Simulations and Knowledge

Simulation — an autonomous run that explores or tests your Application in a real browser. See Simulations.
Graph — a visual map of what Marketrix has discovered about your Application, generated from Simulation transcripts. See Graph.
Knowledge — what Marketrix reads about your product: the documents and videos you add. See Knowledge.
Heatmap — a visual record of where visitors clicked, scrolled, and moved, aggregated from Session recordings. See Heatmaps.
Skill — a reusable routine Marketrix distills from a completed Simulation and replays in later runs. See Skills.

Widget — the embeddable support surface installed on your site, offering Tell, Show, and Do modes. See Widget Overview.
Session — one visitor’s recorded interaction with your site, viewable as a replay. See Session Recording.

Workflows

Workflow — an automation that connects a Trigger to one or more actions. See Workflows.
Connector — a link between a platform (GitHub, Slack, Timer, or MCP) and Marketrix that supplies Triggers or actions. See Connectors.

Applications and Account

Application — a web app or website connected to Marketrix; everything else is scoped to one. See Applications.
Billing Cycle — the half-open, month-to-month period your usage is measured against, anchored to when your workspace was created. See Billing and Credits.
credits — the one unit Marketrix bills in, converted from measured inference cost at a fixed rate. See Billing and Credits.
allowance — the credits your plan grants for the current Billing Cycle. See Billing and Credits.
headroom — what’s left to spend this cycle: allowance minus credits already settled. See Billing and Credits.

Next steps

User Studies OverviewThe full picture behind the Studies and Personas terms above.

Common IssuesTroubleshooting steps if something isn't behaving as this glossary describes.