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!
Related posts
- Extracting click data from Google Analytics
- Google Analytics plugin updated!
- Google Analytics and Google Image search: revisited
- Updated my Google Analytics plugin to track AdSense clicks
- Getting Google Analytics to extract keywords from Google Image searches
Want more WordPress tips?
You should subscribe to my WordPress Newsletter, as you'll get a whole lot more WordPress tips and tricks there! Also, subscribe to this blog right now with RSS, or daily or weekly emails!
Cats: Analytics, WordPress Tags: Display Advertising, WordPress Plugins
Both comments and pings are currently closed.
Yeah, this one rocks. Tested it, thought along, i'm loving it.
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?
Don't know that one to be honest, got a link?
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
As it looks to me, that one can't segment outgoing clicks and can't track image search keywords...
Joost,
Nice plugin, I've got it running on my blog right now. Hopefully time will tell how good it is.
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.
@David: sorry, that's created by the WordPress svn servers...
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 :)
@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...
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!
Great plugin! Works great! Keep up the great work!
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.
@dave: you got me there. Fixed that in the 2.1 release!
With the new tracking code out, will you be updating the plugin to support it?
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
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.