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.
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. Turn on This journey requires sign-in when the protected area needs an authenticated browser session. 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, testing a page before it ships, 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.
• 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.
• Website sign-in: whether the engineer must sign in before desktop testing can reach protected pages.

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.

1. From the project list, select New analysis on the existing project.
2. Set up the journey with a new completed evidence period.
3. Start autopilot to collect fresh connected, technical, browser, and behaviour evidence for the new period.

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