Track what matters beyond pageviews: signups, purchases, clicks, form completions.
- Goal conversions: set up and measure conversion goals -
- Funnel analysis: follow the visitor journey step by step +
- Funnel analysis: measure drop-off across a defined sequence of steps +
- User journeys: explore the paths visitors take on your site
- Ecommerce revenue tracking: attribute revenue to traffic sources
- Outbound link clicks: track clicks to external sites
- File downloads: see which files get downloaded diff --git a/docs/pageview-goals.md b/docs/pageview-goals.md index 6a26c2c3..30ac9c0b 100644 --- a/docs/pageview-goals.md +++ b/docs/pageview-goals.md @@ -46,6 +46,7 @@ Now that you're tracking pageview goals, you can: - Build a [conversion funnel](funnel-analysis.md) to follow the visitor journey from landing page to conversion - Add [custom events](custom-event-goals.md) for more specific tracking like button clicks - Use [filters and segments](filters-segments.md) to analyse which sources and campaigns drive the most conversions +- Explore [user journeys](user-journeys.md) to see the paths visitors take before and after converting ## Edit a Pageview Goal diff --git a/docs/user-journeys.md b/docs/user-journeys.md new file mode 100644 index 00000000..e7e88e57 --- /dev/null +++ b/docs/user-journeys.md @@ -0,0 +1,95 @@ +--- +title: User journeys +description: "Explore the paths visitors take on your site. Start from any page or event and see what they do next, or work backwards from a conversion to see what led them there." +--- + +import useBaseUrl from '@docusaurus/useBaseUrl'; + +The **Explore** tab lets you map the paths visitors actually take on your site. Pick any page, goal or custom event as a starting point and see what they did next. Or work backwards from a conversion to see what led visitors there. + +* Works with all your pages, pageview goals and custom events. No extra setup required. +* Pages from the same directory are automatically grouped to reduce noise and surface patterns more clearly +* Individual pages within a group are also selectable if you want to drill into a specific URL +* Shows "No further action" at each step so you can see how many visitors dropped off +* Displays the conversion rate for the full journey you are exploring +* A refresh button clears your selection so you can start over with one click +* All existing dashboard filters apply, so you can narrow journeys by traffic source, country, device or any other dimension + +
+})
+
+
+## How to use user journeys
+
+Open the **Explore** tab from the navigation bar at the top of your dashboard, alongside Goals, Properties and Funnels.
+
+You will see a list of your most visited pages and most triggered events. Select one to begin exploring the journey.
+
+Each column shows the next step in the path:
+
+* **Starting point:** the page or event you choose as the entry to the journey
+* **1 step after:** what visitors did immediately after the starting point
+* **2 steps after:** what visitors did after that, narrowed to those who followed the path so far
+
+Click any item in a column to select it and load the next step. The conversion rate in the top right updates to reflect the share of starting-point visitors who reached the selected item.
+
+To clear your selection and start over, click the **refresh icon** in the top right corner.
+
+## Starting point vs end point
+
+You can explore journeys in two directions.
+
+**Starting point:** Begin from a page or event and follow what visitors did next. Use this when you want to understand where visitors go after a key page, such as your pricing page or your post-signup confirmation screen.
+
+**End point:** Begin from a conversion goal and work backwards. Use this when you want to understand what path led visitors to a specific outcome, such as a trial signup or a completed purchase.
+
+## Understanding the list
+
+By default, the list shows the 10 most visited pages and most triggered events. If the page or event you want to explore is not visible, click **More** to expand the list or use the search box to find it by name.
+
+**Grouped pages** are shown with a folder icon. Plausible automatically groups pages that share the same directory, so `/blog/post-1` and `/blog/post-2` appear together as `/blog`. This keeps the list readable and makes patterns easier to spot. Selecting a group lets you explore journeys across all pages in that section at once. For example, selecting `/docs` shows what visitors did before or after visiting any documentation page, and selecting `/blog` shows paths around any blog post. This is much more useful than analysing one page at a time when you want to understand how a whole section of your site fits into the visitor journey. You can still select any individual page within a group if you want to drill into a specific URL.
+
+**Goals and custom events** are shown with a cursor icon, so you can tell at a glance whether an item is a page or an event.
+
+**No further action** appears at every step and shows how many visitors did not trigger any recorded page or event after that point. This is your drop-off count.
+
+## Filtering user journeys
+
+User journeys respect all your existing [dashboard filters](filters-segments.md). Apply any filter before or after you open the Explore tab and the journey data will update to reflect only that audience.
+
+For example:
+
+* Filter by a traffic source to see the paths visitors from a specific campaign or referrer take
+* Filter by country to compare how visitor behaviour differs by region
+* Filter by device to check whether mobile and desktop visitors follow the same paths
+* Filter by a landing page to trace journeys that started from a specific entry point
+
+This makes user journeys useful not just for understanding overall behaviour but for diagnosing specific segments of your audience.
+
+## Conversion rate
+
+The conversion rate shown in the top right is the percentage of visitors at the starting point who completed the full journey you have selected. The number in parentheses is the raw visitor count.
+
+For example: a conversion rate of 9% (16) means 16 out of the starting-point visitors followed the complete selected path.
+
+The header also updates to describe the journey length, for example "2-step user journey" when you have selected a starting point and one additional step.
+
+## When to use user journeys
+
+User journeys are best for open-ended exploration. Use them when you want to understand actual visitor behaviour without defining a hypothesis upfront. Good use cases:
+
+* See where visitors go after landing on your homepage
+* Find the most common path leading to a signup
+* Discover which pages visitors view before contacting support
+* Check whether visitors who hit a 404 continue browsing or leave immediately
+* Work backwards from a conversion to see which pages preceded it
+
+For measuring a specific predefined path with drop-off rates at each step, [funnel analysis](funnel-analysis.md) is a better fit. Use funnels when you already know the flow you want to measure. Use user journeys when you want to discover flows you did not expect.
+
+---
+
+## What's next?
+
+* Set up [pageview goals](pageview-goals.md) or [custom event goals](custom-event-goals.md) to use as starting or end points in your journeys
+* Use [funnel analysis](funnel-analysis.md) to measure drop-off across a fixed multi-step sequence
+* Use [filters and segments](filters-segments.md) to explore journeys for a specific audience, such as visitors from a particular country or traffic source
diff --git a/sidebars.js b/sidebars.js
index a4f0cd40..5b0bf491 100644
--- a/sidebars.js
+++ b/sidebars.js
@@ -54,6 +54,7 @@ module.exports = {
'Goals and Events': [
'goal-conversions',
'funnel-analysis',
+ 'user-journeys',
'ecommerce-revenue-tracking',
'outbound-link-click-tracking',
'file-downloads-tracking',
+