Adobe Experience Platform

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.

The auto detection of download and exit links provided by the Adobe Analytics appMeasurement.js is useful.  However, it would make far more sense to me if these were events provided by the core extension. The benefit would be we would be able to:make the way these events are handled consistent with everything else we are doing (i.e. managing what happens through Launch rules rather than hacking stuff together using doPlugins)make these events available as a trigger event for other capabilities implemented through Adobe Launch (i.e. rather than just being an Adobe Analytics thing)

This is strictly a convenience/aesthetic thing, but it would be great to see the full name (or at least more of the name) of Data Elements (specifically in the Adobe Analytics extension in rules). Right now it's something like this: It would be nice for it to instead be like this:(for the record, I mocked that up by taking a guess and changing the class on that field from "coral-Textfield Field--short" to "coral-Textfield Field--long"- so the CSS for this already exists:))

It seems that disabling ClickMap in the Analytics Extension is not enough. You actually have to modify the AppMeasurement.js (which only works if you are not using the CDN): Stopping Activity Map Link TrackingPlease ad an option to really disable it through the UI.Duplicate of: Ability to Turn Off/On ActivityMap Module in Adobe Analytics Extension

There appears to be an issue using certain systems as sFTP hosts, and some systems that may be desirable or suitable to act as a host support REST APIs but not sFTP (e.g. Marketo). Please add the ability to define new host configurations via extensions so that extensions can be created to support various environments in which libraries could be hosted. No assumptions should be made with respect to how files should be sent to the host. For example, Marketo doesn't support real folders, so it's not possible to use Launch's native folder/file structure present in zipped libraries.

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.

1. The Revision Publish Status should be indicated in the compare revision.2. The Name of user made changes to Rule should be visible.3. JS Minification should not be applied for the codes loading in Sync - eg: if the rule is in Page Top or if we provide a custom library in Adobe the code gets minified - for difference checker this is not needed.

Over time the amount of various rules created in Launch can get out of hand and knowing what rules no longer run can be a daunting task. Even more frustrating are the rules transferred from DTM to Launch and needing to know what rules no longer apply. We know that in debug mode, a log churns out in the user's console that includes all the activities done by Launch _satellite code in real time. I feel the entire community of Launch users would love to see a reporting tool internal to a given Launch property that simply illustrates the usage count of rules that are current and rules that are deprecated. The date range of this reporting could be limited to thirty days. That should be plenty time for every given aspect of a site to be hit and know what rules are running. Any rules with zero fires could then be safely disabled and/or deleted. I feel this is a fairly straight forward ask. I do not feel this upgrade applies to data elements.

This is a little thing that would make a surprisingly big difference for me. Right now, in Launch I can only view 10 Rules or Data Elements at a time, with a "Next>" button to get to rules 11-20. There isn't a way to really now how many rules I have overall, which is also a very minor complaint.Ideally, I could define how many elements to see- 10, 20, 50, view all... An eternal scroll feature would be nice too. The real use case is this: I may not remember exactly the name of the rule I'm looking for (maybe someone else created it), so I want to be able to look through all the rules quickly.

When viewing the list of rules or data elements, it would be handy to have a new column for the rule event type, and for data elements the data element type i.e. cookie, custom code, JS variable etc.These could then be used in the search filter options to view, for example, all click based rules for a vertical.(Apologies if this has already been posted somewhere!)

It would be great if we can get some analytics on each Launch property.  I found myself asking these questions from time to time:- What are the Rules and Data Elements in production library that have not been fired or used for a long time.- What rules that are causing JS errors occasionally-How many Rules and Data Element in each property, and breakdown by their types-Who are the most active users in each property-Publishing frequency of each property...... With these data, we can keep each property clean and optimized, and just better governance overall. Best of all, these data will be available as a report suite in Analysis Workspace.   

Hello Team, Currently we're seeing the republished state notification in different property where the republished library not exist. So its better to show the notification where it belongs to.  For example. Look at the below screenshot.   The republished library AppD belongs to different property but I can able to see the republished notification in above property where AppD Fixes library not exist at all.  Looks like its a Launch UI bug - but if it's not considered while implementation so sharing the post as an IDEA. 

