Simulation runs and results

Follow simulation progress and read journeys, funnel stages, outcomes, friction, and optimization recommendations.

The run page turns generated shopper activity into evidence you can inspect before deciding whether the store should change.

Conditional: A run page exists only after an eligible simulation has been launched. Results can be partial, unavailable, or failed, and generated recommendations are not applied automatically.

Entry path

Open a store project → More → Simulation → select a recent simulation.

Before you start

Wait for the run to reach a completed or failed state before treating its totals as final.
Keep the target page and selected mode in mind while interpreting results.
Do not treat generated persona behavior as observed behavior from real shoppers.

Run controls and click results

Control or section	What happens or appears
Back link	Returns to the Simulation landing page and recent runs.
Journeys	Opens individual persona paths, decisions, steps, and available screenshots.
Funnel board	Groups shopper sessions by the furthest journey stage reached.
Outcomes	Summarizes terminal sessions, explicit exits, turn limits, and technical failures.
Persona or session card	Opens that generated shopper journey.
View step details	Opens the selected action, page, intention, rationale, and screenshot when available.
Send to Runner	Creates a Runner chat handoff containing the recommendation context. It does not apply the change.
Validate shoppers	Starts a same-shopper comparison run for an eligible recommendation.

Read a shopper-behavior run

Confirm the status is Completed or note which parts are still running.
Read the session totals and checkout-reach summary.
Open Funnel board to find the earliest common drop.
Open Journeys and inspect representative sessions at that point.
Use View step details to review the attempted operation and visible page state.
Open Outcomes to separate shopper exits from technical failures or turn limits.
Read each optimization recommendation with its evidence, affected area, risk, and validation plan.
Use Send to Runner only when you want a reviewable chat task; inspect the task before accepting changes.

Read a page-stimulus audit

Wait for the aggregate report.
Read the intent score and the number of shopper perspectives together.
Review segment differences and score distribution.
Read friction themes and supporting comments.
Use the result to form a testable hypothesis, not a guaranteed conversion prediction.

Troubleshooting

State	Meaning and next step
Results pending	Sessions have not finished. Wait for more terminal sessions.
No report available	The run finished without the expected aggregate report. Preserve the run ID and contact support.
Replay unavailable	A replay or signed screenshot could not be loaded. Reload the run to request fresh access.
Technical failure	The automation could not complete that journey; exclude it from behavioral conclusions.
Validation queued or running	The comparison is not ready. Wait before judging the recommendation.
Improved, regressed, or inconclusive	The same-shopper comparison favors, harms, or cannot distinguish the suggested change within that generated test.