Traffic Analytics

Google Analytics is one of the many in the market at the moment. There are others like Clicky. Am sure there are other commercial products?

What I'm suggesting is to rename GoogleAnalyticsPlugin to TrafficAnalyticsPlugin where it can support user-chosen analytics. All under one plugin. Ease of management. It should be noted that different analytics provide different form of information, or rather the layout/format.

(Potential) issues?

• Is there really a need for more than one analytics per site? - enable/disable
• Different analytics different code-layout - creates many and large branches in code
• Module is heavy loaded - possible stress on the server? Negligible.

The biggest argument against this is, it's useless/pointless.

-- Contributors: KwangErnLiew - 14 Jan 2007

Discussion

I think the point here is not to allow the site to report to multiple traffic analytics sites at once (which might be possible) but to allow the site admin to install this plugin and set it to report to whichever Analytics service they choose. This, as apposed to creating a separate plugin for each service. Hardly useless/pointless.

-- TravisBarker - 14 Jan 2007

• There are countless analytics services, each with different ways to track the visitor. Some put javascript in the head, some in the body. To cater for each case will create many and large branches in the code.
• Server load will not be impacted. Typically there will be one request for each analytics service. Page load will be affected by the speed of that service: how fast does the server respond.

-- ArthurClemens - 16 Jan 2007