Adobe Experience Platform Data Collection

Currently, you can build/advance a library from the publishing tab as there is a dropdown menu with three horizontal dots that allows you to do this without opening up that specific library. However, you still need to open the library up in order to remove or add an environment when the library is i...

It would be great if the rule search feature in launch was case sensitive. Currently, we use abbreviations like "CC" in the rule names that have custom code in them. When you search that in Launch you get both that acronym and rules that contains words with "cc" in them. Example Rule Name: "Medicare...

Currently only the libraries in the published column display the date they were published. It would be very helpful if libraries that have been built to development or staging displayed the date they were last built in the same manner. This would save a lot of time since you wouldn't have to go open...

When you create a Launch mobile property it only includes instructions for installing the AEP SDK for fully native Android and iOS applications. The ReactNative instructions are found in the Adobe documentation (see link below) but are not readily available in Launch and you must combine that code w...

Chrome, and other browsers I assume, will populate their history log based on the document title Filling out time sheets becomes much easier when I can identify which projects I was working on throughout the day. I've used to plugin to make this happen locally and it has been very helpful.

We have tried implementing an AWS SFTP location with Adobe Launch, which we discovered is not supported. From our support rep:"I checked internally and found that Currently 'S3 does not support SFTP Symlinks for Launch SFTP Hosts'. It is my understanding engineering is considering this as a feature ...

Creating an overview page with more useful information such as:Change History (most recent Data Elements / Rules updated)Most recent Publish History (and by who)It would be much better than the youtube link. 

Idea: Have Rule / Condition / Access Context to display on the rule overview page to help with reviewing.Goal: Have more context and avoiding a step in clicking a page view when looking at rules.  

These two core rule types do not function differently. Also, these rules do not work without turning on the regex even when i'm not using any regex to match the url. 

Every rule should have a quick view button next to it. The quick view should show all the metadata (event configuration, conditions and actions) expended in a single view. This will be very helpful in reviewing / validating rules.