--- isPrivate: true title: Journey Monitoring description: >- Monitor and analyze critical user flows to troubleshoot user experience and technical issues. breadcrumbs: Docs > Journey Monitoring --- # Journey Monitoring {% callout %} ##### Join the Preview! Journey Monitoring is in Preview. [Request Access](https://www.datadoghq.com/product-preview/journey-monitoring/) {% /callout %} ## Overview{% #overview %} **Journey Monitoring** lets you track the health of critical user flows such as login, checkout, or media streaming, all from a single place. For any given flow, you can answer: - Are users experiencing friction? - How fast and reliable is performance? - Are issues coming from the frontend, network, or backend? A *journey* is a user flow defined by a start event and an end event. For example, a checkout journey captures the experience from a user landing on the checkout page to completing the checkout process. Journey Monitoring pulls in data from [Real User Monitoring](https://docs.datadoghq.com/real_user_monitoring.md), [Synthetic Monitoring & Testing](https://docs.datadoghq.com/synthetics.md), [Product Analytics](https://docs.datadoghq.com/product_analytics.md), and [Session Replay](https://docs.datadoghq.com/session_replay.md) to show traffic, conversion rates, uptime, and errors for each journey in one report. This gives engineering, product, and developer operations teams a shared view of journey health without switching between tools. {% image source="https://docs.dd-static.net/images/journey_monitoring/journey-monitoring-map-1.85f9566bb5a0ab7bfbb32e818ea0ee63.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/journey_monitoring/journey-monitoring-map-1.85f9566bb5a0ab7bfbb32e818ea0ee63.png?auto=format&fit=max&w=850&dpr=2 2x" alt="The Journey Monitoring map showing a catalog of journeys on the left with traffic and conversion metrics, and a visual flow map on the right displaying user paths between application views and actions." /%} ## Capabilities{% #capabilities %} For each journey, you can: - Measure the journey's inbound traffic, conversion rate, and time to completion - Track the journey's availability using an uptime SLO based on its [Synthetic test suite](https://docs.datadoghq.com/journey_monitoring/uptime.md) - Identify where users drop off and investigate individual sessions with [Session Replay](https://docs.datadoghq.com/session_replay.md) - Measure the performance of critical steps in the journey with [RUM operations](https://docs.datadoghq.com/real_user_monitoring/operations_monitoring.md) - Share a unified view of journey health across engineering, product, and developer operations teams ## Prerequisites{% #prerequisites %} Journey Monitoring requires the following products for frontend applications, each contributing different data to your journeys: - **[RUM without Limits](https://docs.datadoghq.com/real_user_monitoring/rum_without_limits.md)** and **[Product Analytics](https://docs.datadoghq.com/product_analytics.md)**: Traffic, conversion rate, time-to-convert metrics, and performance. - **[Synthetic Browser Tests](https://docs.datadoghq.com/synthetics/browser_tests.md) or [Synthetic Mobile Tests](https://docs.datadoghq.com/synthetics/mobile_app_testing.md)**: Uptime tracking through the journey's automatically created test suite. ## Journey structure{% #journey-structure %} The start and end of a journey can be either action or view events from [Real User Monitoring](https://docs.datadoghq.com/real_user_monitoring.md). Each journey can have one or more variants. A variant is a specific sequence of intermediate steps a user takes between the journey's start and end. Different users naturally take different paths. For example, some may skip optional steps while others take detours before completing the journey. {% image source="https://docs.dd-static.net/images/journey_monitoring/journey-monitoring-explainer-diagram-final.075f72268a42494e4ab18c3754404560.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/journey_monitoring/journey-monitoring-explainer-diagram-final.075f72268a42494e4ab18c3754404560.png?auto=format&fit=max&w=850&dpr=2 2x" alt="Diagram of a journey with a start event, end event, and three variants, monitored by RUM and Product Analytics in the Live Environment and by Synthetic tests in the Synthetic Environment." /%} ## Setup{% #setup %} Define a journey by selecting its start and end events, then extend coverage with data from your other Digital Experience products. ### Step 1 - Create a journey{% #step-1---create-a-journey %} 1. Navigate to **Digital Experience > Journey Monitoring**. 1. Click **New Journey** or select a [suggested journey](https://docs.datadoghq.com/journey_monitoring/map/suggested_journeys.md). ### Step 2 - Specify journey details{% #step-2---specify-journey-details %} 1. Select a frontend application. 1. Add a journey name. 1. Select one or more start events. 1. Select one or more end events. 1. Click **Save Journey**. The right-hand funnel chart updates automatically based on the selected start and end events. The funnel shows volume, conversion rate, and average completion time for each step. **Note**: Mandatory fields are pre-populated if you start from a suggested journey. You can also add a description, attribute filters, team ownership, tags, and [variants](https://docs.datadoghq.com/journey_monitoring/details_report/variants.md). Clicking **Save Journey** creates the journey and redirects you to the journey's [details report](https://docs.datadoghq.com/journey_monitoring/details_report.md). The details report includes metrics on the journey's volume, conversion rate, and average time to completion. ### Step 3 - Add coverage from other products{% #step-3---add-coverage-from-other-products %} In the journey's details report, you can extend monitoring coverage based on the products you have: - Create [RUM operations](https://docs.datadoghq.com/real_user_monitoring/operations_monitoring.md) to monitor the performance of critical steps in the journey in your real user environment - Add Synthetic tests to the journey's [test suite](https://docs.datadoghq.com/synthetics/test_suites.md#service-level-objectives) to start tracking uptime If you already have pre-created RUM operations or Synthetic tests that cover the journey, Datadog surfaces the operation or test in the journey's details report. ## Metrics{% #metrics %} Each journey and its variants have the following performance metrics: - **Traffic**: Total number of journey attempts across user sessions. Based on the `rum.measure.journey` metric. - **Conversion**: Percentage of journey attempts that were completed. Based on the `rum.measure.journey` metric. - **Time to convert**: Average time to complete the journey across all user sessions. Based on the `rum.measure.journey.duration` metric. - **Uptime**: Availability of the journey based on its [Synthetic test suite](https://docs.datadoghq.com/synthetics/test_suites.md#service-level-objectives) uptime. ## What's next{% #whats-next %} - [**Map**: Visualize all your journeys and their traffic and conversion metrics.](https://docs.datadoghq.com/journey_monitoring/map.md) - [**Suggested Journeys**: Get automatically generated journey suggestions based on real user behavior in your application.](https://docs.datadoghq.com/journey_monitoring/map/suggested_journeys.md) - [**Details Report**: Analyze a journey's traffic, conversion, errors, and uptime in a unified report.](https://docs.datadoghq.com/journey_monitoring/details_report.md) - [**Variants**: Track and compare different paths users take through a journey.](https://docs.datadoghq.com/journey_monitoring/details_report/variants.md) - [**Uptime**: Measure a journey's availability with an automatically created Synthetic test suite.](https://docs.datadoghq.com/journey_monitoring/uptime.md)