Expand my Community achievements bar.

SOLVED

How to track subdomains using AEP Web SDK?

Avatar

Level 2

Hi everyone,  Can someone suggest what is the best way for tracking 2 subdomains in Adobe Analytics using AEP web SDK? 

I have two domains, www.xyz.com and blog.xyz.com. 

Are the below items considered good practice?

1. I want to use separate launch containers for each domain.(as I have multiple third party marketing pixels for each domain. Maintaining 100s of rules might be difficult)

2. I have a schema created where I have added Experience event, commerce event and Adobe Analytics experience event field group (as I want to send data to both AA and AEP). Is it okay to use the same schema for both www.xyz.com and blog.xyz.com? 

3. If someone is navigating from www.xyz.com to blog.xyz.com, will Adobe differentiate them as two separate visitors? I am assuming it will not, as the cookie will be set on ".xyz.com" domain.

4. Do I need to create two separate data streams? or having one data stream will suffice?

1 Accepted Solution

Avatar

Correct answer by
Employee

1. I would strongly recommend trying to stick with one tags property that spans both subdomains, if you can, and develop good naming conventions for your rules so they are easy to manage. And look for ways to consolidate the rules. For example, if two different marketing pixels fire under the same event and condition, use two actions in a single rule to fire them. IMO, things are harder to manage when broken into multiple properties. For example, you would then be managing two Web SDK extensions.

 

2. Yes, it's fine to use the same schema across multiple subdomains.

 

3. The cookies used by Adobe applications are set on the top level domain ".xyz.com" so you should be  fine to identify visitors across the subdomains.

 

4. Yes, you should be able to use the same datastream from two different tags/launch properties

View solution in original post

2 Replies

Avatar

Correct answer by
Employee

1. I would strongly recommend trying to stick with one tags property that spans both subdomains, if you can, and develop good naming conventions for your rules so they are easy to manage. And look for ways to consolidate the rules. For example, if two different marketing pixels fire under the same event and condition, use two actions in a single rule to fire them. IMO, things are harder to manage when broken into multiple properties. For example, you would then be managing two Web SDK extensions.

 

2. Yes, it's fine to use the same schema across multiple subdomains.

 

3. The cookies used by Adobe applications are set on the top level domain ".xyz.com" so you should be  fine to identify visitors across the subdomains.

 

4. Yes, you should be able to use the same datastream from two different tags/launch properties