Skip to content

Journeys user manual

Journeys checks whether the important parts of your product still work. It uses a real browser to follow flows such as signing up, logging in, searching, or reaching checkout. The result tells you about the feature a person uses, not just whether a server returned a response.

The shortest path to a watched check

  1. Add your site and choose a check.
  2. Run the check while you are there to teach Journeys the intended path.
  3. Inspect the result, then choose Yes, start watching and set a schedule.
  4. Return later to read health, uptime, and run evidence.

Adding a site or saving a check does not immediately run it or put it on a schedule. A new check stays Draft until it has passed in an attended run and you approve the path it took. This protects your product from unattended automation that has not yet been reviewed.

A good first check

Start with Availability, Navigation, or Missing page. Checks that create accounts, send messages, add products to carts, or submit forms have real side effects; the catalog marks them before you add them.

Find the answer you need

The terms used in this manual

Site is the product or web property you added to Journeys. Check is one browser task, with instructions and a start URL. Run is one attempt at a check. Scheduled run is a run started by the schedule; it is the only kind that contributes to health and uptime. Memory is the practical advice Journeys learned from successful runs of that check.

Some internal URLs and API responses use the older word journey for a check. They refer to the same saved check; use the labels in the Journeys interface when following this manual.