What is a Page anyway?
In a traditional sense, a “website” is equivalent to a domain (like foo.com), and a “page” within that site is equivalent to a single specific URL (like foo.com/about). For many content-centric landing pages, or basic websites, this definition makes a lot of sense!
But today, most modern websites and web applications do a lot more than just serve static content pages at static locations. Their URLS are more sophisticated, often dynamic, and generally contain data in them.
is really an instance of a “Product Detail Page”
When analyzing interactions with your Product Detail Page, you generally want to look across all Product Detail Pages. You also don’t want to mix in interactions from different pages like the “Product Search Page,” or your main marketing website.
To scope your page-centered analysis to the right level of granularity, FullStory uses machine learning to identify general URL patterns across similar page structures, without requiring any instrumentation on your part, and uses them by default across the platform.
When you see Page analytics in FullStory, like in Click Maps, Scroll Maps and Segment cards, these are based on “logical pages” like aggregate Product Details Pages rather than concrete URLs which could contain a massive amount of variation. In this example, if a particular Product Detail Page gets enough traffic on its own, it’s possible FullStory will separate that one into its own logical page.
Because FullStory is constantly learning about your site’s URL and page structure patterns, logical pages will evolve over time and may cause data fluctuations for a given Page. The data you see is always using our best fit clustering at the present time, based on historical trends.
Example of Combining Multiple URLs into a Logical Page
Imagine you are shopping for blenders on ecommerce-co.com. You could see two different URLs for blenders with different words on the page, but this page is the same Product Details Page.
FullStory is able to use machine learning to know that counts should be combined across certain sessions by matching their UI structure, even if their content is different.
The fact that multiple URLs had the same UI structure allows us to interpret what parts of the URL are variable. Using that intuition, we can turn this:
into this (ie. The “Product Details” Logical Page):
Analyzing Specific URLs
But what if you want to know specifically how many people clicked on things related to your concrete URL
All Page Insights results respect the current segment. So adding a Visited URL Segment search for PATH is p/special-toaster-over-GHJAVFM/GR12330-1A will constrain your results to only users who hit that URL.
Keep in mind, if those users also hit other Product Detail Pages in the Page cluster, data from those page views will still be included.