Comments on: Tracking error pages from Wordpress

By: Suresh

Suresh — Wed, 06 Aug 2008 05:23:39 +0000

I was missing that tracking error page on my site, but after reading this useful post and implementing to track error page in wordpress script, now I am able to track easily. Thanks for sharing this awesome post.

By: Brian Clifton

Brian Clifton — Thu, 19 Jun 2008 13:30:12 +0000

Jeffery: That’s a good point, though you can also see this by clicking through on the page link in question in your reports and viewing the Navigation Summary report.

Thaks for the feedback.

By: Jeffrey Staub

Jeffrey Staub — Wed, 18 Jun 2008 14:25:10 +0000

Good Stuff. I have also found that it is great to know the referring page that led to the 404 so that you can trouble shoot the issue. The use of the document.referrer variable works. I use the following code which could be modified:

var gaJsHost = ((“https:” == document.location.protocol) ? “https://ssl.” : “http://www.”);
document.write(unescape(“%3Cscript src=’” + gaJsHost + “google-analytics.com/ga.js’ type=’text/javascript’%3E%3C/script%3E”));

var pageTracker = _gat._getTracker(“UA-xxxxxx-x”);
pageTracker._initData();
pageTracker._trackPageview(“/404/?page-not-found=” + document.location.pathname + document.location.search + “&page-linked-from=” + document.referrer);

Great book by the way!

By: Brian Clifton

Brian Clifton — Mon, 02 Jun 2008 19:50:43 +0000

Joost: That’s a very good point. Having a clear messeage as to what the error is, plus presenting options to the visitor so they have an alternative is a great way to recover the user experience session.

By: Brian Clifton

Brian Clifton — Mon, 02 Jun 2008 10:14:26 +0000

A twist on the same theme… this is an alternative script using variables available in the DOM rather than the GATC:

[Remember to change the value of domain.com in the script to your real domain name].

I prefer this method as it not effected by any changes that may take place for GATC.