Plan the states, not just the screens
Suppose a fictional order dashboard has a list, a filtered list, and an order detail. The list and filtered list may look like the same page, but they show different results. Capture both if a viewer needs to see what the filter changes. Capture the detail state too, then connect the relevant controls.
Adapt this table to your product before recording. Include the return path and any important alternative route. A sandbox is a collection of captured states and connections; it should not be assumed to run the original product’s backend or support every action from the live application.
Review the starting point
Open the sandbox in the editor, select Flow, then choose Open journey map. The map lists captured pages and links. Find the page a viewer should see first and choose Set as start. Rename pages when clearer names will help your team recognize them.Connect pages
For a page with an available HTML preview:- Select that page in the editor and choose Add link in the journey map.
- Click the element on the page that should lead somewhere. Press Escape to cancel picking.
- Choose the destination page and whether the link applies to this page, selected pages, or every captured match.
- Review the affected pages in the preview before applying. When a link applies across pages, publishing checks that the selected element can be found on each selected page.