Tag: Adobe Experience Platform Data Collection Tags

Should you really build an Adobe Launch Extension?

If you are using any solutions from the Adobe Experience Cloud family of tools, chances are you are also using Adobe’s Tag Management System, Adobe Launch. Launch works like many other Tag Management Systems (TMS), in that it can bring tools and code to a website without the need to change the source code of the website it is running on. This allows the users of the TMS, typically digital analytics or digital marketing teams, to be somewhat independent from IT and development teams when they want to bring technology, like onsite analytics or marketing pixels, to a page. In Adobe Launch, Extensions are used to bring the actual functionality to the websites that it is running on. A good example for this is the Core Extension: This Extension allows us to run JavaScript code on the website (using the Custom Code Data Element or Action), listen for events like […]

Execute a rule only once in Adobe Launch

When you are managing an implementation of Adobe tools like Analytics, chances are you are using Adobe Experience Platform Data Collection, formerly known as Adobe Launch, Adobe Dynamic Tag Management, or the Adobe Tag Manager (and no, this is not a SEO text, it’s the actual list of names. I will still call it Launch for the near future) to implement other tags as well. While Launch is great for making implementation of Adobe’s own tools very fast and easy, managing other tools is not always so straight forward. A common requirement for those 3rd Party tags is to fire a certain tag or pixel only once. What once really means (once per session, user, day, year?) might differ from tag to tag, so as a result it can be surprisingly difficult to fulfill those requirements reliably and consistently. On top of those varying definitions of once, Adobe Launch has […]

Bringing clarity to Adobe Launch using Call Traces

The Adobe Experience Cloud (AEC) comes with its very own Tag Management System (TMS). With Adobe Launch, by Adobe, implementing a basic set of AEC tools like Analytics or Target is quick and easy. That ease of implementation regarding Adobe’s own tools comes with the possible downside of having to put in more work for non-Adobe tools. Depending on how important those Adobe tools are to you, Launch might be your first choice as TMS regardless. Unfortunately, Launch is not ideal when it comes to more complex setups. For example, having a chain of actions that needs to be executed in a specific order can require some manual workarounds, like putting steps into separate rules. The same is true for guaranteed conditional execution within rules, which requires either custom code actions or branching rules into multiple others. I have seen setups with literally hundreds of rules because of those restrictions. […]

Using Adobe Launch 🚀 for configuration management

Adobe Launch (, by Adobe) ist the tag manager that comes for free with the Adobe Experience Cloud. You can use it to manage and orchestrate all the marketing tags on your websites (not only from Adobe) and reduce integration efforts for the mobile Adobe SDKs to just copy-pasting from the launch interface. For a tutorial, look below on this post. Launch is the successor to the Adobe Dynamic Tag Manager (DTM) which was used in the past, formerly known as Satellite. In 2018 Adobe announced plans to retire DTM fully by 2021 (source: https://medium.com/launch-by-adobe/dtm-plans-for-a-sunset-3c6aab003a6f). So if you are still using DTM, you should start migrating to Launch, which is only a one-click-action under ideal circumstances. Launch can host scripts for pre-tailored use cases (called Extensions) or custom code. With rules, we define when and where things should happen. Last, Data Elements let us define variables that we can use […]