Skip navigation.
Home

Google Analytics - part the first

A week or two ago, my Google Analytics (GA) invite arrived. Ironically, a few days before in a work meeting with some Google Ad Sales gents I'd asked if they could provide an invite. So much for "who you know". ;-)

So I figure, I'll grab the GA module for Drupal (which powers this site) and see how it all goes, what it's like and so on.

Seeing as my "primary" goal for all the Software I write is for people to use it... hmm actually that's not quite true. The primary goal is for ME to use it. If others do? Well that's just icing. :-)
Anyway, it's kinda cool to see a new release go out and watch the hordes come flocking in to grab the raw tarball. Now with standard webserver log analysis, it's easy to get numbers.
With something like GA it's a little harder, but seems do-able. GA give an example using a javascript "on-click" function to do so.

Javascript? Yup, that's the way page tagging tools like GA and co work.

Now can anyone else see an immediate and problematic issue?

Those who use Lynx or Wget and related friends don't show up. Or to put real numbers around things: Since I released AWFFull v3.5.1 yesterday, and via the logs I currently have access to, about 20% of the downloads done won't show up in Google Analytics anway (6 from 31 for those that really care. :-) ).

Ouch.

And that's not even counting things like normal browsers that don't accept javascript. It's going to be interesting to track just how... inaccurate GA does get for a site like mine.

Syndicate content