Adobe Experience Platform Data Collection

I know that this was basically impossible to do in DTM, but I'm wondering how feasible it would be to allow the property administrator to configure Launch's primary object from _satellite to another string so that multiple properties could coexist on the same page. My reason for wanting this is to a...

With DTM you had "two" more columns for the rules: Event and a column for each possible extension. The former could still be easily retrieved from the event element(s) of the rule in Launch. For the latter it may also be possible to have some information extracted from the actions. Maybe listing all...

In Adobe DTM, there was a robust system that allowed side-by-side comparison of any pair of revisions of a single rule. I am now deeply missing that functionality in Adobe Launch.Currently, I am able to easily access a revision of a rule that's in an Upstream library (for example, while I'm developi...

Currently if I select a data element from the pool it is just copies to the text field surrounded with %%. If for some reason I change my data element, I need to find all rules where I used it manuall and change it. If the element would be linked to the rule, a change in the data element name would ...

Ideally Launch would include the same functionality to mimic the _satellite.dtmRuleStackArray functionality that is in DTM.  Doing so provides a great audit mechanism, as well as a way to perform a gap analysis for rules that are not in use.

We should have the ability to control default lifecycle metrics behavior in the Mobile SDK configuration. This would include toggling whether or not events such as app launches automatically trigger lifecycle tracking, so that they might be manually sent or disabled entirely.

Since we have multiple environments wherein multiple rules, data elements and even entire properties can be tested. What if we create such features to schedule the rule publish from the test to dev environment and if we are successful in this migration then to prod environment.At times we test the t...

I've found it unnecessarily difficult to delete anything in Launch.  Before I can delete anything, I must first disable it and ensure that the disabled item is published to production.  Once it has been published to production, I can then go and delete it and push it through the publishing process. ...

Adobe Launch is used to write code.  It should have the ability to store that code in a standard software repository (Git).  This should include at least custom code, but would preferably also include files representing non-custom code (preferably in JSON format).  Nearly everything you can do with ...

I should always be able to conditionally load extensions on a page.  For example, I do not want Target to fire on every page.  The extension gives me no way to conditionally define this.  So instead I end up having to control it with a rule.  The inability to do this makes many extensions useless to...