hmm. I am not so sure you are right. I (.. and remember I work for Y! not G) still believe that the UTM.GIF is still called and that the old syntax such as the below is still valid

http://www.google-analytics.com/__utm.gif?
utmwv=4.1&
utmn=&
utmhn=http://www.mydomain.com>&
utmcn=1&
utmdt= &
utmhid=&
utmr=&
utmp=&
utmac=UA-XXXXXX-1&
utmcc=__utma%3D<__utma cookie>%3B%2B__utmz%3D<__umtz cookie>%3B

..or did I completely misunderstand you :-)
Cheers and thank you very much for commenting. Please let me know if I am not right here. (because it is actually simple to check)
Dennis

Regards,

-Eric

I would love to hear how your collected data compares to your FeedBurner data.. since I only have 14 days worth of data and it seems like you might have a year.. :-)

cheers

>>I guess this will work fine with IP+Useragent tracking. I wonder if this hack will work with cookie-based tracking… for example, Google Analytics.

I am assuming that most of us have moved on forward and are using some sort of page-tagging (or cookie-based tracking as you quite correctly call it) – This including Google Analytics. Most of these Web Analytics solutions; whether that is IndexTools, Omniture, Webtrends or even Google Analytics (as far as I remember) – have a HTTP user-agent IMG request method in place (partly as a “fall-back” methodology as well). AND it is this IMG that can be used in this “HACK” :-)

For Google Analytics, the tracking pixel is called “__UTM.gif” – thus a call in this direction: “http://www.google-analytics.com/__utm.gif?…”

Please correct me if this is outdated. However; I am quite sure it is correct. Please post the syntax when you created it.

Cheers
Dennis

-Eric