0

Looking for a best practice for the following scenario:

In a traditional webapp, we perform analytics on logs based on http GETs. The project in question leverages HTML5, jQuery and Mustache.js to dynamically render templates from JSONP calls. The views respond to onhashchange events to create bookmark-able URLs, with parameters via jQuery BBQ.

My issue is that the hash isn't passed to the server, so these changes in URL aren't going to show in regular access logs. The best solution that's been offered so far, is to track the hash changes locally, and PUT / POST them to a service when the browser fires onbeforeunload.

I'm interested in other solutions for tracking local hash history changes on the server, I can't use Google Analytics for this.

lars
  • 99
  • 1
  • 14

1 Answers1

0

Call a simple file (track.html, track.php, track.asp) depending on your server architecture. The file can be empty.

onhashchange, do an AJAX call to the simple tracking file with the hash as the querystring (track.html?hash=hashStringValue). This should show up in your access logs.

Justice Erolin
  • 2,869
  • 20
  • 19