Last November (2017), we released Launch to Production and started giving access to customers who requested it through a random selection process. At the same time, we started giving new Experience Cloud customers access to Launch instead of DTM.


Earlier this year at the US Summit (March 2018), we ended the random selection process and made Launch available to all Experience Cloud customers. Since that time, we've had close to 1,000 different customers log in and create properties in Launch. Half of them have published to their Production environment - and are using it live, we assume =)


This summer (July 2018), we released an upgrade process in DTM to provide a self-service, automated way to move your DTM properties into Launch. You can read more about this in the blog post and in the product docs.


We continue to add new features to Launch. In the coming months, you’ll see things that were never possible in DTM like private extensions and mobile properties for managing SDKs in your native mobile applications. You’ll also see better versions of things that DTM already has like comparing revisions and bulk copy.


Maintaining both DTM and Launch in perpetuity was never the plan and is not a sustainable path forward. Looking ahead, DTM will be in maintenance mode. We’ll keep it up-to-date with security fixes, critical bug fixes, and Experience Cloud changes.  We will not be doing any feature development.


Over the next few years, we will be introducing progressive restrictions on what you can do within DTM. We want to be transparent with those plans so that you can plan your upgrade path accordingly.




Starting in July of next year, DTM will no longer allow the creation of new properties. This will have no impact on existing properties.



One year after that, DTM properties will enter a Read-only mode. You will not be able to create or edit tools, rules, or data elements. You will no longer be able to publish to DTM environments. This will have no impact on previously published libraries.



DTM will go dark. Servers will be decommissioned, documentation will go offline, and communities will be removed. This will have no impact on previously published libraries.


We hope that by letting you know about these things in advance, you'll be able to make and execute your plans to upgrade to Launch without interruption to your business. You'll be joining your Experience Cloud peers who are taking advantage of Launch's open ecosystem, asynchronous deployments, new rule builder, and the APIs.


Happy Tagging =)


This post first appeared on the Launch blog.  You can follow us there.