User experience analytics - navigation paths & page information

[Joyi]

Hi all, we've been trying to set up the User Experience Analytics on our service portal for the org. 

My question is related to the "Navigation paths" and the "Pages" dashboards. 

For Navigation paths, this is what we are getting from a dev instance: 

"Service catalog item" and "Topic pages" are just grouped together with no way for me to drill down to see what catalog items and topic pages people are actually browsing through. As such, this information is meaningless to me when I'm trying to decide what's important in my portal. 

The same thing when it comes to "Pages"

Here, we can see requests account for more than 50% of the traffic. When we drill down, you can see a majority of users are coming from requests and going to other requests. But why are these "requests"? 

Am I missing something here? Or is the analytics just not really helpful at all?

What do I need to do to be able to see the topic pages and the catalog items people are actually browsing through?

[kaushal_snow]

Hi @Joyi ,

You have to ensure that each catalog item and topic page has a unique URL or identifier, define custom page records using the sp_page table, create custom dashboards focused on these elements, implement event tracking for user interactions, and review the configurations of pages labeled as Requests to ensure accurate categorization and tracking....

If you found my response helpful, please mark it as ‘Accept as Solution’ and ‘Helpful’. This helps other community members find the right answer more easily and supports the community.

[Joyi]

Thanks for the reply. But I need more information. 

"You have to ensure that each catalog item and topic page has a unique URL or identifier, define custom page records using the sp_page table"

Are you suggesting I need to create an entry in the sp_page table for every single topic and catalog item we have? 

If so, that would be a complete maintenance nightmare. At the moment, the "Service Catalog Item" and the "Employee Topic" pages are standard pages that populates with the relevant catalog item and topic information. The Page Title is dynamically pulled from the catalog item or the topic itself:

I'd need to create 1,480 topic pages and another 865 catalog pages that are all identical to each other just for the sake of the unique page names being pulled into analytics... This is not even mentioning the 10K+ knowledge articles we have.

Why is the ServiceNow analytic solution not able to track user analytics based on this dynamic page title!?