AdWords is now Google Ads. Our new name reflects the full range of advertising options we offer across Search, Display, YouTube, and more. Learn more

Analytics
4.5K members online now
4.5K members online now
Dive into multiple domain (Cross/Sub) tracking, implementing Ecommerce and Enhanced Ecommerce, setting up Event tracking, and Universal Analytics code.
 
Guide Me
star_border
Reply

Are subdomains considered separate properties for tracking purposes?

Visitor ✭ ✭ ✭
# 1
Visitor ✭ ✭ ✭

My team created two properties--one for each subdomain. Each property has its own tracking code. Looking at some of our data, we're wondering if the two subdomains should be regarded as one property. The documentation I've read suggests our original approach was correct. Any thoughts on this?

Are subdomains considered separate properties for tracking purposes?

Participant ✭ ✭ ☆
# 2
Participant ✭ ✭ ☆

If there is no connection between these two subdomains (no links between them) you can use separate properties.
But if users can easily travels from one subdomain to the other you should consider to implement the same tracking code (same property) on both subdomains to eliminate self-referrars or direct source in reports.

Are subdomains considered separate properties for tracking purposes?

Visitor ✭ ✭ ✭
# 3
Visitor ✭ ✭ ✭

Thanks for your reply, Tomasz_C. The two subdomains (we'll call them A & B) do have links between them. The thing is, subdomain A is an https site and B is an http site. This is having an effect on the GA data because https sites do not pass referral information to http sites. And, yes, the traffic from A is appearing as "Direct" in the B Acquisition report. We are interested in tracking referrals from A to B for various reasons. I'm not even sure that cross-subdomain tracking would circumvent the https-to http issue. Is it possible that giving the two subdomains the same tracking code and treating them as one property would provide better tracking information between the subdomains? Or maybe the solution is to make B an https site (an option we're also considering).

Are subdomains considered separate properties for tracking purposes?

Explorer ✭ ✭ ☆
# 4
Explorer ✭ ✭ ☆

You should definitely make B an https site as this will also impact your organic search position positively. From what you are saying, it's one and unique customer experience, but spread over two different sites (or subdomains). This is often the case and you should think in terms of "customer", not in terms of "technical constraints and limitations".

 

If you used the same UA on both sites, the referrer issue wouldn't apply since it would be considered a single session and the source/medium wouldn't be overwritten. The GA cookie is a 1st party cookie assigned to the topmost domain, thus, a single cookie for A.domain.com and B.domain.com.

 

Alternatively, or in the meantime, you could add <meta name="referrer" content="always"/> to your HTTPS site so the referrer is always passed (but keep in mind this would apply to all outbound links, and if ever there is sensitive info on the HTTPS URL it will be passed on too!) Some more info here.