This feature is available to certain members of the FullStory Beta Program. Sign up here to beta test new features, share feedback directly with Product Managers, and influence our vision for the FullStory platform.
- Introduction to Page Flow
- How Pages are Defined in FullStory
- What does Unknown mean?
- The page I want to see is grouped with other pages. Can I ungroup them?
- Can Page Flow show Native Mobile data?
- Can I see other types of events in addition to page views, or more steps in the journey?
- Why is my selected Page also listed as a previous or next Page?
- Example Use Cases
Introduction to Page Flow
The Page Flow Dashboards card allows you to analyze micro user journeys. Specifically, the previous and next Pages viewed from a given Page. In addition, you can see the percentage of page views that were “Entry” or “Exit” Pages, meaning the user started or ended their session on that Page.
Like with all quantitative data you see in FullStory, you can watch sessions that correlate with any Page Flow path. This can help you really understand how users got from one Page to another and the context of what they were doing at that time.
How Pages are Defined in FullStory
Pages are either single URLs or groups of URLs that you would commonly think of as the same page or page type. By default, FullStory uses machine learning to identify general URL patterns across similar page structures and group them into Pages. If you see brackets [ ] or asterisks * in your Pages, that means that multiple URLs are grouped together into a single Page.
You also have the option to name Pages, modify the URL rules for any Page, or define your own Pages. Learn more about Pages in FullStory.
What does Unknown mean?
If you see an Unknown node on a Page Flow, that is grouping together page views for URLs that are not already defined as a Page. By default, FullStory will create up to 120 Pages. Some large websites will have traffic to URLs that aren’t part of these 120 Pages. You can add more Pages to capture that additional traffic in Settings > Pages by clicking on “Name Page.”
The page I want to see is grouped with other pages. Can I ungroup them?
Yes! By default, the Pages shown are based on FullStory’s Learned Pages algorithm. However, if you’d like to modify them or create new Pages to override them, you can do so in Settings > Pages.
Keep in mind that Page rule changes do not apply retroactively, so you will need to wait for more sessions to see data for new Pages.
Can Page Flow show Native Mobile data?
No, since Pages are URL-based, this card type will only show data from web sessions.
Can I see other types of events in addition to page views, or more steps in the journey?
Currently the Page Flow card only shows one Page viewed in either direction from the specified Page. If you are interested in seeing other types of events or additional steps, please reach out to our support team to let us know more about your use case.
Why is my selected Page also listed as a previous or next Page?
Sometimes users will trigger a new page view of the page they are already on, so this will show up as a previous and next Page. This can happen if the user refreshes the page, or if something causes the page to automatically refresh. This will also happen if a user navigates between different URLs that are defined as the same Page. For example, between blog posts that are both categorized as a single “Blog Article” Page.
Example Use Cases
“Where is the most common place users come from before viewing this page?”
- Create a Page Flow card centered on the Page in question, in this case the PLP Page
- Look for the first/highest volume previous Page
The Homepage is the most common Page users see before viewing the PLP Page.
“Did my A/B test change where users navigate next from this page?”
- Create a Page Flow card centered on the Page in question
- Drill down to a Segment for the control variant of the A/B test
- Duplicate the card
- Change the Segment on the second card to the test variant
- Compare the “Next Page” data across the two cards
The test variant increased the “Exit” percentage (or bounce rate) from 1.1% to 17.4%, so the control is doing a better job of keeping users on the website.
“For users that dropped out of my funnel at this page, where did they go instead?”
- Start with a funnel, and determine which Page you’re interested in learning more about. In this case, you want to know where users went after the /market Page if they didn’t go into the /cart Page.
- Create a Page Flow card centered on the /market Page.
- Look at common next Pages aside from the /cart Page.
For users who didn’t go from the Market Page to the Cart Page, the most common alternative was to leave the website. For users who remained on the site, most went to the Homepage or Login/Signup Pages instead.