Yoast: Building Page.ly Part4: Scalable and Fast Managed WordPress Hosting | Page.ly Blog http://t.co/ba32Hemn
![]()
Google Analytics for WordPress: my latest plugin
I just wanted to let you guys know that I've thrown the first version of my Google Analytics for WordPress plugin out there. You can download it from here, while you wait for me to write the page for it on this site!
It automatically tracks outbound clicks from posts, comments, blogroll, it tracks downloads, it can add search engines and it can track image search keywords as well... All your feedback is hugely appreciated!
Update: I created the page for the Google Analytics for WordPress plugin!






by Roy on 15 September, 2007 at 00:59
Yeah, this one rocks. Tested it, thought along, i'm loving it.
by Ron Klaren on 15 September, 2007 at 11:56
Thanks Joost!
I allready use your Robots Meta Plugin and I'm thinking about using this on as well, but can you tell me how this plugin differs from the Ultimate GA plugin?
by Joost de Valk on 15 September, 2007 at 13:42
Don't know that one to be honest, got a link?
by Ron Klaren on 15 September, 2007 at 21:46
There are a couple of other GA plugins, but this one is the most advanced as far as I know.
http://wordpress.org/extend/plugins/ultimate-google-analytics/
Regards,
Ron
by Joost de Valk on 15 September, 2007 at 21:47
As it looks to me, that one can't segment outgoing clicks and can't track image search keywords...
by Jared on 8 November, 2007 at 19:41
Joost,
Nice plugin, I've got it running on my blog right now. Hopefully time will tell how good it is.
by david on 9 November, 2007 at 15:15
Could you please take out the one level of directoy on your download? It's a minor thing to worry about, but it tripped me up when I dropped the main folder in my plugins. Thanks, and testing it out now.
by Joost de Valk on 9 November, 2007 at 16:48
@David: sorry, that's created by the WordPress svn servers...
by Johan on 10 November, 2007 at 10:29
Nice plugin but I do not like the fact that the JavaScript is placed on top of the page in the source code. Other trackers place this code at the end so it won't slow down the loading of the page.
Also, I prefer the plugin options to be in under the options tab and not under the plugins tab, but this is just a matter of personal taste :)
by Joost de Valk on 10 November, 2007 at 19:25
@johan: there's a reason for putting the script in the header, it makes the data way more reliable, and outbound click tracking can have some huge problems if the script isn't completely loaded yet...
by Efosa on 15 November, 2007 at 13:07
Thanks Johan. I had the same question on the placement of the Analytics code in the header of the HTML code as opposed to the bottom. Glad to see there is a good reason you chose that route. Thanks for your efforts!
by Massimo on 6 December, 2007 at 15:34
Great plugin! Works great! Keep up the great work!
by dave on 6 December, 2007 at 19:26
I gotta say this, I've had to deactivate this recently due to the fact that when you preview an article, GAPP will register it as a page view.
I never noticed this before until I started looking at all my data.
If you ever get this fixed I might reactivate, until then, I've resorted to the hardcoded method, which works nice in the header. I haven't check for any updates, so I'm sorry if this has been corrected.
Works good though, but maybe too good.
by Joost de Valk on 6 December, 2007 at 21:15
@dave: you got me there. Fixed that in the 2.1 release!
by Robert Irizarry on 13 December, 2007 at 17:14
With the new tracking code out, will you be updating the plugin to support it?
by Joost de Valk on 13 December, 2007 at 17:16
Working on that at the moment yes, expect an update in 2-3 days. That will ONLY use the new code though, no point in allowing you to choose in my opinion :P
by Andrew Biss on 12 March, 2008 at 21:12
Hi Joost,
Thanks for the plugin. One problem I noticed is that I was getting the outbound click tracking code generated into my RSS feed. This caused warnings from the RSS feed validator.
This may have been an interaction with another plugin. In any case I was able to work around this problem by modifying the plugin to check if it is being called when processing a feed.
I added checks for "is_feed()" at the statr of the functions "the_content", "comment_text", "comment_author_link" and "bookmarks". In each case if we are processing a feed then the buffer is returned unchanged.
Regards,
Andrew.
Pingback: Tutorial: Wordpress reacties tracken als doel in Google Analytics - MediaKip