- Post History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
03-12-2025 07:39 PM - edited 06-30-2025 09:39 AM
User Experience Analytics: Yokohama Edition!
Overview
With the Yokohama release, we've made understanding your application usage and gaining insights easier than ever! We re-platformed and re-designed User Experience Analytics (UXA) to be more performant, scalable, and flexible.
Immediate changes you will notice:
- We revamped the user interface of the dashboard, so navigating metrics between your users, sessions, pages, and events is more intuitive.
- And, we are so excited to introduce advanced querying features that allow you to filter your users and events more granularly than ever before.
- We moved User Experience Analytics under Platform Analytics in the All Menu, so it's grouped with all of your other analytics tools.
Read more about these highlights below, and make sure to watch our Platform Analytics Academy enablement session on the User Experience Analytics Yokohama release.
Simplified, intuitive user interface
The User Experience Analytics menu item is now organized under Platform Analytics in the ServiceNow All Menu, so you can jump into it more easily.
In addition, the menus within the User Experience Analytics dashboard have been reorganized, so you can more easily find your usage metrics.
Funnels are now easier to navigate to and easier to read, and we also removed "Users flow" since it was redundant to the information provided in Navigation Paths. These UI changes provide a more unified, cleaner look and feel so you can find the insights you need quickly.
Deeper insights into usage
New advanced filtering capabilities have been unlocked as a result of the re-platform. Now, User Experience Analytics viewers are able to:
- Filter data in the cross-application view, so you can understand how segments of users adopt your applications at a high-level and at-a-glance.
- Filter events by event properties, so you can analyze user interactions with specificity. For example, the "View Knowledge Article" event in Employee Center can now be filtered by its properties, such as Article Title or SysID. These filters can also be used in funnels and cohorts to add specificity in user journey completion and cohort behavior.
- Create custom user property filters, so you can analyze application usage like page views and events by user segments defined from your sys_user data. Then, add your custom filter to any visualization in User Experience Analytics.
Additional improvements
The new User Experience Analytics data architecture improves performance and scalability so more data can be calculated more quickly! Additional improvements include:
- Longer user history, extended to two years.
- Optimized metric calculation like Percent time on app and Average page duration.
- Client, Network, Page Load, and Server Time are now aggregated together in the same visualization.
Read about all of this and more in the User Experience Analytics Yokohama release notes, and stay on the lookout for new and updated articles on User Experience Analytics in the Community. 🎉
Happy upgrading!
- 3,269 Views
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
A "return user" is someone who accesses the same application or performs similar actions after an initial visit, within a defined time window like user who visited in last 7 days or last 30 days etc.., Ex: If a user visited application for the 1st time in June & again visited the application in July/August then that user marked as a return user , after Yokohama upgrade how the user is marked as return user when his First Session & Last session is on same date & time & avg time duration is 0.
Can anyone explain how service now UX analytics works for return user after Yokohama Upgrade
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Anyone know how to fix the truncation on the data labels for Data Foundation > Pages, select a page, scroll down to "Previous page" and "Next page"? They don't seem to be tied to existing glide.chart properties for truncation.