Adobe Experience Platform Data Collection

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.

Similar to Make the data element field wider (Analytics Extension), but for rule names.Rule names can be thousands of characters long (as proven in this blog post), but the input field is too short to show anything more than a few tens of characters.

Steps to reproduce:Click on a Help menu item.Expected results:Help page opens in a new window/tab, like how it is for other Experience Cloud products.Actual results:Help page opens in the current window/tab, thus replacing whatever work you had been doing in Launch prior to opening the Help page.

The struggle is having to create elaborate Rule Names to determine what is included in a rule.The community has created long names to resolve this pain point but it is becoming too long and a huge learning curve for people being onboarded into an implementation.The recommendation would be to create ...

Please ensure the unsaved changes box shows up only when a change has been made in a rule.To reproduce, go into a condition that has a text field, such as Path Without Query String. Or go into an action with custom code. Open the editor and click into the text box. Do not make a change. Then cancel ...

Hey guys, for websites we have the awesome ability to set up a data element in Launch and call _satellite.getVar to get the value of that data element, as described on Launch object reference. We are using this with constant data elements from the core extension to provide some config values to our ...

With 4.4.0 version of Web Experience Cloud Visitor API, you can apply SHA-256 algorithm to the values passed to setCustomerId() method.SHA256 Hashing Support for setCustomerIDs This makes securing customer-identifiers much easier. I have been told that there are plans to add capability to mention SA...

We have a security requirement when using AWS API Gateway that requires any incoming POST requests to include a custom header and a secure key.The use-case is for when Adobe Launch sends POSTs for Callbacks whenever a rule is created for example. See Creating Adobe Launch Callbacks docs here:Adobe E...