Journeys & Monitoring

What Is a Journey?

A journey is a saved audit configuration — URL, goal, constraints, device mode, and any store access answers — so you can re-run it without re-entering the details. This is the basis for regression testing your checkout after every deploy, and for ongoing monitoring.

Saving a Journey

There are two ways to save one:

• From a report — after running an audit, click Save as journey on the report page. The configuration is filled in automatically.
• From New Audit — tick Save as journey before running. GhostClick names it for you.

Managing a Journey

From the journey detail page you can:

• Run now — launch an audit with the saved configuration immediately
• Edit settings — change the URL, goal, constraints, or device mode via the gear icon
• Delete — remove journeys you no longer need
• View history — see past runs, including which settings version each one used

Changing the URL, goal, constraints, or device creates a new settings version. Older runs in the history keep a version badge, so it's clear which configuration produced them.

Scheduled Monitoring

Save a journey and enable scheduling to have GhostClick automatically re-run it in the background. Available intervals are every 2 hours, every 4 hours, every 6 hours, every 12 hours, daily, or weekly — which of these you can pick depends on your plan, so faster intervals are marked with the plan that unlocks them. Check /pricing or your account's Usage page for what your plan allows.

Monitoring Replays the Path

The first time a journey passes, GhostClick records exactly what the agent did: which element it clicked, what it typed, in what order, on each device. Later checks replay those same steps — no AI decides anything, nothing has to be worked out again. That's why monitoring can run as often as every two hours without costing what a full agent run costs.

A replay is not a weaker check. It walks the same path a real customer would, on your live site, and either the steps still work or they don't.

When the Replay Breaks

If a step no longer works, the journey ends somewhere unexpected, or the page it starts on has visibly changed underneath the recording, the AI agent takes over the same run, on the spot. You don't get a false failure and you don't have to trigger anything: you get one report that says the replay stopped working and what the agent found when it went to look. If the agent gets through, the path is re-recorded from what it just did.

Either way there's a weekly refresh: at least once a week a journey runs with the full agent rather than a replay, so a recording can never quietly drift away from your site. You can also force one yourself with Re-record on the journey page.

Runs Triggered by a Theme Change

On Shopify stores (Growth and up), a monitored journey can also run whenever your theme changes — which is when checkout regressions usually arrive. Two things trigger it:

• Publishing a theme — a run goes off shortly afterwards
• Editing the live theme — edits are held for about fifteen minutes first, so an afternoon of tweaking produces one run rather than forty

These are replays too when a recording exists. A theme edit is expected to change the theme, so the check is smart enough not to treat that alone as a reason to go and re-record — only an actual change to the page does that.

What the Agent Has Learned

Alongside the recording, GhostClick keeps a readable version of the path on the journey detail page, under "What the system has learned". When a full agent run happens, this is handed to it as guidance rather than replayed, so it finds its way faster while still adapting to a page that has genuinely changed.

You can reorder steps, rewrite a step's description to give the agent clearer instructions, delete steps that are no longer relevant, or add ones it missed. Editing it doesn't bump the settings version — it refines how the agent navigates without changing the journey's configuration.

Alerts

Every saved journey gets a starter set of alert rules so you find out when something changes without having to check manually. See Alerts for the full list of triggers and how to configure email and Slack.