# Explore paths through your game and website

> Inspect page and event transitions to see which paths players actually take. Use the flow report next to a funnel with a fixed destination.

Canonical URL: https://manalens.dev/features/user-journeys

Inspect page and event transitions to see which paths players actually take. Use the flow report next to a funnel with a fixed destination.

[How to install](https://manalens.dev/docs/install)

## Discover a path before defining a funnel

A flow asks what visitors did next. A funnel asks how many visitors followed steps you chose. Start with transitions from an important page or event, then turn a recurring path into a conversion question.

## Segment the transitions

Use the selected date range and context filters to compare traffic from a campaign, device type, or country. Keep the comparison window and collection rules consistent when reviewing a release.

## Use activity for the details

Aggregate transitions show recurring patterns. The activity feed and profile history provide event-level context.

## Read transitions with care

Flows group by the persistent anonymous ID, so a return visit in the same browser stays in one journey. Flow transitions show observed order, not causation. A second device appears as another anonymous ID unless identify links it.

## Frequently asked questions

**How are flows different from funnels?**

Flows explore observed transitions. Funnels measure an ordered set of steps defined by you.

**Are cross-day anonymous journeys available?**

Yes. The anonymous ID persists across days in the same browser.

**Can flows mix pages and events?**

The analytics model contains page and track events. Transition reports use that event stream.

## Explore next

- [Funnels](https://manalens.dev/features/funnels)
- [Sessions](https://manalens.dev/features/sessions)
- [How collection works](https://manalens.dev/docs/privacy)

Implementation reviewed 2026-11-18.
