Solved

Sub-domain Property Creation in Adobe Launch

Forum|Forum|3 years ago
December 6, 2022
1 reply
1575 views

Hi All,

Our company has xyz.com as primary domain and meetings.xyz.com as sub-domain.

Xyz.com implementation is quite old and difficult to manage if we start implementing meetings.xyz.com as well from same web property.

Is it good idea to create separate property in launch for sub-domain?

We would also need to do cross domain tracking in future. Will this type of implementation allow me to do cross domain tracking?

Thank you!

Analytics

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

Best answer by leocwlau

Strictly speaking, "meetings.xyz.com" is also under the same "xyz.com" and "meetings" hostname. It is absolutely sensible to have a different launch property for "meetings.xyz.com" if it is a "different" website.

How to count it as "different"? My general principle is that it has a different information architecture and different navigation.

There is no problem tracking across these two websites. Ideally, both use the same report suite then you can easily follow users from one site to another.

leocwlau

Accepted solution

Community Advisor and Adobe Champion

Strictly speaking, "meetings.xyz.com" is also under the same "xyz.com" and "meetings" hostname. It is absolutely sensible to have a different launch property for "meetings.xyz.com" if it is a "different" website.

How to count it as "different"? My general principle is that it has a different information architecture and different navigation.

There is no problem tracking across these two websites. Ideally, both use the same report suite then you can easily follow users from one site to another.

P

priyankapuradkar2Author

Hi,

xyz.com is the hotel booking site and meetings.xyz.com is meeting room booking site.

The architecture is quite different. meeting.xyz.com is whitelabeled solution and managed by third party.

There is no direct navigation to meetings.xyz.com. User has to go through xyz.com then land on meetings.xyz.com.

Jennifer_Dungan

Community Advisor and Adobe Champion

I support what @leocwlau said.. if the architecture is different enough, it warrants using a different Launch Property (so you can control the tags in isolation), but send the data to the same Suite.

I do this on our sites... but it does mean if you need to change, add or remove something from your tracking, you will need to make changes in each Launch property.

At the end of the day, this will really come down to your preferences and how comfortable you feel in maintaining your code bases.

If the main and sub domains are on a similar enough architecture, you may not need to have a separate property... but this isn't something that we can tell you, only you can determine that yourself.

There are pros and cons to each approach, and how the sites are designed coded will play an important factor in your decision.

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded