Cross-Domain and Subdomain Tracking

Question 1

If you are tracking more than one domain or subdomain within the same property and want to record data for each domain/subdomain separately as well as aggregated data, how should you set up your views?

Answer 1

Set up three views with an Include filter on two

Question 2

Relative to www.mysite.com, which of the following represents a subdomain of the same domain?

Answer 2

sub.alphaward.com

Question 3

What is a side effect of cross-domain and subdomain tracking?

Answer 3

By default, the Behavior reports do not differentiate between visits to identically named pages within the various domains and subdomains

By default, the Behavior reports consolidate metrics for identical request URIs that exist on more than one domain or subdomain. For example, pageviews for www.domain.com/welcome.php and sub.domain.com/welcome.php would be consolidated under /welcome.php as a single request URI.
To distinguish between identical request URIs on more than one domain or subdomain, you can use an Advanced view filter to prepend the hostname (that is, the domain name) to the request URI.

Question 4

If you’re capturing cross-domain or subdomain data within one view, which kind of view filter can you apply to differentiate between identically named pages that exist on the multiple domains or subdomains?

Answer 4

Advanced

If you track across several domains or subdomains within one view, your reports will not by default distinguish between visits to identically named pages. To differentiate the pages, you can use an Advanced view filter to prepend the hostname (for example, sub.mysite.com) to the request URI.