Adobe Experience Platform

Adobe Experience Platform Launch​Use CaseAllow view, and the ability to copy, the code that is generated by Launch App Extensions. Currently no visibility into extension's code   Business ImpactWill be a timer saver in many ways when trying to see if extension contains vendor specific requirements that may not be included in Adobe's version. Will allow us to compare back to the vendor's current documentation for their site tags to ensure the most current is being used. Quick copy the code and add the new requirement in a custom tag if not present in the extension.   Ensures we will know what is being deployed - currently somewhat of a black box. 

I would like to be able to see the type of the Data Element in the Data Elements List Page. An additional column could be added which shows the Data Element Type (similar as it was to DTM). For this the value from the "Data Element Type" field in the Data Element could be used.In addition to that a possibility to filter by Data Element Type could be added in order to show only Data Elements of a certain type.

The previous version of the debugger keeps all the requests open when changing tabs in the browser. The current version shows only the requests for the active tab.This creates extra steps in the workflow when working between two or more tabs and the debugger window. This is often required when validating variables in an Adobe Analytics workspace while testing a page. Leaving the tab also collapses the request so it has to be re-opened and then scrolled to the right to see the current hit.It would be better if the request would stay open, even when the active tab is changed. It would also be better if the focus remained on the most recent hit, rather than adding them outside the window so that they have to be scrolled to.

Sometimes you need to find where a prop, eVar or something is set inside a launch property. If a rule or data element is misnamed or documentation isn't up to date it can be very difficult to find.It would be amazing to have a "code search" feature so you can search for exactly which rules lead to the setting of a variable. You could also find how data elements are set much faster in a similar manner. Other tag managers have this feature and it can be a huge time saver for new starters or consultants getting up to speed on the analytics implementation.On top of this, when viewing data elements it would be extremely useful to be able to see every rule they are currently used in and vice-versa.

Currently in Adobe Launch - we see a blue button when an upgrade is available.  But this does not tell us what is being updating (why do we need to upgrade).  Can we add a version history to all extensions that says what were being changed?  Currently - we are just hitting upgrade and do not know what we need to test to verify it will work on our site.  This should be standard across all Adobe / third party owned extensions to ensure we, the client, know why we should push this change into the system.

Description - I'd like to be able to always view the horizontal scroll bar in debuggerWhy is this feature important to you - to facilitate exploration of the values collectedHow would you like the feature to work - I'd like the vertical scrollbar to always show at the bottom, regardless of where I am in the rows collected.Current Behaviour - I have to vertically scroll all the way to the bottom to find and reach the horizontal bar. 

Description -AEP Segments need to have a way to organize them into folder structure for easy use and maintenance by different Business teams. Why is this feature important to you -Easier to identify and manage different types of segments.How would you like the feature to work -Ability to create folders and then create segments, somewhat similar to campaign workflows in Adobe Campaign. Current Behaviour -All segments show up in the same page.  

Within Adobe Launch, we can have several users go in and contribute in the creation of rules, data elements, custom code in the extensions (like Adobe Analytics).  Can we add in the name of the person who made the changes in each version.  currently - we know when the last version was saved, but we do not know who made the change.  This will help when we need more information on why something was changed. 

In DTM, there are two images used in the Status column  - a check or a clock with a blue circle - that let me easily know if an item has been modified since its last push to production. This Status image is used across the board on rules, data elements and tools in DTM.In Launch, this concept does not seem to exist.I really like and utilize this feature in DTM. Could this feature please be applied to Launch too?

Hi Team,There is no way to know which user made latest changes to "resources" while we create a development build. Please add a "Modified By" field as wellWould request your team to add it.Best ,

Would be nice to be able to see who made changes / see a history of rule and data element changes for auditing purposes.

We are in the process of migrating from DTM to Adobe Launch.  One of the features that we have noticed that is missing that is critical for auditing purpose is to know who published and when.  Within both tools, it tells exactly when the last code update was released.  In Adobe DTM, it does show who was the publisher, but in Adobe Launch this feature was not there. Could we please add in Adobe Launch the ability to see who published each change?

Description - one can now change rule or data element and save it without attaching to particular library. It leads to when second person could work with the same rule or data element and make his own changes then publish it. And publishing to production will release changes from both web-masters due to second person won't have idea idea that he worked with someone's changes.  DTM had such feature. It looked like clocks. If someone saw this active indicator, one would find previous person who commited changes before continuing working with rule or data element. Also we don't have option now to see who commited changes. Which is problematic sometimes. Our company also forced to add Last Names to Libraries to get an idea who last worked with components of property.Why is this feature important to you - to make process of working with Launch more simple. And also to add feature that will help to review last changes and connect them to concrete person in company.How would you lik

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 up each library in order to see what date it was built last. In some of my Launch properties I have 10-12 libraries waiting in the development queue for code fixes from our developers. If this was implemented I could see at a glance which ones needed to be built again and which ones had a more current build.

