Note that there are some explanatory texts on larger screens.

plurals
  1. USelaxsj
    primarykey
    data
    text
    plurals
    1. COI can see that GA places a cookie both for blog.domain.com and domain.com, so based on the info in the followup article, one should think it should work. The _blog.domain.com cookie_ should be used for the first account (single-domain tracking), and the _domain.com cookie_ should be used for the second account (cross-domain tracking). But I realise that it does not work, so I guess you are perfecly correct.
      singulars
    2. COSorry I'm picky. Your answer is accepted so you are free to answer or not ;) In [a followup to the "pitfalls" article](http://www.lunametrics.com/blog/2009/03/06/cookies-tracking-multiple-accounts-ga/), the author writes: "(..) each tracker use[s] completely different cookies. At this point you no longer have the problems listed above. You can track some pages to both accounts, and other pages to just one account without any conflict. You can use different User Defined Segments on each. And you can use cross domain tracking for one set of Tracking Code but not the other."
      singulars
    3. COThanks, now I get it. The cross-domain tracking is most important, so then I will use this account as the name-less tracker and `setDomainName` to `.domain.com`, and track the event only this. But can I add a simple extra tracker for the blog, just using `_setAccount` and `_trackPageview` on this? Due to user permission issues, I would like to track page views on the blog on a completely different account, instead of making different profiles on the main account with a Hostname filter.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload