What I did now is to define a s.doPlugin method, where I check for s.linkType==='d' and then add my custom eVars...

Not sure if I understand you correclty, but in either Chrome or Firefox you can still pretty print the compressed file from launch. Just open the developert tools, navigate to the source, in your cause probably the launch-HASH-ENV-min.js and click the {} icon. There are still some limitations to deb...

Yesterday the action elements were completely f***d up. I couldn't properly reorder them, as where I dropped it was not the place where the element was placed afterwards.

Be aware some plugins may not work in Launch due to the new compiler/compressor of the scripts. It renames all the variables and "s" isn't always called "s" anymore in the built library.One I found an already reported via Customer Care is the getVisitNumHere a fixed verison of that plugin:/** Plugin...

It happened to me a few times as well, but I didn't record my steps to reproduce as you did. So I can't say if the same steps caused my problem. But I agree sometimes the action order gets screwed up between saves.

In the Analytics Extension you can configure which file extensions are considered download links. Is there a way to provide link specific eVars and props to this tracking call?We are currently using the s.doPlugins as suggested here  https://forums.adobe.com/ideas/5674#comment-163455 to set some add...

I fully agree with this. I also have some ideas how to implement it:Have a flag in the Set Variable Action to also include global variablesHave a separate Action called something like "Set Global Variables"We now did something similar to joshd's approach. We have a custom Code JS in our source repo ...

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...

I agree that this would be a good feature, especially if it was working in DTM.But for this example case I would create data elements pointing to the datalayer anyway. With the ContextHub Extension and a custom JSON Schema this is rather comfortable to do and as far as I know there it also fails gra...

I also added an idea for the overview page which goes hand in hand with this:Display more information in the rule overview