Google Analytics Tracking Code Queries

[Unity]

Hello,

I have taken on a new client who has Google Analytics installed. The tracking code is set to 'single domain'. Recently they added a mobile site using a sub-domain (m.website.com) which means that Google Analytics is not picking up this traffic.

I want to revise the account so that I have a master account (raw data) and then profiles for the mobile site, main domain (www.website.com) and one other for a  sub-domain that they are using. I am aware that there is mobile specific tracking code however I thought it would be easier (re conversions/goals/eCommerce tracking) to not use this and by changing the account to 'multiple domains' we could also get data for another sub-domain that they are using .

My questions are:

1. Am I right to want to use individual profiles over web properties. If not please explain why.
2. When installing the tracking code (where the profile number is changing) I believe that I need to add that code with the changing profile number to the sub-domain sections. So my question is a) is that correct, and b) if I use a profile number on a sub-domain section will the master account still gather the data for the main URL as well as all sub-domains.
3. If I change the master account from using 'single domain' tracking code to 'multiple domain' tracking code will this affect historical data? Will I lose the data?
4. When changing from 'single domain' tracking to 'multiple domain' tracking does this affect eCommerce tracking? Or do we only need to be adding the additional lines of tracking code that allow sub-domains to be tracked?
5. The web developers are using asynchronous code however half is in the and the other half is at the bottom of the source code. Given that traffic is being reported in the Google Analytics account should I have any concerns that the code is split?

I have done a lot of reading but seem to be going around in circles, so your help is much appreciated!

Thanks,
Dinny

[Unity]

Very helpful, thanks Mike!

[mikecp]

1. Yes. Use individual profiles. Not web properties.

2. I would suggest using just one profile #. As you said you want to have a raw data, the main site, and the mobile profile. It's easy enough to use the same UA number for all three, then filter into 3 separate profiles.

3. No. In fact, you're actually not making any changes on Google's end by making that switch in the admin. That's really just a tool that generates a different code for you. It's all front-end. As long as you implement properly, you shouldn't lose any data to your main profile. Any new profiles that you create will, of course, start from scratch.

4. Yes and no. I'll explain below.

5. This isn't ideal, but isn't overly concerning. First of all, there is ZERO benefit to splitting the code. The async code does not block other code from loading, meaning it will have no effect on page load speed. By moving the whole code up into the head, you're just ensuring that the best, most honest data is being captured. Still, splitting the code is a common practice that yields fine results.

So, as I mentioned in answer three, I think you first have to understand that it's not a 'switch' in GA's admin that makes the change from single to multiple-domain. The only thing that actually changes in the admin is the way the snippet is written. And I'll tell you that the only thing that will change is that the _setDomain line will be added. So if you properly add this new line into your GA code, you'll be set up to capture all data into your raw profile. From there you can create your two separate profiles using the same UA code, with a custom filter based on the hostname.

Mike