Comments on: Google Analytics _setAllowHash bug

By: Eduardo Cereto

Eduardo Cereto — Wed, 02 Nov 2011 12:19:43 +0000

If you were seeing low time on site than it might be the answer, but since it’s the other way around I don;t think it’s related to this specific bug.

By: Mfagergren

Mfagergren — Wed, 14 Sep 2011 17:37:00 +0000

Hey! My company manages an analytics account for a client that is tracking six different domains individually and collectively, so each site has two codes on it (one that tracks all of their traffic combined and then one that tracks the site individually). The last few months we’ve been seen abnormally high “time on site” data. Why is that? have you seen anything like that. I was wondering if changing the use_setAllowHash(false) to (true) could be the answer. What do you think? Any info would be great!!!

By: Tracciamento dei sottodomini: best practices • Google Analytics in 30 secondi

Tracciamento dei sottodomini: best practices • Google Analytics in 30 secondi — Thu, 27 Jan 2011 22:37:07 +0000

[...] Eduardo Cereto ha un post che approfondisce questo problema con più dettagli e fornisce un altro caso in cui _setAllowHash genera problemi. La morale qui è che avete bisogno di _setAllowHash per il tracciamento cross-domain, ma se invece avete solo a che fare con sottodomini non è necessario e anzi potrebbe causarvi problemi. [...]

By: Google Analytics Subdomain Tracking | jondyer.net

Google Analytics Subdomain Tracking | jondyer.net — Fri, 14 Jan 2011 06:17:47 +0000

[...] Cereto has a post that looks into this issue in more detail and provides another use case where _setAllowHash causes [...]