Adobe Experience Platform

Description -   I am the TAM for Honeywell, initiating a feature enhancement request on behalf of my customer, Honeywell.On the "Audit Events" page in the "Adobe Experience Platform Launch" console interface, there is currently no way to apply filters to the data displayed.In Honeywell's instance, they have over 5,000 rows of Audit Event data that are returned.It would be helpful if the rows can be filtered using the header rows.Can a JIRA ticket please be raised with this request?Why is this feature important to you - It's cumbersome to locate records with no way to filter or searchHow would you like the feature to work - Add (1) filters to the column header row (Sort A to Z, Z to A, etc.) and (2) add a basic search features to query the displayed data set. Current Behaviour - No Current way to filter or manipulate data rows

Hi guys,Can we please have release notes for extension upgrades? All we currently have is a single Upgrade button with an "are you sure?" blurb, with no info on what the update will actually do;This gives me zero confidence in upgrading any of the extensions, as if they break something I don't think I can revert the change.If I have release notes, then i could at least make an informed decision on whether to proceed with the update.A direct feedback link to the team that owns the extension would also be an added bonus, as I could then ask questions.Cheers, Jez

Description: Undo latest changes to a defined "snapshot"I would love to have a new feature which allows me to go back in "property history" to a defined point. maybe it is like working with a git branch: at any point I can create a git branch, try some changes. if it doesn't work as expected, I can delete the branch and revert everything to the master (last snapshot)Why is this feature important to youEspecially when new requirements arrive, there are multiple solutions on how to implement it within Adobe Launch. Or it is just a test if an idea would work as expected. But if something failes or it doesn't work as expected, the "redo" can be a huge effort since we need to edit each single item (extensions, rules, data elements) and set it to the last published state.How would you like the feature to workThe new feature would consist of two action:"Create a property snapshot" which makes a backup of everything within a property"Revert to snapshot" which would delete everything and load l

Within the Experience Platform Debugger, it is easy to replace the Launch embed code with a different one, but any time I do this, the default code is including the async keyword, while or websites have the embed code loaded in sync.Therefore I always have to remove the "async" keyword in the embed code before I apply the replacement when I'm testing. Would it be possible to have respect the sync/async way of loading of the current embed code as the default for replacement?

Description - Add a feature to the extension to allow a checkbox to request that variables are cleared after the beacon fires.Why is this feature important to you -Nice generic feature instead of custom code to add to the extensionHow would you like the feature to work - When the option is checked - add the following after the extension is loadeds.registerPostTrackCallback(function(){  s.clearVars();});Current Behaviourrequires custom code 

Description -I'm testing Adobe Launch with alloy.js and the debugger is not showing the extension enabled? See screenshot.Why is this feature important to you -How would you like the feature to work -Current Behaviour -

Hello @1905403,the functionality to use a dropdown list for properties and environments to replace the embedded Launch code is very helpful. Unfortunately the list is limited to 100 entries - and we have more than that. We support hundreds of websites, and for many of them the request was to track data without implementation effort. Therefore we implement in an own Launch property page and button detections per website (more or less). We are on the way to migrate (as in the meantime management was convinced of the benefits of more detailed web tracking) but we have to deal with more than 100 properties for a long time. Therefore it would be great for us to increase the limit for the dropdown list to e.g.256.Because now the benefit of this functionality is very limited for us. And on the other hand important because it would reduce effort and time for us.

Description -When I'm logged in, in the Debugger extension, I expect to see the eVars, props and events with their friendly name, instead of their number. This is not happening, even though I'm an admin.Why is this feature important to you -Ease of debugging. 

It will be highly flexible if the Launch properties could be mapped and remapped to Environments (embed codes). The benefits:- no need to contact website dev team to update the embed codes- easy to fix an issue if a wrong embed code is added to the page (website)- easy to merge the implementation on several websites into one property or vice versa to split websites among various properties How would the analytics developer/ architect work with this feature:1. Create environments one per website/ domain/ website environment/ app2. Ask the web team to add the embed codes3. Manage the environments mapping in the Launch UI 

I've submitted a forum post asking about how to set List Variables via Launch UI (linked below), and the response was that this needs to be done via Custom Code.  Setting of Adobe Analytics List Variables in Launch? I'm requesting that this functionality be built into Launch to maximize the options available to non-developers like myself.  Thanks

It would be helpful if there was a Core data element that returned the value of the Launch library "Name". This would make it easy to set the value to an Analytics eVar for debugging purposes. We name our libraries using the Major.Minor.Patch versioning convention and it would be helpful to know which Launch library a website visitor was using. Sometimes after a new library is published it seems like some visitors may have the old library cached in their browser. If we could capture the library "Name" as an eVar, we would know this for sure.  

We would like all the existing Adobe Analytics dimensions (eVars[1-200], props[1-75], and events[1-1000], list[1-3]) to be automatically mapped using a supported or new schema mixin. In addition, this would be needed for product syntax eVars and events. This is important for existing implementations with a significant number of custom dimensions. It will ensure customers will not have to manually map every single custom dimension via processing rules. In addition, it will allow customers that leverage the raw data feed to use the AEP SDK.  At this time, only specific dimensions are automatically supported.https://experienceleague.adobe.com/docs/experience-platform/edge/data-collection/adobe-analytics/manually-mapping-variables.html?lang=en#context-data This is already supported for standard dimensions like products, commerce, and page details. https://experienceleague.adobe.com/docs/experience-platform/edge/data-collection/adobe-analytics/automatically-mapped-v

