page vs page name dimension | Community
Skip to main content
V
victortranatx
Level 2
October 21, 2024
Solved

page vs page name dimension

  • October 21, 2024
  • 1 reply
  • 1139 views

What is the distinction between page vs page name? I have been using page name as my primary dimension and just noticed the 'page' dimension. Is there a proper or better one to use over the other?

 

Thanks,

Victor

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by bjoern__koth

Hi @victortranatx 

your "Page Name" is a custom dimension, eVar13 whereas the Page dimension is the standard Adobe dimension, filled by the s.pageName attribute in your tracking calls.

 

"Page" is limited to 100 Bytes, whereas an eVar is able to capture 255 Bytes, so 2.5 times longer values are possible which is important in your case because your values seem quite long and may get truncated at some point. So, eVar13 / Page Name can serve as a backup.

 

On top of that, "Page" is only available in page view calls, where as an eVar can also be broken down when you want to analyze user interactions / custom link tracking.

So, as a best practice, I would always do what you can see in your example. Use the eVar as backup / extension of your Page dimension.

1 reply

tushaar_srivastava
tushaar_srivastava
Level 6
October 21, 2024

Hi @victortranatx 
Please refer Adobe Analytics Page and Page Name Dimensions:

V
victortranatxAuthor
Level 2
October 21, 2024

Tushaar, that second link didn't work for me.

 

I wanted to know if there was any real difference between the two dimensions as far as in-use. It looks like they are basically the same and can be used interchangeably.

 

Please let me know if that is not the case. 

bjoern__koth
Community Advisor and Adobe Champion
bjoern__kothCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
October 21, 2024

Hi @victortranatx 

your "Page Name" is a custom dimension, eVar13 whereas the Page dimension is the standard Adobe dimension, filled by the s.pageName attribute in your tracking calls.

 

"Page" is limited to 100 Bytes, whereas an eVar is able to capture 255 Bytes, so 2.5 times longer values are possible which is important in your case because your values seem quite long and may get truncated at some point. So, eVar13 / Page Name can serve as a backup.

 

On top of that, "Page" is only available in page view calls, where as an eVar can also be broken down when you want to analyze user interactions / custom link tracking.

So, as a best practice, I would always do what you can see in your example. Use the eVar as backup / extension of your Page dimension.

Cheers from Switzerland!
    Terms & ConditionsAccessibility statement

    Loading footer...