1. If you want to create a toally separate profile, that will never have the data, then no, you don’t need to the _setDomainName line of code. Just remember that when you do roll into production, and you want to have all the sub domains rolled up, then you will need to add that extra line of code.

2. Yes, creating an exclude filter would follow the same process as an include filter.

Thanks for the questions and thanks for reading the blog.

Justin

A couple of follow up questions.

1. what if I don’t want a master profile that rolls up all the subdomains? for example – I want to create another profile that is used only for testing purposes in a QA / Dev environment. In this case, do I not add the additional line of code – pageTracker._setDomainName(“sitedomain.com”) ?

2. On the production profile, can I use the same method used for creating a subdomain profile to exclude the subdomain from the production profile? So instead of include, I create a filter that says exclude – hostename – subdomain\.mydomain.\com?

thanks

Great question. You should add the sub domain to the website URL setting. This way the site overlay report will work for your sub domain profiles.

Thanks for the question,

Justin

I’ve seen conflicting documentation. Some has it, some does not. I say go with the GA docs.

Justin

If you don’t add the tracking code then you won’t track the WordPress section with GA. If you don’t want any insight into what happens on the WordPress section then leave the GA code off ;)

Justin

I set up my analytics profiles based on your tutorial although I have one question regarding the sub-domain profile.

Should the website URL under settings match the sub-domain (ie subdomain.site.com) or should it remain the same as the main profile (www.site.com)?

Thanks