Description - One of the limitations of using the setVar() function to create a data element rather than the Launch interface is that you have no control over the storage duration.Please can you consider adding control over storage duration?Why is this feature important to you - Improved flexibilityHow would you like the feature to work -An additional optional parameter that allows you to choose the same storage duration as the Launch interface i.e. none, page view, session, visitor For example:_satellite.setVar('product', 'Circuit Pro', 'session'); Current Behaviour -No control over storage duration of data elements set using the setVar() function

Description -Please add the ability to search "resource changes" in the edit library screen.   At the moment it is possible to search "resources upstream" but not the "resource changes" which seems odd as it is the changes you are work on and therefore most interested in 🙂Why is this feature important to you -Improved workflow/easy of use:  We often have a lot of changes in a library. Without the search functionality it's difficult to find things.How would you like the feature to work -Add a search box at the top of the resource changes list.Current Behaviour -One can only search "resources upstream" but not "resource changes" in the edit library screen

DescriptionTypically, we want to compare the latest version of a rule/element to the live version.  It is very rare that we want to compare to the previously saved version which is likely to be a minor tweak/save point.Why is this feature important to you?This simple enhancement would save timeHow would you like the feature to work?Default to live revision vs. latest revision.  For example, if the current revision is 10, and the live revision is 6, default to revision 6 (live) vs. revision 10 (latest)Current Behaviour?Defaults to latest revision -1 vs. latest revision .  For example, if the current revision is 10, and the live revision is 6, if currently defaults to revision 9 vs. revision 10(latest)

Description - When you are browsing a profile.  And click on the segment membership tab.  There's a list of segments there.  If you are using some integrations or have an external segment like from AAM for example.  Then you click on the segment and get an 'Oh Snap' page. Why is this feature important to you - I would like to be able to view these segments that are external to AEPHow would you like the feature to work - I would not expect an error page.  Either do nothing or link perhaps back to an external tool like AAM for example where I could view more details on the external segment.Current Behaviour - Getting an error page. PLATIR-8228 

Description - make an app that you can use phone instead key express shortcutWhy is this feature important to you - artist who are newbie with software dont need to remember shortkey or where the tool isHow would you like the feature to work - I have many idea to use it, I want to discuss directly by mail or else .Current Behaviour -

Description -  Since Libraries are just collections of changed resources, I want the option of merging two+ libraries together (similar to merging git branches) in dev and/or merge a library from dev into an existing staging library. Why is this feature important to you -  Graduating features from dev to stage while awaiting a production push is a pain.  Combining resource sets from two different dev libraries is a pain.How would you like the feature to work -  In publishing flow:Click the meatballs menu of a librarySelect "Merge in libraries"At this point, the libraries that can cleanly merge would swap out their own meatball menu buttons for checkboxes"Build" would be replaced with "Merge and Build"Check all libraries you want merged inClick "Merge and Build"A confirmation modal/warning dialog pops up, with the option to rename the new library.Click "Confirm"Libraries merge into one, then build.    Similarly, when submitting a dev library for approv

We have started a bit of work to move from DTM to Launch, and came across an issue when setting up the Adobe Analytics extension. When we are setting up the library and we select “manage library for me, we don’t see any of the reporting suites as an option to select.Eventually worked out that the you can type the reporting suite's name, but would be great if it was populated as it is on DTM (The select report suite icon is already there, but its blank when you clock on it) Thanks

I have a hard time believing there isn't already an idea post for this, but I did look. It would be wonderful if the Adobe Analytics extension could use the API to pull down variable/event names- something like this:This would help so much with making sure data element are aligning with the correct variables (and that variables are enabled, etc).

If you have a lot of rules, it would be great that you could enter either tags or put them in a certain folder in order to categorize them.

I often reference data elements in custom code through _satellite.getVar. I'll be in the middle of writing custom code and realize I need a value from a data element. Since I have a lot of data elements, I'll have to leave the rule entirely, find the DE I'm looking for, and copy the name. I would like to pipe data elements directly into custom code with a selector similar to the way variables are set. Selecting a data element would insert it into custom code through the %dataelement% syntax or satellite.getVar syntax

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 labels and/or folders similar to Google Tag Manager or DTM's feature but with a better UI.Each Rule and Data Element can be attributed to labels and the search will have filters to associate a combination of labels.Suggestion on User Interface:Clicking on Labels will do a filtered search based on the labels. Search can also look for multiple labels at a time. (example: Clicks + Facebook)

As a Launch API user, I would love to have place to attach my own metadata to a Launch resource when creating/updating it.  As an example, I might want to create a data element by posting to the standard endpoint,  POST /properties/:property_id/data_elementsIn addition to the normal, required parameters, I'd like to have a place to store my own metadata (perhaps a stringified JSON object up to some sane size limit). This would allow for any number of expanded uses. Thanks for the consideration. -Stew

At the moment the starting point for any new library is the 'upstream resources'.  However, we are finding situations where we want to use a library that is in development as the starting point.  The only way to achieve this seem to be to recreate the setup of the other library by manually selecting the same revisions - unfortunately, this is time consuming and prone to error 😞 Please can you consider introducing an option to 'copy' a library in development to use as the starting point for a new library?