Journeys

Journeys are the pages and clicks a check walks through after the sitemap, like the path from pricing to sign-up. They let Hive Check see the tags that fire on clicks and later pages, not only on page load.

Public pages only. Hive never logs in. Form steps run only when you allow them on that journey.

Journeys belong to a site. Monitor the site first, so its checks keep their history. Then open the site under Tools → Hive and select the Journeys tab.

Create a journey

1. On the Journeys tab, select New journey.
2. Enter a Journey name, for example "Pricing to sign-up".
3. Leave Run in every check on, so every check walks through it.
4. For Page 1, enter the address of the first page, for example https://example.com/pricing.
5. Select Add action to add what to do on that page, in order.
6. Select Add page for each further page.
7. Select Save journey.

The next check walks through the journey.

Step types

Each page can have actions, which run in order after the page loads.

Fill a field and Submit a form are form steps. They can only be chosen once you allow form steps on the journey.

Form steps

Turn on Allow form steps on this journey to use form steps. The editor then warns:

Journeys with form steps allowed show Form steps on in the list. If you turn the option off, the journey keeps its form steps, but they run only when you allow form steps on the journey again.

What Hive refuses

Hive never logs in and never fills password, PIN, one-time code or payment card fields.

• In the editor, a selector that looks like one of these fields is refused before you can save, with "password, PIN and payment fields are never filled. Hive never logs in."
• During the check, Hive also looks at the field itself. When a field is a password field, or the page marks it as a password or card field, Hive doesn't type into it and stops that page's actions, whatever the selector says.

Limits

Every page must be on the site's own address. Hive follows your robots.txt on journeys too: a journey stops at the first page that robots.txt disallows.

Check your journey before saving

The editor lists anything to fix before you can save, for example:

• "Give the journey a name."
• "Page 2: enter the page address."
• "Page 1: the address must be on https://example.com."
• "Page 1, action 2: enter the CSS selector of the element."
• "Page 1, action 1: enter a test value to type."
• "Page 1, action 3: wait between 1 and 10000 milliseconds."

Manage journeys

The list on the Journeys tab shows each journey's name, how many Pages it has, and a Runs switch. Turn Runs off to skip the journey in checks without deleting it.

Use the pencil to edit a journey, or the bin to delete it. Later checks no longer walk through a deleted journey.

Without journeys, a check still loads your home page and sitemap pages. See what Hive checks.