Mobile App Pages in Fullstory

What is a Mobile App Page?

Note: Mobile app pages can only be created in code using the Mobile App Pages API. Pages defined manually in Fullstory and through machine learning are currently only supported for web.

A mobile app page is a section of your app based on functionality. You might refer to these in your app as screens. At Fullstory, we use the term Page universally across web and mobile. This is because they represent the same basic concept and are used to power the same insights in our analytics features, like Heatmaps and Journeys.

Pages can be searched by name or other properties. You can only have a single active page within your app at a time. They cannot overlap, and nesting is not supported. Your app can be divided into pages in the way that is most appropriate for analysis, whether the boundaries of those pages are tied to boundaries in your app structure – Android Activities and Fragments or iOS UIViewControllers – or not.

Please be aware of the following criteria and best practices to ensure you unlock all of the potential benefits this feature provides:

• Only one single page can be active within your app at any given time
• Pages cannot overlap
• Pages cannot be nested within each other
• Define your Pages in a way that best suits your needs in terms of analysis, irrespective of potential boundaries in your app structure due to developmental practices

Note: Mobile App Pages is only supported on Fullstory for Mobile Apps SDK 1.38.0+. Additionally, WebViews are currently NOT supported (this includes Cordova/Capacitor apps that are WebView-based).

Creating Mobile App Pages in Fullstory

Mobile app pages can only be created in code using the Mobile App Pages API. Pages defined manually in Fullstory and through machine learning are currently only supported for web. To learn more about creating Mobile App Pages via our API, see our developer docs for Android, iOS, and React Native.

Note: There is a limit of 1000 API-defined pages defined per account. This limit is shared across mobile and web.

Best Practices - Naming Mobile App Pages

Fullstory's Pages are designed to support aggregate and omni-channel analyses for any API Defined Page captured in Fullstory. Dependent criteria filters available in Fullstory eliminate the need to use the platform source as a prefix or suffix for your page names.

Our recommendation is to not use any prefix or suffix on the page names for API Defined Pages. This will allow you to see omni-channel (or cross-platform) Journeys, and be able to easily see insights on aggregate data in Metrics and Funnels across all platforms while still being able to drill down into specific platforms with a few clicks of your mouse.

Simply name your API pages that exist in multiple platforms with the exact same name to unlock the ability to view your data cross-platform with ease. Fullstory is able to detect what platforms your Pages are coming from, and will provide that information to you in Settings > Data Management > Pages.

FAQ

Why do I see adjusted time frames in Page Insights and Page Flow cards?

When new Pages are defined through the Mobile Pages API, their data is captured on a go-forward basis only. Therefore, if you look at a Click Map or Page Flow card for that mobile app Page, and your original time period starts before the Page was created, Fullstory will let you know that the data actually only goes back to the day the Page was created–and will automatically adjust the start date of your time range to reflect this.

What does it mean when I see a Page that is Not Defined?

When you see a Page that is Not Defined, this means that there is a portion of your mobile app that is not calling the Mobile App Pages API with a page name. In order to better understand what areas of your app are not instrumented and getting grouped into Not Defined, you can create a Dimensionality card in Metrics or Dashboards for events where the Visited Page = Not Defined, and Grouped by App View Name.