Sample Journeys

Looking for inspiration? Look no further! In this article, we’ll share how eCommerce Product Managers, SaaS Product Managers, and UX Designers use Journeys to analyze their data. 

This is part two of a two-part series on Journeys. If you'd like to learn more about the components of a Journey, how to get started, and how to analyze your data, check out part one below.

• Part one: Introduction to Journeys
• Part two: Sample Journeys

Journeys for eCommerce Product Managers

Frankie at FruitShoppe, a small online fruit vendor, wants to better understand user journeys. She’s interested in discovering how users most commonly navigate around the site, but she isn’t quite sure where to begin. Journeys can help! 

To get started, Frankie creates a Journey that starts with the Most Common Pages and Events on her site. Her team has already configured their page settings and instrumented important events (like adding a product to a cart) using the FS.event API.

When she clicks Explore, Frankie sees the 5 most common user Journeys for her site. Now, she has insight into how users typically navigate through her digital experience. 

Journeys for SaaS Product Managers

Paul the Product Manager wants to understand how his company’s most valuable customers spend their time in the product immediately after logging in. To run this analysis, he first completes a few setup tasks: 

1. Paul checks his Page Settings to confirm they’re correctly labeled and defined. 
2. Paul instruments an event using the FS.event API to capture when customers log in to his product. 
3. Paul identifies high-value customers using the FS.event API.
4. Paul creates a segment of high-value customers.   

Then, Paul creates his Journey! He looks for Journeys that start with the event “Login button - home page.”

Then, he narrows his results to the “High Value Customers” segment. From here, he can explore the most common paths high value customers take after logging in to their accounts.

Journeys for UX Designers

Debbie the Designer just launched a new UI to a group of Beta users. She hopes that the new UI will make it easier for users to find the Admin Dashboard page in her application, a page that’s been tricky to find in the past! To start her analysis, Debbie completes a few setup tasks:

1. Debbie identifies Beta users using the FS.setUserVars API.
2. Debbie creates two segments: one segment for Beta users, and one for all other users. 
3. Debbie checks her Page Settings to make sure that the Admin Dashboard page is properly labeled and defined. 

Debbie is ready to begin! She creates a Journey that ends with the Admin Dashboard page.

Then, she uses the Segment dropdown to compare how the steps users take to reach that page differ between Beta users and other customers.