Page URLs in Adobe Analytics

The pagename variable is populated via data layer.

The URL with hash is not collected as paginate unless your code is built to pass it to Pagename variable.

Your hash states are they all part of  a Single Page App(looks like it) you may need to pass the URL of of each page in question to an evar.

Do any of these replies provide an answer to your original question? If so, please mark the most correct answer. If not, can you provide some additional details to help the community better answer your question.

well, you are setting the "page URL" field but looking at the "pagename" variable in reporting! those are not the same!

see your screenshot from Launch, there's a field called "Page name", use this to get the "page" variable filled in reporting.

remark: we only overwrite the "Page Name" and leave the "Page URL" as is. that means, the page URL is always the URL the user can see, but we give the "Page name" custom values.

additional remark: a lot of people have a eVar (maybe the most important one for everybody) with exact the same value. the reason are "custom/exit/download links" which don't have a value in the default "page". that means, if you want to see eg. downloads per page, you need an evar with the "Pagename".

I was setting up Page URL like this:

Where %HashValue% was returning values after hash symbol like /login, /home etc. 

This resulted into getting Other in the reports instead of the actual values:

In your case, are you working with Page URL or Page Name field?

where and how do you set the pagename variable? are you sure the "pagename" is correct on the data sent to adobe analytics?

since we use this setup very often and haven't had any problems, it's hard to see/imagine a problem without access to your implementation...

Thansk ursboller​that seemed a good idea to me as well, and I did try sending only "after-hash" values like /login,  /home etc.

But I run into another problem, I started seeing just Other instead of the actual vlaues I was sending. Please see my original message, it's better described there.

Create a data element with window.location.href and it should give you the URL with #

maybe this is a feature from "old days" where the hashes where used as trigger points to scroll down a page (so basically if the same user has two pageviews and just the hashes changes, it is still the same page)

but since they are now used as "SPA" navigation, this is a completely other use case. now the change of the hash IS a new page.

but: think about NOT changing the settings but changing your implementation: in DTM/Launch override the pagename with only the hash value.

so basically instead of sending the full URL with hast, you override the pagename to only contain the hash (maybe with prefix). at least that's what we do on all our implementations with hash-navigation.

I am going to guess but are all these pages part of a SPA? Single Page app? If so I recommend you look at Direct call rules. They work great and are very efficient for state changes.

Soe trick to follow some SPA you need to disable first time load. You also should make sure you check logic for a user doing a manual reload.

GLTU