Paths do not need steps written in advance; conversion through fixed steps is Funnels. Where on the page people clicked is Heatmaps & experience.

ConsoleAll-platform analyticsBehaviorBehavior analysis

How to configure

The measurement is the node: page or screen, event, or both. On the web a page is the view path; on apps and mini programs the screen name wins. Event mode drops internal names that start with a double underscore.

Behavior: direction is forward from a start (default) or backward from an end. Steps are 2 to 10, default 5. Each step keeps 3 to 15 nodes, default 8, and folds the rest into “other.” Repeated identical nodes collapse by default. Counting defaults to sessions, or people. You may set a start anchor, an end anchor, or neither. With neither, forward starts at the first step of the session and backward at the last. Exclusions allow 20 patterns, including wildcards. Up to 10 clean-up rules rewrite a matching path into one label.

No breakdown and no compare period. Identity defaults to person, but the default count is still sessions until you switch it to people.

How to read the result

The chart is flow from one step to the next. A node’s number is how often that node was passed. Forward paths also show drop-off: inflow minus what continued. The summary is starting volume, node count, step count, and total drop-off. Export is source, target, and count.

Limits & definitions

At most 50,000 transitions are kept before the per-step trim, so a long tail is dropped first. Drop-off is meaningful only forward. An anchor is the earliest start or the latest end inside that session or person. Without an anchor, one session contributes only its first or last few steps.