> ## Documentation Index
> Fetch the complete documentation index at: https://help.trfyx.com/llms.txt
> Use this file to discover all available pages before exploring further.

# User journeys

> Understand the paths visitors take through pages and product experiences.

# User journeys

User journeys help you understand the sequence of pages or product steps people follow. Instead of looking at every page in isolation, use a journey view to explore how one interaction leads to another and where users branch, loop back, or leave.

## Questions journeys can answer

* What do visitors commonly view after a landing page?
* Which pages tend to appear before signup or purchase?
* Do users take different paths to the same outcome?
* Where do people go after encountering a help or pricing page?
* Does a new navigation structure change the paths people take?

Journeys are descriptive: they show recorded sequences, not necessarily the motivation behind a user's choice.

## Investigate a journey

<Steps>
  <Step title="Choose an entry point or audience">
    Start with a page, screen, or segment tied to the question. Use a consistent date range and avoid comparing different audiences without accounting for their differences.
  </Step>

  <Step title="Read the next steps">
    Follow the most common transitions and notice less frequent branches that may be important. Keep in mind that common behavior is not always the behavior that creates the most value.
  </Step>

  <Step title="Find the point of friction">
    Look for loops, repeated visits to the same step, exits before a key action, or paths that differ between users who complete a goal and those who do not.
  </Step>

  <Step title="Compare against a goal or funnel">
    Use a [goal](/goals) to define the outcome and a [funnel](/funnels) to quantify progress through the key steps. Journeys are useful for exploring paths; funnels are useful for measuring a defined sequence.
  </Step>

  <Step title="Inspect sessions for context">
    Review relevant [session replays](/session-replay) when you need to understand how a transition occurred or whether the interface may have caused confusion.
  </Step>
</Steps>

## Tips for meaningful analysis

**Keep the question narrow.** A journey from the homepage to signup is easier to interpret than an unrestricted path across an entire product.

**Compare equivalent groups.** When comparing campaigns, device types, or time periods, keep the date range and journey definition consistent.

**Distinguish correlation from cause.** A page that appears frequently before conversion may be helpful, but the journey alone does not prove that the page caused the conversion.

**Check tracking coverage.** Missing events or pages can make a path look incomplete. Verify collection before interpreting a missing transition as user behavior.

## Journeys vs. funnels

| Use a journey when… | Use a funnel when… |
| - | - |
| You want to explore multiple possible paths. | You have a defined sequence of steps to measure. |
| You don't know which route users take. | You want to compare conversion and drop-off between stages. |
| You want to discover unexpected navigation. | You want to monitor a known activation or purchase process. |

## Next steps

Use [funnels](/funnels) to measure the flow you discovered, create a relevant [goal](/goals), and review [session replay](/session-replay) for qualitative context.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.