Adobe Experience Platform

Currently, debugger adds new events as columns to the right of existing event table, as they fire. Because this is often off-screen from the user (and the left-right scroll bar is only available at the very bottom of the columns), it makes finding the event you're looking for in a series very difficult: Current: events fire, then you scroll down, then scroll to the right until you think you're near the events you want, then scroll up and check, and repeat.Better: events fire, each appearing as a new column closest to the query param labels, and 'pushes' old events out to the right. That way, a user can simply watch the dimension row they care about as events pop in and find the event they're looking for immediately, no endless scrolling necessary.

As a user I expect to be able to see when specific Launch rules fired, in the proper sequence relative to data layer changes and other requests, within the context of the Event Timeline so that I can better understand where to look (which Launch rule) when I see a problem. 

When you multi select data elements you currently have the option to , enable, disable, copy, and delete the data elements.  Please can you consider adding an option to edit the 'duration' across multiple data element at a time? We recently had a situation where we wanted to alter the duration on 50+ element, and although we could filter the list to show them we had to go in to each individually to edit them which was very time consuming.

Within the custom code editor, if there is a large amount of code entered adobe appear to be dynamically loading the code as you scroll - so the whole block of code is never there in it's entirety.  This makes it very difficult to search the code as the browser search functionality does not work as expected. Please can you consider adding an option to search the custom code within the editor?

While a user is making changes to any rule or data element, autosave the changes periodically (e.g. every minute). If the user is logged out automatically – which erases all unsaved changes, the user can have the option of recovering from his last auto-saved state and pick up his work from there. The autosave does not need to create a new revision automatically. New revisions should still be made when the user saves manually.

We would find it incredibly useful and time saving to be able to move and copy actions between different rules in launch. I'd expect to access the feature by via a clicking with right mouse button on an action to reveal a menu with the options. Please can this be considered?

