Launch is the next generation of website tag and mobile SDK management capabilities from Adobe. Launch gives customers a simple way to deploy and manage all of the analytics, marketing, and advertising integrations necessary to power relevant customer experiences.
Launch empowers anyone to build and maintain their own integrations with Launch, called Extensions. These extensions are available to web and mobile Launch customers in an app-store experience, so customers can quickly install, configure, and deploy their integrations.
Here are the benefits for using Adobe Launch:
- Faster time to value with the ability to dynamically deploy changes to your website or mobile app
- Trustworthy data through centralized collection, organization, and delivery using data elements
- Compelling experiences through the integration of data and marketing technology using rule builder
Here are the key features that are available in Launch:
-
Web
An extension is a package of code (JavaScript, HTML, and CSS) that extends the Launch UI and client functionality. You can build, manage, and update your integrations using a virtually self-service interface. You can think of Launch as an operating system, and extensions are the apps you use to achieve your tasks.
-
Mobile
Mobile extensions are comprised of a Launch UI configuration screen and native SDK components that work with the core Adobe Experience Platform SDKs to deliver functionality to mobile apps.
Important: In Android and iOS extensions, only contents on secure http connections (https
) are served. When a URL that contains http://
is passed in, the connections are blocked.
Browse, configure, and deploy marketing/advertising tools built and maintained by independent software vendors.
Create robust rules that combine multiple events, sequenced in the way that you determine using if/then logic with conditions and exceptions. Extensions provide options for:
- Events
- Conditions
- Exceptions
- Actions
Collect, organize, and deliver data across web-based marketing and advertising technology.
The publishing process enables teams to dynamically publish updates to both web pages and application. Different people can create an implementation, approve it, and publish.
Here are some benefits to this publishing process:
- Changes to your implementation are encapsulated within libraries you define
- You specify where and when you want your changes deployed
- Multiple libraries can be built in parallel by different teams
- Unlimited development environments
- Deliberate, permissioned process for merging libraries together
Automate implementations of individual technologies, or a group of technologies.
- Launch interacts with the Reactor APIs
- Deployments can be automated through APIs
- Integrate the Launch APIs with your own internal systems
- You can build your own user interface, if desired
Launch requires the following:
- You must be an Adobe Experience Cloud customer.
- You must deploy the Launch or DTM embed code on your web pages.
- For mobile, you must integrate the Adobe Experience Platform Mobile SDKs into your application.
The Launch container tag is 60% lighter than DTM and 40% lighter than Google Tag Manager. The content of your container is minified, including your custom code. Everything is modular. If you don't need an item, it is not included in your library. The result is an implementation that is fast and compact. See Minification.
Launch provides several improvements over similar systems, including:
- No use of
document.write ()
where Chrome doesn't allow it - The Page Top and Page Bottom rules are bundled into the main library to minimize unnecessary HTTP calls
- Custom action scripts within a rule can be loaded in parallel, but are executed sequentially
- If you avoid Page Top and Page Bottom rules, the code is mostly asynchronous, with a path to getting fully async
Launch is the next-generation of the Adobe tag-management capability, built into the Adobe Experience Cloud. Launch enables clients to:
- Deploy client-side web products using integrations called extensions
- Consistently capture, define, manage, and share data between marketing and advertising products from other vendors and from Adobe
Launch is an advanced JavaScript delivery system that evaluates conditions and executed actions to efficiently and effectively deploy client-side libraries and products. It provides a highly scalable approach to managing and building extensions, together with a robust set of APIs for programmatic interaction with the Adobe Experience Cloud.
No. Launch is an entirely new product with a new code base. The system has been redesigned from scratch using modern front-end development practices and an API-first approach. Everything is built on a robust set of APIs, which makes the system very powerful and highly flexible.
Yes, legacy DTM (the existing production version) will continue to be supported for the foreseeable future. Adobe will continue to fix any significant bugs and ensure consistent performance. At this time, no major feature enhancements are planned for legacy DTM.
Many customers see Launch implementations as an opportunity to start from scratch and cleanup many issues they have with current implementations. If this does not describe you, you can copy an existing DTM property into Launch and save yourself a bunch of effort. See the Upgrade FAQ for more inormation.
There is no additional charge for Launch. It is available for any Adobe Experience Cloud customer.
No, you won't have to change your production embed codes if you're currently using the existing (legacy) DTM system. You can continue to work in your current DTM Company and Web Properties without worrying about changing that embed code.
If you'd like, you can link your DTM Production embed code with your Launch Production embed code so you don't have to change your page tags. See Link DTM Embed Code for more information.
We call them Extensions. Launch is built into the Adobe Experience Cloud and it is fully extensible. Customers, Adobe Partners, agencies, and marketing or advertising technology vendors will soon be able to build Launch extensions that add new functionality or modify existing functionality. The system allows partners and clients to build, manage, and update their own integrations. This is just one way Adobe is opening up the Adobe Experience Cloud so customers and partners can build products and businesses on the Platform, and so everyone can more easily connect Adobe technology to the marketing and advertising technologies from other vendors.
Extensions are available for all Adobe solutions and for a growing number of independent vendors. New extensions are always under development and more are added to the catalog every week.
Each extension developer maintains their own roadmap and schedule for their extensions, the Launch team does not have control or influence.
Anyone can build an extension now. To get started, go to developer docs. Currently all extensions are open to all Launch users, but later this year we will add the ability to build an extension that can only be seen by your company and a whitelist of others that you specify.
Launch is SOC-2 and Gramm-Leach-Bliley Act ready. Launch also offers the capability of being self-hosted. The JavaScript libraries can be served from your own servers, or the CDN of your choice. For IT and security teams, this gives you the ability to run automated testing, to check the files into your own version control system, and to fully comply with any internal production migration processes, security-related or otherwise.
Launch. Any new deployments done with DTM will need to be migrated eventually as DTM reaches it's sunset phase.
Yes. Launch has capabilities to give users and extension developers flexibility in collecting, managing, and distributing data within single page application experiences or Ajax-heavy pages or sites. This applies regardless of your development framework preferences, whether that's Angular, React.js, Ember, Meteor, etc.
Read more about the benefits of using Launch for your SPAs on the Launch blog.
Yes. Launch includes an extension that specializes in listening for changes in dynamic data layers.
Event types are available through extensions. The Launch Core extension includes 30 built-in event types. Other extensions add additional event types. For example, the YouTube extension includes four video event types: play, pause, end, and time played. Through extensions, Launch can support any other browser event types or synthetic event types, such as specific visitor activity sequences.
Performance is very important to us. Launch is designed to deliver and run marketing and advertising technologies on your web site as efficiently as possible using today's best practices. Adobe technologies deployed together through Launch are faster than any other deployment method. You can read more about performance and our perspective in the Performance Whitepaper.
Browser support in the Launch client-side libraries:
- Chrome (latest)
- Safari (latest)
- Firefox (latest)
- Internet Explorer (10 and above)
- iOS Safari (latest)
- Android Chrome (latest)
Browser support in the Launch application interface:
- Chrome (latest)
- Safari (latest)
- Firefox (latest)
- Internet Explorer (11 and above)
Legacy DTM supported older versions of Internet Explorer, but over the last few years, the percentage of overall web users with older, outdated browsers has dropped to a small segment for our clients. Most Adobe clients now leverage more modern web platform features in current browsers and create better user experiences, including single page applications and interactive Ajax-heavy web sites and pages. As most clients move to more modern approaches with their sites, they demand a solution like Launch that enables those approaches.
These are the questions we've received most often from customers and partners since the Launch announcement. If you have other questions, please ask in the Adobe Community on the main Launch page located at https://adobe.com/go/launchme.
Launch is just one example of where our platform is headed: more open, more integrated and as always dedicated to customer success.