From a security point of view, it needs to be really clear within the tool who is approving/progressing a library through each of the following steps:Summit for approvalApproved for publishingPublishingAt the moment it is really opaque; Although there is an audit log it's next to impossible to decipher.  Also I would expect this information to be available within the area where you are viewing a particularly library which it is not currently (there is an 'activity log' but this just shows the date when a 'build' occurs and contains no user info)

Hello Team, Can we have the ability to add metadata for the Property, rules, datalements, extension so that we can get to know easily who create it, what's the purpose, under which category the rules, datalement resides. It would be great to know this things to avoid redundancy. This feature have in DTM at the moment and with the help of metadata we can search the things easily. Currently in the list of all properties, I'm not able to see who created that property? when it's published last time and the history overall?

Description -From a governance perspective separation of duties between Developing, Approving and Publishing a library is really important to us. Unfortunately, the permissions management in Adobe Launch is not flexible enough to enable us to enforce a separation of duties between developing and approving a library. This is because like many Digital Analytics teams we do not have enough people to have a separate development team with development rights and a separate testing team with approval rights.  Instead, users perform both development and testing activities which means they have to hold both the "develop" and "approve" permissions.  This means the system will allow the user to approve a library that they have submitted for approval (i.e. they can approve something they have developed, therefore no system enforced separation of duties).Why is this feature important to you -Governance and security is incredibly important to our organisation and many other

It would be very useful to know the date that the revision was created when using the compare revisions screen - at the moment you just get the revision number (e.g. revision 3):  

It would be nice to be able to clear logs and events from one place and/or have the option to not persist between reloads. Why is this feature important to you -It is annoying to have to clear logs and events in different tabs every time I reload.How would you like the feature to work -Under settings you could have a clear all data button and a persist data check box. Current Behaviour -You have to clear logs and events from different tabs. 

Description -When using Adobe Launch oob, you insert a script to your website that points to "assets.adobedtm.com".As it is possible to get CNAME from Adobe for Analytics and Target (which helps a lot with Cookie issues), Adobe should offer this for Launch, too.Why is this feature important to you -I think it is important, because many "browser privacy tools" may block the domain "assets.adobedtm.com", so the Tag Manager is not loaded for those visitors.I really appreciate that Launch offers a "self hosting" option, but it is struggle to get this done with internal IT (at least for me).How would you like the feature to work -Just like the CNAME program for Analytics/Target, it should work the same way (including a SSL certificate for the new CNAME).Current Behaviour -As I said above, the default Launch domain may be blocked as "browser privacy concerns" are rising. It would be a good alternative for "self hosting"

s.t() and s.tl() both support variable override which allow to set variables only for the call and keep the other variables as they were.For the moment is not possible to call "Send Beacon" with override variables.It's would be greate to (at least one):- add an action that "capture" all "Set Variables" to use it as override variables for the next tracking call- add an option for "Set Variables" to "buffer" variable and use it as override variable for the next tracking call- extend "Send Beacon" action settings UI to have the same UI as "Set Variables" for overwritten variablesSome times you need to compute variables based on page variables (like events) without update it.See also Adobe analytics extension - clear variables on bea... - Adobe Experience League Community - 402972

In the old debugger it was possible to navigate through the events with the arrow keys, so you would not have to scroll all the way to the bottom to drag the horizontal navigation bar. We are utilising a lot of parameters, meaning the horizontal scroll bar is hidden from view, and not easily accessible. That feature of scrolling with the arrow keys is missing from the Adobe Experience Platform Debugger, so that you quickly lose overview of the events, when you have many parameters. Can you please add this feature (again)? Thanks 🙂

Description - The ability to create custom index(es) on AEP datasets for better query service performance. Not sure if Azure Data Lake Service accomodates the encoding, but it looks like there could be serious performance gains by defining a ColumnIndex and OffsetIndex, reference.Why is this feature important to you - Many users are interested in using Query Service, but the current UI can't conveniently handle larger requests, and even directly using ODBCs can be time consuming for larger datasets. Though there is native partition elimination and other benefits of using column-oriented storage, it would be extremely useful if clients could define a custom index improving performance. Even if only a single index per dataset, it could be a very helpful feature.How would you like the feature to work - It could be added to the UI of the data set with a simple checkbox/numbering selection for composite indexes with a specific order. Maybe a dialogue pop-up warning of any extra storage-rela

Description -In the Launch part of the debugger. There's the Console Logging checkbox. That's the subject of this suggestion. 1. Stop reloading the page on that checkbox change. You don't need to. Just execute _satellite.setDebug(1) and set the local storage value. 2. Have it on by default whenever a library substitution/setting is done. The cases when it's not needed by default are... edge cases.Why is this feature important to you - 1. Stops wasting my time on needless pageloads.2. Stops wasting my time on enabling it when it's obviously the intention.

DescriptionIt it possible to track localhost traffic in the Adobe Experience Platform Debugger?I am trying to use it locally, but I don't see anything within the toolWhy is this feature important to you -Will allow me to test my configuration locally and work quicker