Seeing the same page in 2 different formats in page visit reports | Community
Skip to main content
Level 2
Feb 5, 2024 4:02 PM UTC
Solved

Seeing the same page in 2 different formats in page visit reports

When looking at our page visits in workspace, we see the same page listed twice with different volume of visits e.g.

https://domain.co.uk/page/subpage

and

domain:page:subpage

 

Looking at the debugger on the page I only see pageName puled through as domain:page:subpage

Does anyone know why we see this duplication?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Jennifer_Dungan
Jennifer_DunganAccepted solution
Level 2
Feb 5, 2024 11:05 PM UTC

This is what I was going to ask 🙂

 

What is the distribution of "url" values vs curated page name values? Are you talking about a small percentage of pages that are missing the curated name, or a large percentage?

 

If no pageName is passed, Adobe will use the URL instead... it's possible that you have some scenarios where the code to populate the page name is failing, or maybe there are multiple rules for different scenarios where the page name wasn't set at all....

 

You may have to try and breakdown the URL version to see if there is a pattern to the scenarios where only the URL is populated, then try to test those specific scenarios to figure out what is happening.

2 replies

RobertBlakeley
New Participant
Feb 5, 2024 5:46 PM UTC

One possibility is that the page name is not set in some use case.

Page Name is a required field for page calls (as opposed to link calls). If the page name is not set, Adobe defaults the page name to the URL.

Translate
Jennifer_Dungan
Jennifer_DunganAccepted solution
Level 2
Feb 5, 2024 11:05 PM UTC

This is what I was going to ask 🙂

 

What is the distribution of "url" values vs curated page name values? Are you talking about a small percentage of pages that are missing the curated name, or a large percentage?

 

If no pageName is passed, Adobe will use the URL instead... it's possible that you have some scenarios where the code to populate the page name is failing, or maybe there are multiple rules for different scenarios where the page name wasn't set at all....

 

You may have to try and breakdown the URL version to see if there is a pattern to the scenarios where only the URL is populated, then try to test those specific scenarios to figure out what is happening.

Translate