Return to Answer

(Without knowing the purpose behind having two accounts in your tracking code...)

Am I missing a dot somewhere?

In the past, it was suggested by Google to use a dot before the domain when including subdomains (i.e., .domain.org), however this is no longer advised as can be seen here (under Traditional (ga.js) syntax), since the dot causes cookie resets, as covered here (under number 2).

GA is not showing pageviews of the pages of the subdomain. Instead, GA lumps all the pageviews in the subdomain.

This is because Google categorizes subdomains as internal links to the root domain, as covered here, and by default does not show the domain or subdomain in reports.

To solve this using one profile, create a filter as covered here:

1. Under Admin -> View (Profile) -> View Settings, click Filters.

2. Click + New Filter and provide the Filter Name.
   

3. Under Filter Type chose Custom and select Advanced.
   
   

4. Under Advanced:
   
   a. FieldA should be set to Hostname
   b. FieldB should be set to Request URI

5. Set the values for both Field A and Field B to (.*), which is an expression that captures all characters.

6. Set the Output To --> Constructor option to Request URI and provide $A1$B1 as the value for that choice.

Alternatively, you can add another profile to Google Analytics for the subdomain, and create a filter to show only traffic for the subdomain:

Admin -> View -> Filters -> New Filter

GA is not showing pageviews of the pages of the subdomain. Instead, GA lumps all the pageviews in the subdomain.

This is because Google categorizes subdomains as internal links to the root domain, as covered here, and by default does not show the domain or subdomain in reports.

To solve this using one profile, create a filter as covered here:

1. Under Admin -> View (Profile) -> View Settings, click Filters.

2. Click + New Filter and provide the Filter Name.
   

3. Under Filter Type chose Custom and select Advanced.
   
   

4. Under Advanced:
   
   a. FieldA should be set to Hostname
   b. FieldB should be set to Request URI

5. Set the values for both Field A and Field B to (.*), which is an expression that captures all characters.

6. Set the Output To --> Constructor option to Request URI and provide $A1$B1 as the value for that choice.

Alternatively, you can add another profile to Google Analytics for the subdomain, and create a filter to show only traffic for the subdomain:

Admin -> View -> Filters -> New Filter

Am I missing a dot somewhere?

In the past, it was suggested by Google to use a dot before the domain when including subdomains (i.e., .domain.org), however this is no longer advised as can be seen here (under Traditional (ga.js) syntax), since the dot causes cookie resets, as covered here (under number 2).

(Without knowing the purpose behind having two accounts in your tracking code...)

Am I missing a dot somewhere?

In the past, it was suggested by Google to use a dot before the domain when including subdomains (i.e., .domain.org), however this is no longer advised as can be seen here (under Traditional (ga.js) syntax), since the dot causes cookie resets, as covered here (under number 2).

GA is not showing pageviews of the pages of the subdomain. Instead, GA lumps all the pageviews in the subdomain.

This is because Google categorizes subdomains as internal links to the root domain, as covered here, and by default does not show the domain or subdomain in reports.

To solve this using one profile, create a filter as covered here:

1. In the View (Profile) Settings page, click the Add Filter link.

2. Choose Add New Filter and provide the filter a name.
   

3. Choose Custom filter and select Advanced on the Filter Type settings.
   
   

4. Under Advanced settings:
   
   a. FieldA should be set to Hostname
   b. FieldB should be set to Request URI

5. Set the values for both Field A and Field B to (.*), which is an expression that captures all characters.

6. Set the Output To --> Constructor option to Request URI and provide $A1$B1 as the value for that choice.

Alternatively, you can add another profile to Google Analytics for the subdomain, and create a filter to show only traffic for the subdomain:

Admin -> View -> Filters -> New Filter

(Without knowing the purpose behind having two accounts in your tracking code...)

Am I missing a dot somewhere?

In the past, it was suggested by Google to use a dot before the domain when including subdomains (i.e., .domain.org), however this is no longer advised as can be seen here (under Traditional (ga.js) syntax), since the dot causes cookie resets, as covered here (under number 2).

GA is not showing pageviews of the pages of the subdomain. Instead, GA lumps all the pageviews in the subdomain.

This is because Google categorizes subdomains as internal links to the root domain, as covered here, and by default does not show the domain or subdomain in reports.

To solve this using one profile, create a filter as covered here:

1. Under Admin -> View (Profile) -> View Settings, click Filters.

2. Click + New Filter and provide the Filter Name.
   

3. Under Filter Type chose Custom and select Advanced.
   
   

4. Under Advanced:
   
   a. FieldA should be set to Hostname
   b. FieldB should be set to Request URI

5. Set the values for both Field A and Field B to (.*), which is an expression that captures all characters.

6. Set the Output To --> Constructor option to Request URI and provide $A1$B1 as the value for that choice.

Alternatively, you can add another profile to Google Analytics for the subdomain, and create a filter to show only traffic for the subdomain:

Admin -> View -> Filters -> New Filter

(Without knowing the purpose behind having two accounts in your tracking code...)

Am I missing a dot somewhere?

In the past, it was suggested by Google to use a dot before the domain when including subdomains (i.e., .domain.org), however this is no longer advised as can be seen here (under Traditional (ga.js) syntax), since the dot causes cookie resets, as covered here (under number 2).

GA is not showing pageviews of the pages of the subdomain. Instead, GA lumps all the pageviews in the subdomain.

This is because Google categorizes subdomains as internal links to the root domain, as covered here, and by default does not show the domain or subdomain in reports.

To solve this using one profile, create a filter as covered here:

1. In the View (Profile) Settings page, click the Add Filter link.

2. Choose Add New Filter and provide the filter a name.
   

3. Choose Custom filter and select Advanced on the Filter Type settings.
   
   

4. Under Advanced settings:
   
   a. FieldA should be set to Hostname
   b. FieldB should be set to Request URI

5. Set the values for both Field A and Field B to (.*), which is an expression that captures all characters.

6. Set the Output To --> Constructor option to Request URI and provide $A1$B1 as the value for that choice.

Alternatively, you can add another profile to Google Analytics for the subdomain, and create a filter to show only traffic for the subdomain:

Admin -> Profiles -> Filters -> New Filter

(Without knowing the purpose behind having two accounts in your tracking code...)

Am I missing a dot somewhere?

In the past, it was suggested by Google to use a dot before the domain when including subdomains (i.e., .domain.org), however this is no longer advised as can be seen here (under Traditional (ga.js) syntax), since the dot causes cookie resets, as covered here (under number 2).

GA is not showing pageviews of the pages of the subdomain. Instead, GA lumps all the pageviews in the subdomain.

This is because Google categorizes subdomains as internal links to the root domain, as covered here, and by default does not show the domain or subdomain in reports.

To solve this using one profile, create a filter as covered here:

1. In the View (Profile) Settings page, click the Add Filter link.

2. Choose Add New Filter and provide the filter a name.
   

3. Choose Custom filter and select Advanced on the Filter Type settings.
   
   

4. Under Advanced settings:
   
   a. FieldA should be set to Hostname
   b. FieldB should be set to Request URI

5. Set the values for both Field A and Field B to (.*), which is an expression that captures all characters.

6. Set the Output To --> Constructor option to Request URI and provide $A1$B1 as the value for that choice.

Alternatively, you can add another profile to Google Analytics for the subdomain, and create a filter to show only traffic for the subdomain:

Admin -> View -> Filters -> New Filter