1.5.0: A number of bugfixes and improvements introduced, namely:
fixed the problem with tracking code on the pages requested through HTTPS(SSL), following the instructions at http://www.google.com/support/analytics/bin/answer.py?answer=31846&query=SSL&topic=&type= (kudos go to: toob, Peter Craume, Nils Dehl, Henrik Andersen, Tim Kleigrewe – did I miss someone?) Sorry guys, it took me a long time but I did it!!!
reverted the change in 1.2 that disabled tracking code insertion in BE. The feature stopped working in 4.0 due to the changes in how caching is handled in the core. I always thought that filtering your own traffic should be done in analytics profile, now I have an excuse! (thanks go to: Dennis Riedel, Dmitriy Osadchiy)
configuration format change – now all options are nested under page.config.tx_m1_google_analytics. The old configuration options (for example, page.config.googleAnalytics_account) are still working for backwards compatibility.(thanks: Soeren Schaffstein)
new option: page.config.tx_m1_google_analytics.trackDownloadsFrom lets you list the top level directories on your website where the downloads will be tracked from (thanks: Marcel Burkhalter)
new option: page.config.tx_m1_google_analytics.pageName -lets you pass a parameter to the main call to urchinTracker. (suggested and written by Soeren Schaffstein)
1.4.0: added support for all _u... custom tracking variables (thanks: Bjoern Kraus)
1.3.0: moved the tracking code to the end of <body> container, following Google's change in instructions (thanks: Errol Mars)
1.2.0: disabled code insertion during Backend view or FE editing (thanks: Jan-Hendrik Heuing, Ingo Renner)
1.1.1: documentation quirks fixed
1.1.0: redone completely, documentation written