Begin with the visitor’s task
A journey is a person trying to accomplish something. Write that task in plain language before choosing events or drawing arrows. Then separate the actions you can observe from the intentions you cannot directly measure.
For a service website, reaching the contact page and activating an email link are distinct steps. Neither guarantees that a message was sent. Use names that match the evidence.
Arrive with a question
A useful landing page sets the context.
Explore the right information
Clear navigation makes the next step easier.
Take a meaningful action
Measure the outcome you can actually observe.
Use paths to explore and funnels to evaluate
A path explores recorded sequences. A funnel evaluates a process with steps you define. Google’s path exploration documentation illustrates forward and backward exploration using page and event nodes.
For your own plan, specify the start, the counting unit, the allowed time window, and whether intermediate actions are permitted. Keep those rules stable across a comparison.
Write the hypothesis
Describe the observed pattern and at least two possible explanations. Do not turn every exit into a failure.
Repeat the task
Test the relevant page and environment. Record an observation separately from your interpretation.
Check the change
Repeat the scenario after a release and inspect comparable reporting periods when enough evidence is available.