Adobe Experience Platform

In DTM it didn't matter which order you put in the s.props once you saved they resorted into order. So for example you could enter them in s.prop1, s.prop23, s.prop2, s.prop11.  And when you saved and reloaded the rule it would sort them s.prop1, s.prop2, s.prop11, s.prop23.   Which is really handy when you are scanning for something.  Launch doesn't do this so as the implementation changes and grows you need to manually reorder variables (unless I have missed something)

I know that this was basically impossible to do in DTM, but I'm wondering how feasible it would be to allow the property administrator to configure Launch's primary object from _satellite to another string so that multiple properties could coexist on the same page. My reason for wanting this is to allow a configuration where two or more Launch instances are deployed on the same page.I have come across scenarios in the past when this would be absolutely ideal (especially if both were driven from the same event-centric data layer).Example 1: A holding company wishes to collect analytics data globally on all of its brand websites.  The individual brands also wish to collect analytics data but don't want to be bound by the SDR of the holding company.   Having multiple Launch properties on the page would allow this. Example 2: A solution is designed for a website that is fully driven from data layer events but the organization's IT staff will not be able to deliver the application modificat

It would be useful to have some tiered access control on Launch rules (and perhaps data elements). I would like to be able to create a baseline set of rules that can be viewed by others but not changed. The scenario for this is an environment where Launch is triggered by various application events such as "Page Loaded", and "Product Viewed". There would be book-end rules that are created for each event, say "Product Viewed - 10" and "Product Viewed - 90".  These rules would be triggered by the same custom event, but would be set up with event order of 10 and 90 so that one runs early and the other runs late. The early rule that runs on 10 would have an AA Action of Clear Variables, followed by an AA Action of Set Variables. The late rule that runs on 90 would have an AA Action of Send Beacon. These book-end rules might be created via the Launch API and would provide the basic tagging needed by this and many other properties. If a person wanted to extend this solution with additional AA

This idea comes from a question asked on the community:The community member would like to see Session Storage added as a Data Element option in addition to Local Storage.

Ideally Launch would include the same functionality to mimic the _satellite.dtmRuleStackArray functionality that is in DTM.  Doing so provides a great audit mechanism, as well as a way to perform a gap analysis for rules that are not in use.

We should have the ability to control default lifecycle metrics behavior in the Mobile SDK configuration. This would include toggling whether or not events such as app launches automatically trigger lifecycle tracking, so that they might be manually sent or disabled entirely.

Since we have multiple environments wherein multiple rules, data elements and even entire properties can be tested. What if we create such features to schedule the rule publish from the test to dev environment and if we are successful in this migration then to prod environment.At times we test the things in stage in live websites by switching the library to point to stage for a rule or data element. When we know that the testing is positive for an update then we can schedule the publish for that rule/data element and property to next day or near to go-live dates.

I can create a Data Element of type javascript variable, or custom code, that references/returns an array.  However, Launch (and DTM) doesn't have any functionality baked in to take advantage of this.  Instead, it ultimately expects a string value returned (and type casts the value to string when parsing %data_element% syntax references to enforce it).  Meanwhile, you have for example Adobe Analytics hier variable, which would benefit from being able to reference an array.  As of right now you just provide 4 fields and i can reference 4 separate data elements (or hardcode 4 separate values).  But in practice, I can have more than 4 levels in a hier variable.  I think it should be a pretty easy update to the Launch interface to just have the hier[n] variables be a single field to reference a data element that returns an array, and a field to specify a delimiter (already implemented), and then under the hood, check if the returned data element value is an array and then join by delimiter

Adobe Launch is used to write code.  It should have the ability to store that code in a standard software repository (Git).  This should include at least custom code, but would preferably also include files representing non-custom code (preferably in JSON format).  Nearly everything you can do with the GUI you should be able to do by cloning the repository, editing files, committing changes, and pushing them to the remote repository where they can be reviewed and deployed.  Users should also have the ability to provide an external repository location to be used by Launch on a per-web-property basis.IDE: Though Adobe Launch does a great job of hiding complexity, it is really a sort of IDE (Integrated Development Environment).  I am recommending a series of improvements, all labelled "IDE", that re-envision the product based on this fact.

Are there any plans to extend the Custom Event portion of Event Type in Rules? I would like to eventually see the ability to add events to things other than elements on the page, particularly the window and/or document.

