Journeys
/dashboard/<siteId>/journeys — the shape of how people move through the site.
The flow
Section titled “The flow”Columns of nodes with ribbons between them. Each column is one step away from
the anchor, and every visit appears in every column: once a visit is over,
the boundary node (Exit going forward, Session start going backward) is
repeated to the edge of the diagram. That is what keeps each column’s total
equal to the number of visits, and gives the ribbons somewhere to land instead
of stopping mid-picture.
Node kinds:
| Kind | Meaning |
|---|---|
| Page | A pageview, labelled with the path |
| Event | A custom, outbound or revenue event, labelled with its name. Only with Custom events on |
Exit / Session start |
The visit boundary |
Other |
Everything outside the top 6 at that step, kept so the column still adds up |
Six nodes per column, plus Other and the boundary.
Controls
Section titled “Controls”| Control | Parameter | Values |
|---|---|---|
| Start at / Ends at | start |
path:/pricing or event:signup_completed. Absent means “Any page” |
| Where next / What led here | direction |
forward (default), backward |
| Steps | depth |
3–6, default 4 |
| Custom events | events |
1 to include, otherwise off |
The anchor is the visit’s first occurrence of that page or event. With no anchor, the flow starts at each visit’s first hit.
Going backward, the anchor is the last column, so both directions render left-to-right and the final hop is always into the page you asked about.
How filters apply
Section titled “How filters apply”Filters pick the visits; the flow then walks those visits in full.
Applying a filter to the rows instead would delete exactly the steps around the
match — which is the one thing a flow diagram exists to show. So filtering to
country=DE gives you the complete journeys of German visitors, not the German
fragments of everyone’s journeys.
Clicking the diagram
Section titled “Clicking the diagram”| Action | Effect |
|---|---|
| Click a node | Re-anchors the flow on it — sets start |
| Shift-click a node, or its list icon | Opens Sessions filtered to it |
The Sessions link chooses the filter that matches what the node means: event
for an event node, entryPath for the first column of an un-anchored forward
flow, and path for everything else. The journey-specific parameters are
dropped on the way.
Top routes
Section titled “Top routes”The whole page routes visits take, most common first, up to ten. Pages only — an event anchor does not consume a step. Per row:
- the sequence of paths, up to
depth; - visits and the share of the flow they represent;
- exits — visits that ended on the last page of the route.
Each route links into Sessions, filtered on its first page (path when the
flow is anchored, entryPath when it is not).
Page explorer
Section titled “Page explorer”For one page, counted per view rather than per visit:
| Figure | Meaning |
|---|---|
| Views | Views of the page in range — the denominator for every share |
| Entrances | Views that started the visit |
| Exits | Views that ended the visit |
| Previous | What was viewed immediately before, up to 8 |
| Next | What was viewed immediately after, up to 8 |
Clicking a neighbour re-anchors the flow on it.
URL parameters
Section titled “URL parameters”| Parameter | Values | Default |
|---|---|---|
range |
the nine range keys | 30d |
| all 26 filter keys | see Filters | none |
start |
path:<value> or event:<value> |
none |
direction |
forward, backward |
forward |
depth |
3, 4, 5, 6 |
4 |
events |
1 |
off |
Anything before the first : in start that is not event is read as
path. depth is clamped into 3–6 rather than rejected.
Related
Section titled “Related”- Sessions
- Funnels — an ordered flow you define, with drop-off
- Pageviews & SPAs