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?

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.

Hi All, it seems I found an explanation. I contacted Adobe ClientCare and they replied the following:So I've just  requested this query string stripping to be disabled, let's see...Strangely I couldn’t find any info on this, so it looked to me like a bug in AA.Thanks all for your suggestions!

I've checked that... There are no processing rules at all:Should I ask Adobe to check Vista rules?..Did you guys work with history fragments and were they properly displayed in AA?thanks

I exported Page URL from the warehouse. It contains full URLs, with hash symbols and values after it.So it means that it's getting truncated somewhere between the warehouse and AA reports... any ideas?thanks

I don't set Page Name at all.I set Page URL within Launch as usual:I'm sure that it picks up the hash part because I see it in Adobe Debugger. So the URL is sent to Adobe in full (with hash), but in the reports it's displayed truncated (without hash).Are you saying that the only way to get the hash ...