On this page: Learn how to use Live Reporting to monitor key journey metrics from the last 24 hours directly within the journey canvas.
After your journey is published, on once the Dry run mode is activated, Live Reporting provides metrics from the last 24 hours, directly within the journey canvas.
The displayed events occurred within the past 24 hours, with a minimum interval of two minutes between the event and its display, typically within five minutes.
For your journeys in Live or Dry run mode, you can check:
-
Entered profiles: Total number of individuals who entered the journey.
-
Exited profiles: Total number of individuals who exited the journey (including errors).
-
Profiles in error: Total number of individuals who encountered an error during their journey.
-
Discarded profiles: Total number of individuals who were discarded from the journey for one of the following reasons:
- For Audience Qualification activities, a discard can happen if the expected verb for audience qualification mismatch what journey has received (e.g. “exited” instead of “realized”).
- For event-triggered journeys, a discard can happen if the individual attempted to reenter the journey too soon or when reentry was not allowed.
- On recurring journeys, a discard is counted on each recurrence if the individual is already in the journey and the reentry policy is not set to “force reentrance”.
- On Read Audience activities, a discard occurs if no identity is set for the exported individual, or if the received identity namespace does not match the expected one for the journey.
For each activity within every journey in Live or Dry run mode, you have access to:
- Entered: Total number of individuals who entered this activity. For Action activities, as they are not executed in Dry run mode, this metric indicates profiles passing through.
- Exited (met exit criteria): Total number of individuals who exited the journey from that activity, due to an exit criteria (including errors).
- Exited (forced exit): Total number of individuals who exited the journey while it was paused due to a journey practitioner configuration. This metric is always equals to zero for journeys in Dry run mode.
- Error: Total number of individuals who had an error on that activity.
Troubleshooting missing reporting data troubleshooting-missing-data
If you do not see expected data in your journey reports, consider the following:
-
Journey name synchronization: Verify that the journey name in Adobe Journey Optimizer matches the name stored in the reporting dataset. A mismatch between these names can prevent reporting data from appearing correctly.
-
Data refresh timing: After updating a journey name or configuration, allow sufficient time for the data to refresh. Reporting data typically appears within a few minutes, but in some cases may take longer.
-
Access permissions: Ensure you have the necessary permissions to view journey reports. If you see no data, check with your administrator that you have the View journeys report permission enabled. Learn more about permissions
-
Journey status: Reporting data is only available for published journeys or journeys running in Dry run mode. Draft journeys do not generate reporting data.
If issues persist after verifying these items, contact your Adobe administrator or Adobe support for assistance.
This section contains structured knowledge intended to support interpretation, retrieval, and question answering related to this topic.
For complete understanding, this information should be combined with the documentation on this page. Neither source is intended to stand alone; the page describes the feature, while this section provides additional context that helps disambiguate terminology, intent, applicability, and constraints.
- TL;DR: This page explains how to view and interpret the live report embedded in the journey canvas, covering the key profile flow metrics available for published journeys and journeys in Dry run mode.
Intents:
- View real-time journey performance metrics directly in the journey canvas
- Interpret Entered, Exited, Error, and Discarded profile counts for the journey and each activity
- Understand why profiles are discarded from a journey
- Troubleshoot missing or unexpected data in journey live reports
- Verify the required permission to access journey live reports
Glossary:
- Live Reporting: Real-time metrics displayed directly on the journey canvas covering the last 24 hours (product-specific)
- Dry run mode: A journey execution mode that simulates the journey without sending real messages, in which live reporting is also available (product-specific)
- Discarded profiles: Profiles that attempted to enter the journey but were rejected due to qualification mismatches, reentry restrictions, or identity issues (product-specific)
- Exited (forced exit): Profiles that were removed from the journey while it was paused by a journey practitioner; always zero in Dry run mode (product-specific)
Guardrails:
- Live report data covers only the past 24 hours.
- Events are displayed with a minimum interval of two minutes from occurrence, typically within five minutes.
- The View journeys report permission is required to see live report data.
- Reporting data is only available for published journeys or journeys in Dry run mode; draft journeys generate no data.
- For Action activities, the Entered metric shows profiles passing through (not executed) in Dry run mode.
- The Exited (forced exit) metric is always zero in Dry run mode.
Terminology:
- Canonical name: Live report (journey canvas) — Acronym: none — variants: journey live report, in-canvas reporting
- Synonyms: “Entered profiles” = “profiles who entered the journey”
- Do not confuse: “Live report” ≠ “Journey global report” (live report is the last 24 hours in the canvas; global report covers a wider historical time range in the reporting UI)
FAQ:
- Q: How current is the data shown in the live report? — Events from the past 24 hours are shown, with a minimum display delay of two minutes and typically within five minutes.
- Q: Why can I not see any data in my journey live report? — Check that you have the View journeys report permission, that the journey is published (not in draft), and that the journey name matches the name in the reporting dataset.
- Q: What causes profiles to be discarded? — Discards can occur due to audience qualification verb mismatches, reentry policy violations on recurring or event-triggered journeys, or missing/mismatched identity namespace on Read Audience activities.
- Q: Is the live report available during Dry run mode? — Yes; live reporting is available for both published live journeys and journeys running in Dry run mode.
- Q: What does the Entered metric mean for Action activities in Dry run mode? — It indicates profiles passing through the activity, since actions are not actually executed in Dry run mode.