Description - Currently there is no way to specify the order of execution of extensions that are included in launch.js and run at the top of the page.
Why is this feature important to you - We use a data monitoring technology that is deployed through Adobe Launch and needs to be the very first extension that runs when the library loads so it can properly monitor the data being collected on pages. As of right now it can't monitor all technologies consistently because the order of extension code is randomized at every publish and there is no way to specify that extension A should load before extension B.
How would you like the feature to work - I would like to be able to specify either the exact processing order or be able to set an optional priority score (similar to rules) for extensions that are bundled with the core launch.js file.
Current Behavior - Adobe Launch does not currently have a way to specify in the interface the priority of how extension code executes when the library initially loads on the page.
