Fixed stages let you compare dates on the same map. To explore an unnamed event sequence, use Paths.
ConsoleAll-platform analyticsBusinessJourney mapsAn industry pack installs one journey named after the pack. You can edit it here. See Industry packs.
Metrics & definitions
A journey has at most 20 stages. Each stage needs at least one page or one event, and at most 20 of each. A page is a full path, or a prefix when it ends with *.
Reach is counted in sessions. A move to the next stage requires the same session to hit this stage first and the next stage later. The first stage’s reach rate is 100 when it has sessions. Later rates are relative to the first stage’s sessions.
| Number | Meaning | Source |
|---|---|---|
| Users / sessions | People and sessions that hit the stage | Pages or events listed on the stage |
| Events per page | Events in the stage divided by pageviews | Falls back to sessions when there are no pageviews |
| Error, frustration, exit | Share of stage sessions | Error events, rage clicks, and sessions whose exit page is a stage page |
| Sentiment | 0 to 100 | 100 minus 1.5 times the error rate, 1.5 times the frustration rate, and 0.5 times the exit rate |
Error, frustration, and exit are computed only when the stage has page patterns. An event-only stage scores those three as zero, so sentiment sits high. That does not mean the experience was good.
How to use it
- Click New journey and add stages in real order. The sample names can be replaced.
- Put one page pattern or event name per line. Save, pick dates, and read reach and drop-off.
- When sentiment falls, see whether error, frustration, or exit moved, then open the top pages for that stage.
Access & limits
Creating, editing, and deleting journeys needs an owner or admin. Events need a session id. Server events with no session never enter a stage. A website path and an app event can share one stage.
FAQ
A later stage is larger than the one before it? Reach rate is versus the first stage, not versus the previous stage. People can skip a middle stage and still hit a later page or event.
Sentiment stays at 100? The stage has no page pattern, so error and exit cannot be tied to a page and those terms stay zero.