---
isPrivate: true
title: Map
description: >-
  Visualize and monitor the performance of your journeys in the Journey
  Monitoring map.
breadcrumbs: Docs > Journey Monitoring > Map
---

# Map

{% callout %}
##### Join the Preview!

Journey Monitoring is in Preview.

[Request Access](https://www.datadoghq.com/product-preview/journey-monitoring/)
{% /callout %}

## Overview{% #overview %}

The **Journey Monitoring map** displays all created and suggested journeys in a frontend application. Each tile in the map displays metrics on a journey's volume and conversion rate. If the journey has at least one Synthetic test defined, the tile also displays the journey's [Synthetic test suite](https://docs.datadoghq.com/synthetics/test_suites.md) uptime metric.

{% alert level="warning" %}
Only frontend applications that are instrumented with RUM without Limits, Synthetic Monitoring & Testing, and Product Analytics are eligible for Journey Monitoring.
{% /alert %}

## Explore and manage journeys{% #explore-and-manage-journeys %}

Use the map to explore and manage your journeys:

- Change the zoom level in the map
- Hover over a journey to see its description, start, and end definition
- Click on a journey in the catalog to navigate to the journey's [details report](https://docs.datadoghq.com/journey_monitoring/details_report.md)
- Use the filters and search bar to narrow down the displayed journeys in the catalog and map
- Click on a journey's three-dot menu to edit or delete the journey

## Journey states{% #journey-states %}

Journeys in the map and catalog may be color-coded based on their configuration and performance:

- Suggested journeys are **purple** and tagged with a "Suggestion" pill
- Journeys with a dropping conversion rate are **orange** and contain a red chevron
- Journeys with failing tests are **red**
- Journeys with no tests in their Synthetic test suite contain a **warning** in their tooltip

## User flows in the map{% #user-flows-in-the-map %}

The leftmost node in the map represents the starting point for all user sessions in your application. All other nodes in the map are either pages or journeys. A page node can represent a parent path that expands to show its nested pages.

{% image
   source="https://docs.dd-static.net/images/journey_monitoring/journey-monitoring-map-zoom.9b1bc88e3c67bc667ea2430692ad08eb.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/journey_monitoring/journey-monitoring-map-zoom.9b1bc88e3c67bc667ea2430692ad08eb.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." /%}

The thicker the connection line, the more traffic flows between two nodes. Journeys that are not connected to the Session start node are journeys that users navigate to only after a session has already begun, rather than as an entry point into the application.

## Further reading{% #further-reading %}

- [Learn about Journey Monitoring](https://docs.datadoghq.com/journey_monitoring.md)
- [Learn about suggested journeys](https://docs.datadoghq.com/journey_monitoring/map/suggested_journeys.md)
- [Learn about journey details reports](https://docs.datadoghq.com/journey_monitoring/details_report.md)
- [Learn about journey variants](https://docs.datadoghq.com/journey_monitoring/details_report/variants.md)
- [Learn about journey uptime](https://docs.datadoghq.com/journey_monitoring/uptime.md)