How admins see who's on a Journey, where they are in it, and whether the program is actually moving — because Journeys don't show up on the standard assignment report.


Journey assignments don't appear on a user's standard assignment report. That means an admin who only checks that report will think no progress is being tracked — even when learners are moving through the program normally. The Journey-specific analytics page is the only place that surfaces Journey progress, completion timing, and last-interaction signals.

Tracking is most relevant when a Journey has time-released steps or a long horizon. Without visibility into who's stalled, who hasn't started, and who's actively progressing, the program runs blind — and stalled learners often need intervention long before the due date hits.

For the strategic frame on Journeys overall, see Journeys In Continu.


How to Open Journey Tracking

1. Open the Journeys list. From the left-hand navigation, click Share > Journeys.

2. Open the Journey's analytics page. Search for and click the title of the Journey you want to track.

Journey analytics view showing learner progress


What the Analytics Page Shows

Learners on the Journey. Everyone currently assigned, in one list. This is the audience you assigned via the Assignments page or an automation.

Start date. When each learner began the Journey. Useful for spotting cohort-vs-cohort comparisons and assignment dates that drifted.

Progress. Where each learner is in the Journey sequence. The most actionable column — anyone stuck on the same step for too long is a candidate for intervention.

Date completed. Empty until they finish. Use this for compliance and certification tracking.

Last interaction. When the learner last touched the Journey. A stale "last interaction" date alongside incomplete progress is the strongest indicator of a stalled learner.


Filtering and Downloading the List

Search and filter. Narrow the list by specific users, or filter by attributes like location or department to see how a sub-segment is progressing.

Download User List. The Download User List button exports a .csv of the currently filtered view. If no filters are applied, the export includes every learner on the Journey.

The CSV is useful for stakeholder reports, audit trails, and bulk follow-up on stalled learners. Pair it with the program's communications plan rather than treating the download as the end of the work.


Configuration Pitfalls

Only Checking Completion. Filtering on "completed" tells you who finished, but it hides everyone who's stalled. The actionable view is the in-progress list with a stale last-interaction date — those learners are what need attention.

Forgetting the Filter is Applied to the Export. If you filter the view and then click Download User List, the CSV only contains the filtered rows. To export everyone, clear filters first.

No Routine Cadence. A Journey that's checked only when stakeholders ask leaves stalled learners stuck. Build a weekly or bi-weekly cadence into the program owner's calendar so intervention happens before the due date.

Treating the Standard Assignment Report as the Source of Truth. The standard report doesn't include Journeys. An admin who relies on it will assume the Journey isn't being tracked when it actually is — and miss the dedicated view entirely.

No Action on Stalled Learners. Visibility without follow-up is just data. Define what counts as "stalled" (e.g., no interaction for 14 days mid-Journey) and what action follows (manager nudge, reminder email, attempt reset if technical).


Where This Fits

You're here because a Journey is live and you need to see how it's going. Assignment is in Assign a Journey; the manager-facing view of the same data is in Tracking Journeys For Managers.


See Also


Progress, last interaction, and stalled learners. The dedicated Journey view surfaces what the standard report can't.

Was this article helpful?
0 out of 0 found this helpful