Join us January 15th for an AMA with Champion Achaia Walton, who will be talking about her article on Event-Based Reporting and Measuring Content Groups!
SOLVED
page vs page name dimension
1 Accepted Solution
Correct answer by
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!
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.
Correct answer by
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!
