However I need to convert this so it will work with the new Async tracking code which is now standard. Can you confirm if this code is correct?

Jquery:
_gaq.push(['_trackPageview', ('/outgoing/' + jQuery(this).attr('href'))]);

JavaScript:
_gaq.push(['_trackPageview', ('/outgoing/' + this.getAttribute('href'))]);

Appreciate any help you can give with this!!

See: http://cantonbecker.com/random/outgoing.png

We’re trying out this code on http://asiafoundation.org

I can’t figure out what might be causing this. I expected out pagecount to inflate somewhat, but this looks like some huge portion of our internal clicks counting as bogus /outgoing clicks. Our pagecounts have *doubled* since dropping in this code.

Thanks for any ideas!

This article may be before the _trackEvent() method was released. But in my opinion Event Tracking is far more appropriate for tracking outbound links than _trackPageview().

See: http://code.google.com/apis/analytics/docs/gaJS/gaJSApiEventTracking.html

Eg: _trackEvent(category, action, opt_label, opt_value)

So with an outbound link it might look something like this:

_trackEvent(“links”, “outbound”, “link name”, 2)

Where the category = links
The action = outbound
The label = link name
Value = 2

This is also more robust because technically you could assign a value to each outbound click (useful for affiliates / shopping compare sites etc..) in the example above I specified a value of 2.

If your anchor tag has a name attribute or title for that matter, you could pass in that value for the link name to help identify it, or you could just take the href.value

eg: link name

Hope that helps.

Thanks for the tips, I have used them on my website and have yet to see if they work!

Anyhow, I just took a look through the rest of your blog and some of the posts are outstanding. I will definitely be subscribing!

Thanks,

Dave