I agree, an API would be fantastic. But I think that Google faces a number of challenges when it comes to a data API. First there are obvious privacy and security issues that they must address. Second, I think there could be some technical issues. Analytics stores a lot of data and an API could put a tremendous load on the system (even for Google).

I eventually think that there will be an API and Google will put their own unique spin on it.

Thanks for the feedback,

Justin

But WHY? I’ve been dying for this. Have been tempted for so long to use the CURL method of extracting data – but don’t want to go through the word because I just know a week later they’ll announce their own legit API. Ho hum.

I don’t think that Google will change the link tagging parameters. There are too many people that have already tagged their lings using the utm_ parameters. With that said, we are talking about Google, and I wouldn’t put anything past them!

Gary,

I assume you’re talking about event tracking and why we should use it rather than creating pageviews with urchinTracker… The old method is a bit of a hack. Page level interactions are very different than page views, and should be collected and reported differently. Hence the creation of event tracking.

Thanks for the comments,

Justin

Late comment here, but I was curious to know if custom URL Coding will also undergo a change at some point, or does Google Analytics plan on keeping the “utm” naming convention for the campaign tracking dimensions in URLs.

Thanks for your comments!!

Unfortunately there is no ETA for the event reporting. You know Google and how they love their privacy.

Thanks for the comment,

Justin

Justin

“a snazzy movie of Avinash” ?
OR
“a movie of a snazzy Avinash” ?

Hang on a sec… what’s that bright red glow to the East? Ahh. Of course. Avinash is blushing. ;-)

Cheers!
- Evil Steve