Add a checkbox to the Adobe Analytics extension to auto-add (enable) AppMeasurement_Module_Integrate (similar to how it's done for AAM and Activity Map).

In the previous Experience Cloud Debugger, I could easily detect/identify all Target Activities/Experiences firing on a page. That worked under mBox.js and at.js v1.x. It stopped working after we upgraded to at.js 2.3.x. I cannot find a similar feature anywhere in this new debugger. It had been so convenient to be able to see this information in the summary. We run multiple activities on a page with personalizations, recommendations and timed promos. Land on a page, hit the Experience Cloud Debugger and it was all right there on the summary screen in a matter of seconds. No need to generate a token and add it to the URL. It was all there in 1 click. Please restore this invaluable feature.

This is a small thing, but for folks spending a lot of time in Launch, would be really helpful. When I'm editing the configuration of something within a rule (action, condition, etc), it would be great if that screen included visibility into the name of the rule I'm currently working on. Right now, if I'm setting up a lot of rules all in a row, it's easy to get confused about which one I'm currently looking at. Nothing in the action configuration screen indicates which rule is potentially being altered by my changes on this screen:It would be great if there were some sort of breadcrumb or reminder:

When we link our adobe account with the debugger it has a refresh button that says. Attempt to pull in the latest information about the report suite including variables, settings, etc. I need this. The New debugger is better but this really stinks that i can't see the names of my variables in the debugger. Also pass those custom names into the Excel file. PLEASE. Thank you,-JGCollinson

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. 

I'd like to recommend that the page showing the list of rules page is vastly improved.The main problems to be addressed are:- Currently limited to show only 10 rules at a time- No ability to filter by rule attributes such as event type (with priority) & extension type & conditions- No ability to sort by any of the key attributes of a rule such as event type (with priority), extension type & conditionsTo summarise, the ability to sort, filter and even just visually see the rules in place for a property is mostly limited to using the names of the rules. This means we have to try and enforce consistent rule naming conventions in order to meet these needs - which can be difficult to achieve when multiple staff are using the tool.

We've recently moved over to using Adobe Launch which was on the whole a very positive experience. However, there is always room for improvement and I've kept a list of all the little niggles that we came across in the first month which I've provided (in no particular order) here below... Adobe Analytics Set Variable action - Add conditionality to individual variablesThis form/interface seems a little clunky and unsophisticated.  I'm guessing this is because it was done this way for DTM backwards compatibility?  It would be good if this was re-thought.  In particular, I'd like the ability to add conditionality to the setting of individual variables to stop us having to fall back to custom code. Add ability to enable/disable actions within a ruleIt would be useful for trouble shooting to be able to quickly knock out actions to see what affect it has.  Also in the same way as disabling rules, it would be good to be able to remove something from the curr

Currently, Adobe Launch allows 3 kinds of hosts: Akamai, managed by Adobe, and SFTP.For a CDN host, only Akamai and SFTP are viable options. (For SFTP, this assumes that the CDN replicates the scripts found in your SFTP destination.) So the only external CDN is really Akamai.Depending on one external CDN as a host is dangerous. If something happens at Akamai, it disables all Launch scripts hosted there. Also, clients may not necessarily want to use Akamai for whatever reasons.Idea: partner with other CDNs to allow hosting from them, e.g. Cloudflare.

I use the debugger mostly for Analytics and it would be preferable for me if the new network requests loaded on the left (front) rather then the right (end).  I am mostly looking for the latest request and it is a pain to have to go to the bottom of the window and scroll to the right to see the newest request.    Maybe make the sort/load direction an option? If that is not possible, maybe the left/right scroll bar could be at the top of the window as opposed to the bottom?

I find it annoying that the request automatically collapses if I leave the application for a moment. I'd like it to keep the state I've left it in, as long as the window remains open. 

I find the contrast too soft, specially when reading in the light mode. 

With the new v1.8.4 there is a change which I really don't like. To understand  the change, first have a look at how it looks in the old v1.8.3: As you can see there are all the default variables easy to access. I understand that in most cases all the fields remain empty and it is a lot of place ... that might be the reason why the change was made in v1.8.4, see here:All the default variables are now hidden behind a simple checkbox - check it and see the additional fields as above. What's bad?There are 2 points that I don't like about thatIf you have the settings closed, you have no indication that you maybe have filled in some of the fields - so easy to forget about a single field that has a value. just had sort of nightmare while debugging an issue...the action remembers the setting of the view in the UI - good. but this setting is written in the final launch library code! it adds an additional string to the action with a boolean value for "showAdditionalSettings".Idea

I'm trying to see the differences between two Platform requests. The meaty part of the Platform request, which I control as an implementer is the "events" area of the post body. This is where all of my custom name/value pairs I am sending are contained. In the current formatting of the Debugger, it's nearly impossible to compare two requests side by side because this info is displayed in a tiny cell. You would have to click one cell, copy the JSON object then click the other cell and copy the JSON object and then compare the two using some other tool. Please make it easier to see the differences in the request between these two fields. I suspect this is a challenging task in all of the tools that have switched to sending data in the post request body (e.g. at.js 2.x) instead of as query string parameters.  

Currently, there's no option to collect the value of a Product Syntax in a Data Elements for Adobe Launch Mobile property using the Context Data Key. Would it be possible to add the possibility to capture Product Syntax in a Data Element? Thank you

Currently, to add eVars and prop in a product syntax we need to use the eVar slot :cdata.put("&&products", ";Shoes;1;69.95;eVar1=Merchandising;eVar2=TEST,;Socks;10;29.99;eVar1=Merchandising;eVar2=TEST2"); Would it be possible to use the variable name that we have in Adobe Mobile Services? For example, if eVar1 is attributed to "productCategory", we'd have :cdata.put("&&products", ";Shoes;1;69.95;productCategory=Merchandising;eVar2=TEST,;Socks;10;29.99;productCategory=Merchandising;eVar2=TEST2"); For cases that we have multiples eVar and prop, it's harder dor developper to understand what they are pushing. Thank you

1) Within a given Rule, a note can be added on a Component level (e.g. an Action view), or on a Rule level.  Currently, there is no way to know there are any notes on a given Component, unless you open the Component view. I like being able to also write notes on a Component level, but I don't like that I cannot see an overview of all notes within the Rule, in one place. I would like to see all notes listed in the main Rule overview, with prefixes or section headers signifying which Component they belong to. 2) Within the Publish flow, when you build (e.g. a Dev) environment, it is currently not possible to add a note AND perform the Save action at the same time. You must first Save the build (or Save+Build), which takes you out of the view, and then go back to the Build view, and then add your Note.  This seems like an unnecessary and annoying extra step. I would like to be able to add a Note at the same time I create/update the build, and have it saved at the same

When the implementation has 2+ dimensions with the same name, it's not possible to determine which one is used in the Segment. The solution would be to display the (i) icon on mouse hover similar to how it happens in the left rail (the appearing popup has a reference to the variable).

Can you add an option to export the mobile code snippets on Adobe Experience Platform Launch?Often our mobile apps are developed by third party, and we do not provide access to Adobe Launch, so we have to copy and paste the code snippet out of the Adobe Launch.  It would be nice if we can export the whole thing to a text file or pdf file.  Thank you!

It would add a very useful additional layer of flexibility if the Adobe Analytics extension allowed you to add a condition against the variable you were setting (dare I say it, similar to processing rules! &#x1f605) At the moment if I want to conditionally set a variable (e.g. an eVar) I either have to have a completely separate rule or I have to use custom code within the action both of which are a compromise for different reasons.