Add support to easily access the DTM rule name which is currently triggered.This can be used for monitoring purposes. For example, you could populate an s.prop with the rule name and create a simple Analytics Workspace to monitor that rules are firing as expected over time. This would also mean you could use anomaly detection.(This was inspired by Jim's "Tag Fire Count" idea)

I should always be able to conditionally load extensions on a page.  For example, I do not want Target to fire on every page.  The extension gives me no way to conditionally define this.  So instead I end up having to control it with a rule.  The inability to do this makes many extensions useless to me.

I can disable a data element, but can I delete one?If not, would like the ability to completely remove it from the UI.

When setting Adobe Analytics variables within an action several levels of the hierarchy are expanded by default. I often find myself removing it entirely just to clean up the workspace. It would be nice if hierarchy was collapsed by default and could be added if needed.

If a rule or data element fails I would like to see more robust error messaging in the build screen, e.g. which rule or data element failed rather than a generic failed message.

Hi,the idea is basically very simple I want to call a particular rule in the actions section:This can be very helpful for SPAs because I can e.g. define the Page Name or page specific events in the triggered rule but don't need to include all variables I typically have in a Page Load. The second Page Load Rule then appends all evars, props and events which are standard on every page and sends the beacon. Hence I only have one central rule for all Page Loads.Currently I use this with a custom script and just call _satellite.track() but of course as a build in feature this would be easier to handle.

We LOVE the idea of libraries.  The ability to create one, add related rules to it and then promote them as a group is a big plus for Launch.I envision creating libraries named after the JIRA story that requests the work.  Again, a huge step  in being able to track requirements through implementation.It would be great if there was a comment field available at the library level similar to what we have for rules.  That way, more detailed information about what is in the library can be added.  Something as simple as a link to the JIRA story or more complex like a full explanation of what work is being done there.  Think of it like how you add a comment to a PR in Git.

Today, the Access controls are not that granular with respect to Mobile services UI and we cannot create custom roles and assigned access to certain features only. either you have to be Admin or not. I have a specific scenario,We want our product managers/Sales/Marketing teams to have access to send Push messages to App users, we cannot have them do that unless they are admins. But Admin has full control and we want to limit that. Our idea is to for Adobe to implement Role based Access Control, where Admin can create custom roles and assign user to that role/ User Group.

Launch (and DTM) Data Element Change event type polls the data element every 1000ms (1s).  I would like a field added to specify how frequently to poll.  Add a warning about potential performance considerations, similar to what you already display about timing, but give me the ability to specify this value!.josh

It would be really useful to be able to be able to store a description against each data element and each rule to explain what it is.In Adobe Analytics, the ability to add descriptions to components has become common place so I was a little surprised not to have the ability here.From a workflow/governance/documentation perspective, it would really helpful to be able to store this information.Please can this be considered?

In Adobe Analytics it is possible to prevent users from logging in outside of our corporate IP address range.However, there is no equivalent for Launch; yet the security implications of an unauthorised access to Launch is much greater.Obviously, we could go down the route of setting up single sign on for the whole of the Experience Cloud but this is not an easy process and our requirement is only around Launch where the risks are much higher (i.e. the ability to inject code into our website).Please can you consider providing an easy way to lock access to a given IP address range?

Current choices are:AkamaiSFTPI would like to see the following added:FTP Library DownloadGIT/SVN

Currently, the following roles are available:developapprovepublishI want to be able to stop people approving code that they have developed themselves.  However, our team is not big enough that we can afford to have mutually exclusive groups of developers and testers.  Therefore, I have to give 'develop' and 'approve' rights to everyone, which mean users can effectively mark their own homework.What I would like is an additional 'approve' permission which only allows a user to 'approve' libraries submitted for approval by other users  i.e. they can 'approve' other peoples code for publishing, but not their own.

I feel like the Rules tab could use a lot more love. Right now the Rules tab is pretty bare. It just shows the rule Name, Last Modifed date, and Status. And (multi) select functionality just lets me bulk enable/disable rules. Some things I would like to see added to this tab:For the rule rows:The rule priority (Order) #.   Would make it easier to figure out which rules are popping first. The Event Type(s)  for a given rule. Would make it easier to figure out which rules are popping on page top, etc. Extension(s) used in the rule.  Would make it easier to find all rules that e.g. pop AA varsCondition Type > Date Range if used in the rule. This would make it a lot easier to keep track of random marketing pixels set to expire, to find and remove themGeneral Tab functionality:Ability to sort  by things such as rule priority (Order), Event Type, etc.  Ability to search/filter (e.g. search by rule name, filter for all rules that include foo extension, etc. )Ability to change the rule prio

Right now adding resources when building a library is very cumbersome, depending on the situation. We can easily add any recently changed resource with that available option, or we can add a resource manually one at a time.I'd like to see an "Add all resources" regardless of whether it's recently changed or not, which would just add every resource instance using the latest revision.I think it would also be great to have a way to add multiple resources manually without the following back and forth process:Select Add a resourceChange option from "Changed" to "All" to make sure all resources show upSearch through the list to find the resource you want to addSelect revisionClick "Select this revision"Add a resource area closes (why?)Repeat from step 1There's no way (that I know of) to say, select multiple resources via some multi-select/checkbox system that could also just automatically select the latest revision (regardless of recent changes or not) to add all at once.