For AI agents: A markdown version of this page is available at https://docs.datadoghq.com/journey_monitoring.md. A documentation index is available at /llms.txt.

Journey Monitoring

This product is not supported for your selected Datadog site. ().

What is Journey Monitoring?

Journey Monitoring lets you track the health of critical user flows, such as sign-in, checkout, or media streaming, from a single place. For any 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 represents a user flow from a defined start to a defined end. Journey Monitoring combines data from Real User Monitoring (RUM), Synthetic Monitoring & Testing, Product Analytics, and Session Replay in a shared view for engineering, product, and operations teams.

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.

Prerequisites

Journey Monitoring requires an active trial or paid subscription to at least one of the following products:

RUM-enabled applications have a Product Analytics Preview enabled by default. The Preview retains Product Analytics events for a rolling 30-day window. Disabling Product Analytics also disables Product Analytics Preview. For questions, contact Datadog Support at support@datadoghq.com.

How journeys are structured

RUM and Product Analytics

If RUM is enabled and you have Preview, trial, or paid access to Product Analytics, define the journey with action or view events. A journey can include variants that represent specific sequences of intermediate events between its start and end. Variants require a Product Analytics trial or paid subscription.

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.

Synthetics only

If RUM and Product Analytics are not enabled, Synthetic test suites appear automatically as journeys. In this configuration, the test suite defines the journey. Create another test suite to add a journey.

Get started

Follow Configure journeys to define an event-based journey, add variants, link RUM operations, and add Synthetic test coverage. Create a journey manually or start from a suggested journey.

Key performance indicators

Event-based journeys report starts volume, conversion volume, conversion rate, and time to convert. Journeys with Synthetic coverage also report uptime. Product access determines each KPI’s data source, retention period, and calculation.

API

Use the Journey Monitoring API to query, create, update, and delete journeys.

What’s next


Further reading