If you advertise on Google, set up your Adwords tracking code. They made changes to their tracking code beginning 2008, which means we have some updating to do. Here's a good blurb on what needs donw.
Enjoy,
Jeff
www.SalesDrivenMarketing.com
Advertise on Google, Yahoo and MSN. All budget sizes welcome.
------------------------
January 4, 2008
Should You Join the Migration? urchin.js Migrates to ga.js
By Caitlin Minteer, Google Analytics Support Tech
In mid-October Google announced the beta release of the new tracking code: ga.js. Then, in December, they released the new code to all Google Analytics users. So you might have noticed, within Google Analytics, that there is now a tab labeled 'New Tracking Code' within the Profile Settings > Tracking Code section.
You may be thinking, "Why should I care?" Well, here are a few reasons why the migration to ga.js is practically inevitable for those of you who want to remain on the cutting edge of the latest and greatest technology. And why, for those of you who don't want to rock the boat, it may not be necessary to switch over... yet.
With the upgrade to ga.js you will have access to several new features including Event Tracking, and Outbound Link Tracking.
Event Tracking will be especially useful for those who have Flash based sites, or for those who use multimedia on their site. An "event" is an action that a user takes on a webpage that doesn't necessarily involve a new pageview. Examples include clicks on buttons or images, navigation in embedded Flash, or Ajax events, like moving a map in Google Maps, or applying a label in Gmail.
Outbound Link Tracking will tell you which links visitors clicked on your site that direct them to another site without the manual tagging. This means that instead of adding urchinTracker to each and every one of your outbound links to see where visitors are going once they leave, you don't have to do anything.
A few other benefits of the updated ga.js include:
Faster, smaller source file - which will allow for a faster download time
Object oriented - instead of using functions
Automatic detection of HTTPS
Increased namespace safety
One question seems to keep surfacing about the migration, so I will go ahead and address that now. The new Google Analytics tracking code (ga.js) will NOT work with the previous tracking code (urchin.js). They are not compatible, so all pages on your site should be updated with the new code.
So the bottom line: Should you switch to ga.js?
Google is still supporting the urchin.js tracking code, and sources predict that that they'll continue support for another 12-18 months, so if you're happy with the current features and you're not worried about any new releases to ga.js (and the potential discontinuation of support down the line), then you're probably OK for another few months, at least. Eventually, though, you're going to need to switch to ga.js.
If you want event tracking and automatic outbound link tracking, as well as any new features that are released in the future, and you're willing to spend a little time and resources on getting everything set up properly, then you might want to consider joining the migration.
If you're looking for help, Google has written a reference guide for switching over to the code in pdf format, and if you need any assistance from ROI Revolution, an Authorized Google Analytics support partner, be sure to take a look at our Google Analytics support plans and we'll get you on the path to a seamless migration.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment