Launch has gone mobile!!
Used by thousands of customers for web tag management, Adobe Launch can now be used to manage your mobile SDKs.
Creating a mobile property in Launch allows you to:
-
Create data elements and build sophisticated rules that can combine actions across multiple solutions.
-
Manage mobile extensions:
- Mobile Core and Profile extensions are pre-installed with every mobile property.
- Extensions are available for other Adobe solutions including Adobe Analytics, Adobe Target and Adobe Audience Manager.
-
Mobile Core extension and all additional extensions can be downloaded and installed through a dependency managers such as Maven and CocoaPods.
-
When you add an extension, you must recompile your app and complete the app store submission/approval process.
Data elements, rules, and extension configs are delivered to your application dynamically, are updated at app launch, and do not require app store updates.
For more information about getting started with mobile properties, see Mobile.
When you save a library, Launch will now check all the resources in it and prompt you to add any required extensions that are missing.
- Rights in the Admin Console have been slightly rearranged. Manage Properties now belongs to the Company Rights group. All other permissions (Manage Environments, Manage Extensions, Develop, Approve, and Publish) are in the Property Rights group.
- Database improvements to improve API response times.
There were some edge cases where the rule builder would not display rule components in the same order that the database was saving them in. Now rule builder always displays rule component order correctly.
Newly created Launch properties now come with a "Managed by Adobe" adapter and three environments (one of each type) by default.
The extension catalog is now sorted by display name rather than name.
- When switching properties, the cache was not clearing correctly and incorrect warnings displayed to users about which extensions were installed
- Rules with modified actions now correctly show as changes when adding to a library in all cases
Launch users will now be notified when new versions of extensions are available and can install them on their own. Read more here.
Embed codes have moved from the Environment detail page to an installation instructions modal. This modal is displayed automatically after you create a new environment and is accessible from the Environments List view.
- In some scenarios, rules saved through the UI were not being saved with the correct order. This has now been fixed. In a future update, a data migration will fix all affected rules, but in the meantime manually editing the rule, making a change, and saving will fix an impacted rule.
- Anchor Delay has been moved from Property Settings to configuration for the Core extension Click event
- Tracking Cookie Name has been moved from Property Settings to the Adobe Analytics, Google Universal Analytics, and Cookie Optin condition settings
Target Extension has been updated to use at.js v1.3.1. When you deploy Target with Analytics, we now wait until all Target calls have resolved (including redirect offers) before Analytics fires, resolving the race condition that previously existed.
- Updated Adobe Analytics extension to support AppMeasurement 2.9.
- Added "Make tracker globally accessible" feature in the Adobe Analytics extension, which enables the tracker to be scoped globally under
windows.s.
- Fixed a bug that caused list view to reset when returning from detail view
- Fixed a few bugs to improve loading of resources in the revision selector
- Fixed a bug where multiple rules were overwriting s.events in the Adobe Analytics extension
The Launch and DTM libraries using Akamai are now available on CDN edge nodes in China. This provides much faster library load speeds for end users in China.
The information contained in error messages has been improved and expanded throughout the API and UI. This should be especially useful for build failure messages.
Changed the behavior of the Add All Changes button on the Edit Library page. Previously, a resource was only considered "changed" until you had added it to a Library and saved it. Now a resource is considered "changed" until it has been published to the Production environment.
The Adobe Privacy extension provides functionality for collecting and/or removing user IDs assigned to end users by Adobe solutions.
The new Value Comparison condition Compares two values, using any of several available operators. This replaces the functionality of several older conditions that were far too specific.
This condition allows you to specify the number of times the condition should return true within a time period or event occurrence. Examples: 5 times per Day, 2 times per Visit.
Data Elements now have a "None" duration option. Newly created Data Elements default to this setting.
Environment pages now display async embed codes as the default. Toggling between sync and async works exactly as before.
Open source documentation for Launch now available at https://docs.adobelaunch.com.
Events in rule builder are no longer draggable.
Improved warning messages.
-
No longer prompt for unsaved changes on rule components when
changes have been saved.
-
Fixed problematic interactions with Active Library.
Rule ID is now emitted for each rule in a build, and can be referenced in the browser.
Page Load events now execute in logical order in async deployments (Library Loaded > Page Bottom > DOM Ready > Window Loaded).
Data elements can now reference other data elements.
Minor style improvements.
- Active Library has been moved to the top right to make more space for content
- Action buttons moved to the top right
- Bulk Edit now lists smarter actions, collapsed into a More menu on smaller screens
- Form fields now have default focus
- Updates AppMeasurement.js to 2.8.0
- Adds support for server-side forwarding
The Adobe Analytics for Video Extension adds the core Video Analytics JavaScript library. This library provides the functionality for adding the mediaHeartbeat instance to a Launch site or project. The Adobe Analytics for Video Extension (VA Extension) requires two additional extensions:
- Analytics Extension
- Experience Cloud ID Extension
- Updates visitor.js to 3.1.0
- Adds two configuration properties:
resetBeforeVersionandserverState
Support was added to extension cards on the catalog page for future Learn More links to more information on the Extension Detail page on adobeexchange.com
Event details are copied to the top-level event object (%event.detail% in text fields and event.detail in custom code)
Fixed the following issues in the Core extension:
- Custom code windows were throwing
document.writeerrors and not executing in async deployments - Main modules were not included in a library
- Problems occurred with min and max values on the Random Number data element
You can delete data elements, rules, and extensions. See Delete Resources.
When you link your DTM embed code to Launch, you can keep your DTM production embed code on a page, but serve Launch files there instead of DTM. See Link DTM Embed Code to Launch.
This release includes several interface enhancements:
- Rebranding of Marketing Cloud to Experience Cloud
- Element styling
Fixed an issue that caused a database query to take a long time to run and cause occasional 502 errors on API queries
- Added Adobe Exchange listing to extension.json
- Added checks to see if Target is disabled and if Authoring is enabled
- Fixed an error in the Adobe Target Extension that prevented the Visual Experience Composer from unhiding the page when deployed through Launch.
- AppMeasurement has been updated to version 2.6
- The initialized Analytics tracker is now exposed through a shared module in the Launch extension so other extensions can include code to interact with it.
- Updated views in extension configuration screens
- at.js has been updated to version 1.2.3 (adds support for JSON offers)
- Enable/Disable actions ask if you want to add to your Active Library
- Create a new library from the Active Library drop down
Fixed an error in the Adobe Analytics Extension that caused "Error, missing Report Suite ID in AppMeasurement initialization" to appear in the browser console.
Cache control headers are now automatically set for libraries hosted on Akamai (assets.adobedtm.com). Previously, we did not set cache control headers for any files hosted on assets.adobedtm.com.
- Production builds: Cache control headers are set to 60 minutes
- Staging builds with "-staging" in the filename: Cache control headers are set to 0 minutes
- Dev builds with "-development" in the filename: Cache control headers are set to 0 minutes
- Launch Staging builds without "-staging" in the filename: The default of 60 minutes is inherited
- Launch Development builds without "-development" in the filename: The default of 60 minutes is inherited
Note: It is up to browsers to receive and respect the cache control headers. Some browsers might ignore them.
Important: Launch developers who do not have "-development" or "-staging" in their Environment embed codes need to re-create their Development and Staging environments to get the 0 cache control header. If you don't re-create the environments, you'll have the same 60-minute cache control as the production libraries.
Events in rules can now be assigned an order. When an event is triggered, any rules that use that event are executed in the order defined. Lower numbers run first (1 comes before 10). See Rule ordering for more information.
Set a new or existing library as your active library. When creating/editing rules, data elements, or extensions, you'll now have an option to save and build to your active library. This will immediately save your change to your library and execute a build. The status of the build can also be seen.
You can now pass actual objects to the log function and view them as objects in the browser console when using _satellite.debug(). This makes the Launch logger behave a lot more like console.log. To enable this change, there is no longer a persistent history attached to the _satellite.debug() function, so when you call it for the first time, you'll no longer see a history of past events. You will see any debug messages from that point forward.
-
On-page
The Launch library now includes support for running asynchronously. There are important ramifications for how this changes what happens in your library. You should read the Async documentation before you do anything.
-
Async Toggle on Environments
When retrieving the embed code for an environment, you can now flip a toggle switch to get the embed code if you want the library to load asynchronously.
The following have been added to the core extension:
- Random Number Data Element
- Page Info Data Element
- Date Condition
- Sampling Condition
- Information Videos on Empty List Pages
- Persistent filters
The following changes were made to be more descriptive of the actual behavior in sync and async scenarios:
- Page Top is now called Library Loaded
- On Load is now called Window Loaded
- Fixed an issue where the Launch library would load twice in certain edge cases.
- There are now audit log entries for Property Delete.
- Improved the load speed of the Revision Selector when you quickly click from one entry to another.
- Help links now open in a new tab.
Release date: November 8, 2017
Important: Launch is being rolled out incrementally to Adobe Experience Cloud customers. If you have would like a chance to get early access, please put let us know by entering the required information in the Launch Release Form.
This is the first release of Launch.
Launch is the next-generation of tag management capabilities from Adobe. Launch gives customers a simple way to deploy and manage all of the analytics, marketing, and advertising tags 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 Launch customers in an app-store experience so they can quickly install, configure, and deploy their tags.
Launch enables you to:
Launch is offered to Adobe Marketing Cloud customers as an included, value-add feature. Launch is an entirely new product with a new code base, designed to replace the previous Dynamic Tag Management (DTM) service. However, DTM 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.
- Faster time to value
- Trustworthy data through centralized collection, organization, and delivery using data elements
- Compelling experiences through the integration of data and marketing technology using rule builder
An extension is a package of code (JavaScript, HTML, and CSS) that extends the Launch UI and client functionality. 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.
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
The rule builder includes real-time error checking and syntax highlighting for your custom code.
When the criteria outlined in your rules are met and conditions are satisfied, the actions you define are executed in order.
Collect, organize, and deliver data across web-based marketing and advertising technology.
The publishing process enables teams to publish code to pages. Different people can create an implementation, approve it, and publish it to your pages.
- Changes to your code are encapsulated within libraries you define
- You specify where and when you want your code 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
The Launch container tag is 60% lighter than Adobe Tag Manager 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.
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