Projects and analyses

A project is a simple folder for related work. Give it a name and an optional description. It does not decide what UX Robot tests. An analysis is one dated evidence and report snapshot inside that project: a Journey analysis for one website that follows one complete visitor task and ranks its findings by your connected GA4 evidence.

Use whatever grouping makes sense to your team: a website, product, department, customer experience, or improvement programme. Related journeys in the same project can test different tasks.

1. Open the organisation and select Projects.
2. Select Create first project or New project.
3. Name the project and add an optional description. There is no project type.
4. Select New analysis inside the project to open Set up journey analysis.
5. Enter the website, the starting page, the visitor’s user story and what success means, and a safe stopping point. Or select Suggest journeys and pick one: UX Robot proposes user stories from your GA4 data and fills in the brief.
6. Choose a completed Connected evidence period. Future dates and today are not accepted, because a day that has not finished cannot be measured completely.
7. If the journey goes past signing up, signing in or entering a code, turn on Your team completes one step, such as signing up or signing in and describe the step. Never store credentials in UX Robot.
8. Select Save journey analysis.

The evidence period controls connected GA4 and Search Console collection. Once reports have been collected, the period is locked; the whole brief locks when autopilot starts. Create another analysis when you need a different period or task. See Journey analyses for every field in the brief and how the run works.

• User story: who the visitor is, what they want to do, and why. Write the goal as an outcome rather than a click path.
• Success means: what the visitor should see when the task has worked. If it depends on something UX Robot never does, such as paying or creating an account, describe what they should see just before that step, or hand that step to your team.
• Safe stopping point: the last permitted step, such as “Stop before payment or placing an order.”
• Market, device and viewport: the conditions the whole journey is tested under. Suggest from GA4 shows the device and market most of your visits use.
• Your team completes one step: a step only a person should do partway through the journey, such as signing up or signing in with a test account. The agent starts signed out and tests up to it, including the sign-up or sign-in page, checks those pages as a new visitor sees them, waits while your team does the step, then carries on through the rest of the journey in their session. See Sign-up and sign-in journeys.

Be factual: unsupported assumptions can be repeated in the generated report. Evidence itself is gathered after you select Start autopilot; it is not entered in this form.

Approved analyses are locked point-in-time records. They cannot be edited, so a rerun after a fix is always a new analysis next to the earlier one.

1. Open the approved analysis and select Run this journey again. UX Robot copies the brief into a new analysis in the same project, with an evidence period of the last 28 complete days.
2. Check the brief, then start autopilot to collect fresh connected, technical, browser and behaviour evidence.
3. The new run checks every open and shipped issue from the earlier runs, and its report opens with what changed since.

To test a different task, select New analysis on the project instead. See Issues and ticket tools for how issues carry from one run to the next.