I am auditing GA implementation for a startup and found they have a separate property for each of its subdomains. And yes, it is possible to navigate from subdomain to root domain and vice versa.

Each subdomain has a specific function as a blog or guide: (blog.example.com) and tools (tools.example.com) various tools user can use.

This is also true for Google Search Console as well.

Now the question is: is above setup correct? Since each property will have its own TrackingId how will this affect reporting?

Or should I just remove all subdomain property?

PS: I am using Google Universal Analytics and managing all of that with GTM.


There is no correct or wrong. It depends on how you want gather data, how many data is gathered, who has an access to which property and so on. Usually one makes a master property for the whole domain with all subdomains and one property à subdomain. This setup is easy to manage and it has clearly divided data. It looks like:

It means:

The same in the Search Console: one property for the whole domain, like *.example.com, and one property for every subdomain.

  • Thanks for the feedback Usually one makes a master property for the whole domain with all subdomains can you please elaborate? – HVenom May 16 '19 at 12:30
  • i've updated my answer – Evgeniy May 16 '19 at 12:51
  • Can you reflect How will tracking across subdomain(directom.com/google-analytics-subdomain-tracking) impact above or is it the alternative to the strategy you suggested? – HVenom May 17 '19 at 5:45
  • You can compare: make firstly correct setup of cross-domain-tracking at the first master property of the main domain (example.com). Than create second master property and implement it into main and subdomains, as i outlined above. So you get to know, what is the difference between two measure ways. – Evgeniy May 17 '19 at 14:07

I personally go with the one property for all sites (domain, subdomain, alternate domain) and then use views to provide different ways of looking at them. e.g. all sites, each individual sites, a sub folder etc.

Doing this can be confusing as the default reporting does not include the domain (hostname) of pages. So reports covering multiple sites get a bit mixed up. You can add it a secondary dimension but that means constantly customising reports. Many people use a filter to make the path report the full URL for views that cover multiple sites.


I recently worked with a client who set up their GA they way you describe - although theirs was less deliberate and more messy.

I ended up adding a property which would record data from the entire site (what Evgeniy suggests above). It didn't replace their setup, it just extended it. So in the simplest terms, every sub-domain and domain of theirs reported back to their respective properties, but also back to one single property (needed to set up cross domain tracking). I did this mostly with GTM.

why did i do this?

I wanted to see traffic as it moved across the entire site. People were supposed to go visit the toolkit, the blog, their dashboard, etc, and I wanted to be able to manipulate, view, segment, and track behavior of all this data together. Frankly, I wasn't sure how I would do this with their setup.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.