Google Analytics - Changelog - Web Tracking (ga.js)

Release 2013-02 (February 13, 2013)

2013-02-13T08:00:00Z

The following changes have been pushed to the latest version of the tracking code:

Added support for specifying local currencies with _set, e.g. gaq.push(['_set', 'currencyCode', 'EUR'])

Release 2012-02 (February 24, 2012)

2012-02-24T08:00:00Z

The following changes have been pushed to the latest version of the tracking code:

The maximum allowed site speed sample rate (_setSiteSpeedSampleRate) has been increased from 10% to 100%.
The _setAccount method now trims any leading and trailing spaces.

Release 2012-02 (February 1, 2012)

2012-02-01T08:00:00Z

The following changes have been pushed to the latest version of the tracking code:

Updated the list of organic search engines detected by default. Added ‘startsiden.no’, ‘rakuten.co.jp’, ‘biglobe.ne.jp’, and ‘goo.ne.jp’. Removed ‘search’ and added ‘conduit.com’, ‘babylon.com’, ‘search-results.com’, ‘avg.com’, ‘comcast.net’, and ‘incredimail.com’ all of which were previously attributed together as ‘search’.

Release 2012-01 (January 26, 2012)

2012-01-26T08:00:00Z

The following changes have been pushed to the latest version of the tracking code:

The limit on custom variable length has been increased from 64 to 128 characters. Additionally, the length is now checked before URL encoding.
The rate limit for event hits has been relaxed. You can now send 10 hits with 1 additional hit per second (previously this was limited to 1 hit every 5 seconds). Note that the 500 hits per session limit still applies.
__utmv cookies are now written with a different variable separator (caret instead of comma) to be compatible with RFCs. This should fix some of the issues related to cookie encoding issues seen by customers.

Release 2011-11 (November 16, 2011)

2011-11-16T08:00:00Z

Changes to Site Speed data collection:

Site speed data is now automatically collected for all web properties at a 1% sample rate. The _trackPageLoadTime function, previously required to opt-in to site speed data collection, is now deprecated.
The default sample rate may be adjusted using the new _setSiteSpeedSampleRate function.
If a virtual path is used in the _trackPageview call, that path will now also be associated with any site speed data collected from that page.

Release 2011-10 (October 17, 2011)

2011-10-17T08:00:00Z

This release contains the following new feature:

Events can be marked as non-interaction by setting the new opt_noninteraction parameter of the _trackEvent() method to true. Marking an event as non-interaction indicates that hits from the tagged event will not impact bounce rate. For more information, see the ga.js reference.

This release contains the following bug fix:

Fixed an issue where propagating the AdWords gclid URL parameter on internal site links could result in inflated paid visit counts.

Release 2011-08 (August 16, 2011)

2011-08-16T08:00:00Z

This release fixes a bug which caused inflated numbers of visits and/or a decrease in the number of new visitors for some sites. The first effect primarily affected sites with organic traffic coupled with specific user behavior. The second effect was only on sites using an unsupported tracking configuration with multiple trackers.

Release 2011-08 (August 11, 2011)

2011-08-11T08:00:00Z

Changes to session calculations:

One campaign per session: If a new campaign is started during an existing session, the tracking script will now automatically start a new session. A new campaign will be triggered by a change to any of the following fields: campaign id, name, source, medium, term, content, or gclid.
The tracking script no longer starts a new session in the event that a user closes the browser.

Changes to cross-domain tracking:

The call to _setAllowHash(false) is no longer required when configuring cross-domain tracking. Pages that already include a call to _setAllowHash(false) will continue to work, but it is no longer required when setting up a new site.
The tracking script will now attempt to repair linker parameters that have been mangled by HTTP redirectors and browsers. Approximately 85% of linker values that are currently discarded due to encoding changes introduced by redirectors and browsers should now be successfully restored and accepted by the tracking script.

Release 2011-07 (July 26, 2011)

2011-07-26T08:00:00Z

This release contains one new feature:

The tracking code now postpones hits for prerendered pages until those pages are viewed by the user. If a prerendered page is never viewed, no hits are sent. This feature is only available to sites using the async tracking script. You can learn more about prerendering in Google Webmaster Central Blog.

Release 2011-07 (July 14, 2011)

2011-07-14T08:00:00Z

This release contains a variety of bug fixes and refactorings, and one new feature:

Added social tracking support ( _trackSocial )

Release 2011-05 (May 18, 2011)

2011-05-18T08:00:00Z

This release contains the following bug fixes.

Fixed a bug in cross domain tracking that caused incorrect encoding of campaign data in some cases.
Fixed a bug in cross domain tracking that caused cookies to be loaded from the URL more than once, causing incorrect cookies in some cases.
Fixed a bug in Custom Variables that caused some values to be encoded in reports.