Adobe Experience Platform Launch is being rebranded as a suite of data collection technologies in Experience Platform. Several terminology changes have rolled out across the product documentation as a result. Please refer to the following document for a consolidated reference of the terminology changes.
Private extensions are now available! Private extensions are extensions that are developed by your company and are only available for properties within your own company. No one else can see or use them. Other than that, they behave exactly like regular extensions.
Would you like to provide a standard set of functionality that hundreds of your properties should use in the same way? Package that up into an extension and have all your properties use it. Writing the same custom code and using it over and over again? Put that into an extension and stop writing custom code.
When you create properties, there is now an advanced option to “Configure for extension development”. This creates a “Development” property that can be used for testing your private extensions during development before you’re ready to make them available on your regular properties.
You can now make a copy of a rule within the same property. Before you ask, the answer is “Yes, copying it to another property is coming next.”
_satellite.pageBottom()) would clear website content.
Tags have gone mobile!
Used by thousands of customers for web tag management, the tag workspace can now be used to manage your mobile SDKs.
Creating a mobile property in the Data Collection UI allows you to:
Create data elements and build sophisticated rules that can combine actions across multiple solutions.
Manage mobile extensions:
Mobile Core extension and all additional extensions can be downloaded and installed through 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, all the resources in it are now checked and tags prompt you to add any required extensions that are missing.
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 tag properties now come with a “Managed by Adobe” host and three environments (one of each type) by default.
The extension catalog is now sorted by display name rather than name.
Adobe Experience Platform users are now 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.
The tags 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.
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 tags is available at Experience League.
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).
Minor style improvements.
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)
You can delete data elements, rules, and extensions. See Delete Resources.
When you link your DTM embed code to tags, you can keep your DTM production embed code on a page, but serve tag files there instead of DTM.
This release includes several interface enhancements:
Fixed an issue that caused a database query to take a long time to run and cause occasional 502 errors on API queries
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.
It is up to browsers to receive and respect the cache-control headers. Some browsers might ignore them.
Tags developers who do not have
-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 tag 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.
The tag 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 changes were made to be more descriptive of the actual behavior in sync and async scenarios:
Release date: November 8, 2017
This is the first release of tags in Adobe Experience Platform.
Tags is the next generation of tag management capabilities produced by Adobe. It gives customers a simple way to deploy and manage all of the analytics, marketing, and advertising tags necessary to power relevant customer experiences.
Tags empower anyone to build and maintain their own integrations by using extensions. These extensions are available to Platform customers in an app-store experience so they can quickly install, configure, and deploy their tags.
Tags are provided to Adobe Experience Cloud customers as an included, value-add feature. Tags 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.
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. Rules provide options for:
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.
Automate implementations or a group of technologies.
The container tag created by tags 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.
Tags provide several improvements over similar systems. These include:
document.write ()where Chrome doesn’t allow it