Google Analytics cookies vs subdomain for static content

Question

I have a website on www.example.com and use Google Analytics. I\'ve also set up static.example.com which serves all static content.

The problem is that the default b

Answer 1

Google Analytics stores all session data in cookies that helps it to ‘remember’ previous page views. The function call pageTracker._setDomainName(".example.com") tells every sites to store cookies for host example.com (instead of their own subdomain) to ensure the ability to reach each other's data.

The form pageTracker._setDomainName("none") is needed in and only in that case when your site spans across multiple, different domain names.

Set this method to none in the following two situations:

* You want to disable tracking across sub-domains.
* You want to set up tracking across two separate domain names.

Cross-domain tracking requires configuration of the _setAllowLinker() and _link methods.

To answer your question, Google Analytics uses first-party based cookies for collecting data. When you want your static content's traffic to appear in GA, you have to allow cookies for them, too. To avoid this issue, you may choose a server solution like Urchin that parses server log files instead of dealing with cookies.

Answer 2

The solution is to do pageTracker._setDomainName("www.example.com") and then GA will issue the cookies to ".www.example.com". That way analytics still works fine and the cookies do not leak into the other static subdomain.

Answer 3

For anyone loading the Google Analytics javascript async (the recommended way according to Google) the syntax looks like this:

_gaq.push(['_setDomainName', 'www.allinpoker.se']);

This line should be before _trackPageview since it's configuring the cookies. You could find more info on developers.google.com.

I also recommend setting up a permanent redirect on (in my case) allinpoker.se to www.allinpoker.se since you only want the tracking on the www sub domain.