If we could include more verbose meta data in published libraries, no matter how old they are, that would be very helpful.  I had a customer recently and with them, reverse engineer all their Launch rules after the previous Launch “owner” left their company.  It took almost 2 months to trace down rule creators and email ghosts to figure out where everything came from.  I know we have the ability to Audit Events but its very clunky to jump to a different site section to review all this information.

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 websites (as described here). Awesome! Now we would like to do the same thing with our apps. Is there any equivalent way of getting the value of a constant data element configured in Launch via the SDK in apps? This would be a killer use case for us and safe us a lot of headache with our agencies. Best,Frederik

Please show the rule name when a user is viewing / editing a rule's components. It is very easy to lose your place. In DTM, everything was on the same page, with rule name and different components available there, so it was quick and easy to move thru. Now, everything requires a click, and each click results in a screen without the rulename visible. Example:Create or edit a rule.Click an event, condition, etc.The screen shows "Edit Rule" as the title - that's it. The only way to find the rule name if you forget (or want to verify) which one you opened is to click Discard or Save.IDEA: Use the "Edit Rule" space to provide a descriptive title (e.g., "<Rulename>: <Event/Condition/Action>") or at a minimum the first 60 characters of the rule name (e.g., "Edit Rule: <first 60 characters of rule>...") with ellipsis and title attribute to show rest on hover. For those of us interrupted often, this would save a lot of time of lost work, do-overs, fixes, when we're f

Linking Production Launch code to DTM is really helpful and a thoughtful feature. One less hassle to handle.If there is a possibility to enhance the linking functionality, we recommend to build the same linking functionality to Staging environment in Launch and DTM as we have it in production.This way, clients do not need to go through the hassle of deploying Launch embed code in their development environments for this migration. It would be an extra consistent approach to production, if we have the linking capability for 1 matching DTM and Launch testing environment. E.g. DTM Staging. Then, when the clients are ready to totally use the Launch embed code, we could deploy it to all environments including dev, staging and production.Meanwhile, as we currently do not have this feature, we use Fiddler, Charles, or Requestly to replace the DTM staging environment code with Launch embed code for testing. just FYI.Hope this helps. Thanks so much

Consider if one makes any edit to a Rule, DE, Extension, etc, but then undoes/removes the edit, they are still required to build a library and move it forward to Production with a "changeless" change. Request is for a mechanism to "revert to the last built state". In other words, "trash any modifications to the element that do not match at least Dev state". e.g. If I have a library built in Dev, I should not be able to "undo" the element as it is locked in the upstream, but if there is no Dev/Stage/etc build, and the current state of the element === the current published state, and there is no delta to send upstream, I shouldn't have to build and publish a new (empty) library to flush it out of the backlog. Replicate at the most basic level:Choose a currently published rule and edit the rule by renaming it (append an "!" to the end, for example)Edit the rule again and remove the "!", returning it to essentially it's previously unchanged state (i.e. it mirrors what Production

Migrated from Alpha--UX Flow of this page needs a little tweeking so the user knows where they are at all times and what they’ve completed.  Leave rule components where they are when creating conditions (events, actions, etc) so the user knows where they are at all times. Just expand and close the window.

It would be great if we could make the input field for the Evar/Prop string wider so you could see more characters. This would save time as it would reduce the number of times a user would have to spend moving the cursor further to the right and help make it easier to spot typos that are off screen when a user opens up the Set Variables component of a particular rule.  

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. 

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.  

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 in the development column. It would be nice if you could remove and add environments from development libraries in a similar way without having to individually open each library to remove or add environments. This change would save me a lot of time as I am have to open multiple libraries to remove and add the dev environment every day. 

In order to keep my list of evars and props in a sensible numeric order, it would be really great if you could rearrange the list. Or let us sort the list by number.

List Vars (s.list1, s.list2 and s.list3) are common enough variables (moreso than Hierarchy, I suspect) but right now we have to move to custom code to set them. I understand it gets trickier because of the list-y nature of them, but in most cases my Data Element is making the properly-delimited list I want, and I just need a way to reference it in my rules. Also, it's odd to have Transaction ID in the interface, but not purchaseID- they're very similar, and it would be nice to be able to set them side by side and not in custom code.