Adobe Experience Platform Data Collection

Have conditions as separate entity will help to reuse condition across Rules. Currently its more of rewriting same across onn Rules( which can help to trigger diffrent tags on same set to cinditions).Hope it make sense.

One challenge I have found with Adobe Launch is debugging custom rules. The custom code in Adobe Launch is put into JSON strings and evaluated resulting in the code not being available in Developer Tools for debugging.I found a feature in Chrome Dev Tools that allows a local override and a “SourceUR...

In DTM the delay link activation breaks the JS-based links and in some instances anchor links functionality.The request is to either:1. Have an option to disable the delay link activation on links that are pure anchors, contain the URL of the existing page + an anchor, or contain javascript commands...

would be nice to know what the warning or error messages are in the custom code section. Can't see what the issues are, just shows warning signs.

Being able to quickly copy a templated launch property would allow for quick standups of scripts ready to launch analytics, experience cloud id service, target, ads, facebook pixels or all of the above. Our use case comes from wanting to get a standardized, unique script so we can quickly add adobe ...

I have a few improvement ideas for the publishing process. One is already covered here: rapid rollback Here a few more:in DTM it was sometimes a bit annoying that a saved rule was directly visible on staging. But now that we have a proper workflow I would like that feature back for libraries that ar...

In DTM,  _satellite.getVar will honor the "window." prefix in the first argument.In Launch, this is not supported. For example :_satellite.getVar("window.digitalData.page.pageInfo.pageName")It is fairly common practice in DTM to use the above as it will fail gracefully if any part of the nested obje...

I used the notation field at the bottom every time to add a note about what change I made and why. (well, most of the time )  I would like to see that in brought back in Launch.  It's a good habit to get into.

In DTM it didn't matter which order you put in the s.props once you saved they resorted into order. So for example you could enter them in s.prop1, s.prop23, s.prop2, s.prop11.  And when you saved and reloaded the rule it would sort them s.prop1, s.prop2, s.prop11, s.prop23.   Which is really handy ...

In DTM when you look at the rule details, you see if the analytics part contains custom code before you open the accordion containing the details. I miss this featue in Launch. Currently I would have to define a naming convention for the action so it is clear that it contains custom code.