3 ms·

Let's debate whether it is expected behavior or not. I propose that there is no other way for Analytics to handle subdomains than what you describe, because th

by mmelin 17y ago

Let's debate whether it is expected behavior or not. I propose that there is no other way for Analytics to handle subdomains than what you describe, because there is no way for Analytics to be certain that domain.com and sub.domain.com belong to the same site. Of course, an option to inform Analytics of this fact would be nice, but out of the box I really don't see how it could work differently.

patio11 17y ago
As far as I know the code to do exactly this is: pageTracker._setDomainName(".example.com"); Warning, warning: when you start playing with Google Analytics you will quickly learn that it is Enterprise software: built to be infinitely customizable using massive amounts of work to just short of your actual needs but no farther, and filled full of sharp edges to cut yourself on. That said, it is a very impressive piece of software in a lot of ways. (My internal analytics are a lot more useful to me, but my heart aches for how easy it is to dig into arbitrary things in GA.)
- jacquesm 17y ago
  Yes, that's it exactly. https://www.google.com/support/googleanalytics/bin/answer.py?answer=55524&cbid=1beih2v4piof5&src=cb&lev=answer https://www.google.com/support/googleanalytics/bin/answer.py... That's the relevant page in the support area. My mistake, I should have realized their default is set to treat subdomains as different sites because that is probably a more common use case.
  - leviathant 17y ago
    Keep in mind that if you have existing tracking goals set up and you implement URI filtering like this, your goals will need to be rewritten to accommodate the domain being appended to the beginning of each URI. This will also break the site overlay/clickmap, if that's something you use.
    - arantius 17y ago
      > .. appended to the beginning .. Or, of course, prepended.

3 ms·

Let's debate whether it is expected behavior or not. I propose that there is no other way for Analytics to handle subdomains than what you describe, because th

by mmelin 17y ago

patio11 17y ago
As far as I know the code to do exactly this is: pageTracker._setDomainName(".example.com"); Warning, warning: when you start playing with Google Analytics you will quickly learn that it is Enterprise software: built to be infinitely customizable using massive amounts of work to just short of your actual needs but no farther, and filled full of sharp edges to cut yourself on. That said, it is a very impressive piece of software in a lot of ways. (My internal analytics are a lot more useful to me, but my heart aches for how easy it is to dig into arbitrary things in GA.)
- jacquesm 17y ago
  Yes, that's it exactly. https://www.google.com/support/googleanalytics/bin/answer.py?answer=55524&cbid=1beih2v4piof5&src=cb&lev=answer https://www.google.com/support/googleanalytics/bin/answer.py... That's the relevant page in the support area. My mistake, I should have realized their default is set to treat subdomains as different sites because that is probably a more common use case.
  - leviathant 17y ago
    Keep in mind that if you have existing tracking goals set up and you implement URI filtering like this, your goals will need to be rewritten to accommodate the domain being appended to the beginning of each URI. This will also break the site overlay/clickmap, if that's something you use.
    - arantius 17y ago
      > .. appended to the beginning .. Or, of course, prepended.