You can clone with
HTTPS or Subversion.
This is the original post here : [http://forum.piwik.org/read.php?2,90224]
I hope I'm not missing anything, but I thought I'd post something in here before I went crazy. I have built an AJAX application that relies on hash tags to navigate through the page. We need to keep track of each of the individual hash tags, but the only report I'm aware of that shows the pages that a user has visited is logging in to the Piwik Dashboard and going to Actions>Pages. I've attached two screenshots to help show my point. One is of the Piwik interface and you can see one of the files (2551-0.php) is the only page in it. The second screenshot shows my database and the log_action table showing that there are different hash tags being recorded for 2551-0.php.
My question is if I'm missing something and need to set a preference somewhere to show all the different hash tags within a given page, or if this is a (un)known issue that has(n't) been addressed.
Response by matt:
you are right this is an issue that hasn't been dealt with yet. What happens is that we record the pages with the hash, but then at archiving time, we actually aggregate on the URLs without the hash.
we could probably easily allow to keep the hash values and show stats for each hashvalue. please create a ticket if you want this
Keywords: ajax, hashtag, hash, hash value
Screen Shot 2012-06-12 at 2.33.53 PM.png
Screen Shot 2012-06-12 at 2.33.32 PM.png
There are several ways we could deal with this issue:
Also see this interesting post for a use case of tracking with hash tags: http://www.e-nor.com/blog/web-analytics/tracking-traffic-from-press-releases-in-google-analytics
If I could offer my opinion, in my case, this would be great as a global setting. I have about 700 sites (and climbing) that are using this hashtag feature.
Alternatively we could also have a setting "Disable hash tags" which could be enabled by default, where hash tags are used for campaigns tracking (eg. #pk_campign=X&pk_kwd=Y), but are removed before being recorded in log_action.
Let's do this new default setting (disabled hash tag, default is disabled, when enabled it will track each hash tag as different pageview).
I think it's important to be consistent between the actions report and the database. This means that when hash tags are enabled, they should be recorded in the DB and shown in the pages report. When they are disabled, they should be included in neither of them.
Here is a proposal spec:
In ac59017: Fixes #3232, add ability to discard URL fragments when tracking for all websites or for just some websites.
In 3069034: Fixing test failure regression introduced in previous commit.
In 4124ad4: refs #3232 Minor changes
Keep Page URL fragments when tracking Page URLs [ No (default) ] ```
SELECT values are eg.
* No (default)
This way the setting is not very visible (good because it's not used often) and it does not add more horizontal scrolling.
In da85ebe: Fixes #3232, remove keep url fragments column in website table and move to under URLs column in edit mode.
Keep Page URL fragments when tracking Page URLs [ No (default) ]
In d8dd525: Refs #3232, tweaks