Skip to content

Creating Simulations

To create a Simulation, open the Simulations page and click the + button next to the Simulations heading. This opens the Generate New Simulation modal.

Fill in the following, then click Generate Simulation:

  1. Experience — A slider from Novice to Expert (five levels, defaults to Expert). A higher level gives the run access to a richer set of learned Skills; lower levels narrow it toward core browser operations.
  2. Persona — Choose Generic (no specific Persona) or one of your derived Personas (see below).
  3. Simulation Instructions — Describe what the run should explore or test.
  4. Max Steps and Timeout — Control how far and how long the run can go (see below).

Instructions tell the run what to focus on. Be specific — for example, “Navigate to the settings page and test every account-management control.”

You can reference Application details with variables:

  • {{url}} — Your Application’s URL.
  • {{username}} and {{password}} — Sign-in credentials (available when your Application is an app rather than a public website).

The runtime substitutes the real values just before each action runs, so credentials are never stored in the transcript.

A Persona shapes how the run approaches your Application:

  • Generic — No specific Persona. Marketrix explores neutrally, following only your instructions.
  • A derived Persona — One of the Personas Marketrix builds from your real user data. The modal surfaces your top Personas for the Application. When you run with a Persona attached, the finished Simulation can surface the friction that Persona would experience as a set of findings.

If you don’t have derived Personas yet, run with Generic. Derived Personas come from UX Research, which builds them from real session activity.

These two limits bound a run. Marketrix always knows how much budget it has left and paces its exploration accordingly.

  • Max Steps — How many actions the run may take. Range 1–1000, default 100. Reaching the budget ends the run cleanly (it counts as Completed, not Failed). Increase it for large Applications with many pages.
  • Timeout — A hard wall-clock limit in minutes. Range 1–360 (up to 6 hours), default 30. If the run hasn’t finished within this window, the Simulation stops automatically.