tag:blogger.com,1999:blog-3580069.post3321707769768336080..comments2024-02-27T07:06:31.494-05:00Comments on Google Analytics Solutions: Web Analytics TV #18Nickhttp://www.blogger.com/profile/07298613952446925742noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-3580069.post-8202808692893678712011-05-09T03:41:47.997-04:002011-05-09T03:41:47.997-04:00Thank You.
Zamre Bin Ab. WahabThank You.<br />Zamre Bin Ab. Wahabzamrehttps://www.blogger.com/profile/02221700521471574634noreply@blogger.comtag:blogger.com,1999:blog-3580069.post-30996058332522814822011-05-04T09:41:12.282-04:002011-05-04T09:41:12.282-04:00(y) nice n thankyou(y) nice n thankyouJonrohttps://www.blogger.com/profile/08780741430692368998noreply@blogger.comtag:blogger.com,1999:blog-3580069.post-86218885397642981702011-05-03T19:53:46.830-04:002011-05-03T19:53:46.830-04:00Nick, Avinash - apologies if this isn't the pr...Nick, Avinash - apologies if this isn't the proper venue for this question. We've been using setDomainName, etc., to track subdomains on our sites (icanhascheezburger.com, others) for months without issue. Yesterday, visits and visitors began to spike, bounce rates and time on site got worse, etc., indicating possible cookie corruption. <br /><br />Assuming we changed nothing on our side, my question is - did Google release something yesterday that change the way Analytics handles domain and hash information, and that might have caused this?Lorenhttps://www.blogger.com/profile/04398503643874305074noreply@blogger.com