Launch implementation best practices for a portal

[fern1]

Hi everybody,

we have a doubt about Launch implementation best practices. The consulting company that implemented it created a launch property for each of our websites (domain and subdomain) and linked them to each site report suite and a global one.

However, we have a new project to centralize them all with the same CMS (now we use multiple ones) for all our sites and create a single portal. Considering this CMS will allow us to develop new landing pages super seamlessly with its own URL, is it better to use a single Launch property for all portal pages (technically each site will have its own dev team and business unit, but for the end user it will have the look and feel of a single portal) and to have a javascript code linking the URLs with the respective report suites or to have a separate launch property for each URL (as we have now)?

Thanks in advance

[Anil_Umachigi · Accepted solution]

@fern1 Ideally you will consolidate it to one launch property, however here are few consideration to keep in mind. 

1. This assumes that there's one team taking care of launch implementation and maintenance, if not you may have to manage that with process and access controls 
2. Naming Convention: This becomes critical for naming rules, data elements and dev environments 
3. Marketing & Other Tags: Check if you have other tags for same vendors (example - different fb business accounts for brands) which may complicate migration to one property. 
4. Data Layer/Source: Ensure the data (datalayer and UI scraped data) used today by various sites will be available in the consolidated CMS

Hope that helps 

Anil