Code Authors

Posted: Sun Apr 06, 2008 3:50 pm

For others like me that like to look at pretty pictures of statistics I recommend the Google Analytics package posted below which uses the new (free) Adobe AIR runtime library.

I have found this software makes analysing my Google tracking stats much easier and it even provides some clever overlaying onto Google maps for an at-a-glance look at where your visitors are coming from.
Very user friendly and saves the hassle of having a browser open and logging in as the software does all that for you.

http://www.aboutnico.be

Newbie Joined: Jan 13, 2006 Posts: 63

Interesting (AIR beta). Have you looked into QuantCast?

Posted: Fri Apr 18, 2008 12:53 pm

I have not looked at QuantCast but I will now you have mentioned it Smile

I mentioned the widget above because when checking my analytics from Google, it becomes a complete pain having to navigate backwards and forwards in the browser and then wait again for the query to run but if QuantCast offer somthing similar or another method of tracking stats then I would certainly look at it.

Newbie Joined: Jan 13, 2006 Posts: 63

Uh oh...

Posted: Fri Apr 18, 2008 1:21 pm

Uh oh??

Newbie Joined: Jan 13, 2006 Posts: 63

Click the link to see the Uh oh...

Posted: Wed May 28, 2008 12:02 pm

Hmm, not sure why he says on the website it was a trial as mine still works perfectly.
Also works well with Ubuntu Smile

Client Joined: Sep 25, 2006 Posts: 47

I've never really looked at Google Analytics, but one of my colleagues runs quite a large site which uses vBulletin on a dedicated server. He said he was getting quite a high load on the server so he disabled webalizer and added Google Analytics. Apparently the difference is considerable, site loads a lot faster and the load has dropped from 1.5 to 0.3.

After what I have heard I am definitely going to have a play. Smile

Posted: Fri May 30, 2008 7:29 pm

It might just be Webalizer was not optimally set Wink

You see, Webalizer and most other stat tracking software shipped with cPanel etc is normally set to write the data to a log type file every hour, or less.
When you have a busy site, this means that the 'writing' almost never stops for a breather so is constantly using resources.
On my VPS because I don't need the stats deadly accurate and updated every hour, I have them set to update ever 'even' hour (2am, 4 am, 6am etc) which has reduced resources a heck of a lot.

It is a good point though about stat tracking as not many people with VPS or dedicated servers realise just how much resource is used for stat tracking.

Personally I find Google tracking good but their admin side of it is close to crap with having to keep switching back and forth between screens. Now I'm using the AIR driven tool it is an absolute pleasure to use.

Client Joined: Sep 25, 2006 Posts: 47

I'll mention that to him. Wink

From what I understand vBulletin has a feature to enter the code once and it then populates all the pages for you. Perhaps this is something we should consider for RN. I know we have discussed MS Analysis before, because the current stats module is cr@p.

Posted: Fri May 30, 2008 9:01 pm

You mean, enter the google tracking code somewhere and vbulletin populates that to the script (like putting it in footer.php)?

Client Joined: Sep 25, 2006 Posts: 47

Yes basically. I guess it is not difficult to do, although some people don't like messing with the code. I'll shut up now and go to bed. Laughing

Posted: Sat May 31, 2008 2:04 pm

Hmm, it's an idea though.
I think the editor might throw it out if was placed in one of the footer fields in admin->preferences but if/when we start using smarty templates it could be really handy.

Client Joined: Sep 25, 2006 Posts: 47

I inserted the code into one of my sites, now just trying to make sense all of the data. Laughing

Need to do some SEO to get the traffic up.

Client Joined: Sep 25, 2006 Posts: 47

I've tried it on one of my Nuke sites by adding it to the footer field and Nuke doesn't try to strip anything out, but Google doesn't recognise the code. I think it is because it should be immediately before the closing body tag.