User-Defined Pages

Page definitions represent important destinations in a customer’s digital experience. Fullstory will automatically suggest page groupings and names using AI-suggested pages. You can also define pages manually or send page data using the API. Once pages are set up, anyone within your Fullstory organization can access pages across metrics, segments, journeys, and more.

Pages can be defined in multiple ways:

• AI-suggested
• User-defined (manual) - covered in this article
• Web API
• Mobile API

See Pages in Fullstory for a complete overview of pages or continue reading to learn about user-defined pages.

Creating user-defined pages

Fullstory supports defining and naming page groups directly within most areas of the application. Using a simple pattern syntax, you can group common pages together and give them a name, making pages easy to understand for anyone using Fullstory in your organization. No code is required to define pages within Fullstory.

Note: Mobile App pages must be created via the Mobile App Pages API.

To get started, navigate to the pages settings page:

1. Click your account name in the top left.
2. Click Settings.

3. Under Data Management, click Pages.

   For an overview of the page settings page, visit Pages in Fullstory.

4. Click Create Page to begin manually defining a page.

   

   You can edit the following fields:

   • Page Definition: Set the URL Rule(s) that will define the page. URL patterns can only match a single page definition. Fullstory will notify the user if there is a conflict.

   • Name: This label will be used elsewhere within Fullstory for search and analysis. Consider adopting a naming convention to make pages more useful.
     Click the purple sparkles to automatically generate name suggestions and a description.

     Note: If you're using the web API to define page names, the pageName value sent via the API will take precedence over any page names you manually define in Fullstory. 
   • Role (optional): Assign a role to the data. Learn more.
   • Description (optional): A brief description of the page that can be used by Admins and Architects to help with page management.

Query Parameters 

Websites sometimes use query parameters to manage site navigation. Utilizing query parameters when defining pages tells Fullstory to group pages by the query parameters.

For example, a documentation site might have menu items labelled "renters" and "owners", which correspond to URLs like docs.cargorentalsfs.com/?tab=rentals and docs.cargorentalsfs.com/?tab=owners, respectively. Adding query parameters to a page definition tells Fullstory to create separate pages for "renters" and "owners".

To use query parameters in a page definition, select “+ Query Parameter” in Data Studio. From there, you can define the key-value pair for the data you wish to track. If you wish to track a group of pages, you can use * as in the value field.

Syntax

URL rules are how Fullstory understands how to group your pages under a definition. It is a simple syntax that defines a pattern. Any URL that matches that pattern will be included under that label when creating charts and running searches. Rules are mutually exclusive and URLs cannot be matches under more than one rule. Definitions can have more than one rule, and in the case a URL could match to multiple rules, the most specific one will take precedent.

• Use * (wildcard) to match any single token at a position.
• Use ** to match all paths that start with a common prefix.
• Use [] to match groups of tokens at particular positions.

A single wildcard will match part of a URL path only at that part. For example, if the page you’d like to group is:

https://exampleapp.com/books/business

where “books” is a product category and “business” is a subcategory, you could create a subcategory grouping with this rule :

https://exampleapp.com/books/*

This rule would not group any subpages such as

https://exampleapp.com/books/business/booktitle

A double wildcard will match any paths that start with the non-wildcard prefix. For instance, if in the example above you wanted to catch all individual book pages you could use a double wildcard this way:

https://exampleapp.com/books/**

And finally, if there are specific values you’d like to target, you can use brackets. Continuing with our example above, perhaps there are several book categories that are related such as business, real estate, and economics. To categorize these all under the same rule, use brackets:

https://exampleapp.com/books/[business, realestate, economics]/*

Frequently Asked Questions

What if the URLs on my site use hash (#) paths?

Hash paths are sometimes used in URLs, particularly on single-page applications, as browsers don’t consider the path fragment after the hash as a separate page. The structure of these URLs look something like like this, https://mywebsite.com/#/login/foo, where the hash is the first URL path following the website domain.

By default, Fullstory does not take these hash paths into consideration when creating page definitions via our AI-suggested page algorithm, nor will they work properly when manually defining pages.

That said, there's a flag we can enable on our end to take these hath paths into consideration and properly categorize those pages. While this won't affect AI-suggested pages, it will allow you to manually create new page definitions that match the URL patterns on your site.

One thing to note, if you're utilizing anchor links across any of the domains you're capturing in Fullstory, enabling this flag would mean that all hash fragments would be considered a page view across all domains. Anchor links are actually the reason we don't have this flag enabled for customers by default since we found that most customers would not want these to be counted as a new page view.

If you'd like to us to enable this flag for your account, please have an Admin user reach out to our Support team to make that request.