Adobe Experience Platform

Existing OOTB alerts are geared towards technical teams, audience management team does not have any visibility into audience quality. This feature is important because it provides an ability to the end users (Audience Management team) to proactively monitor the audience size variances before the campaign is impacted

Disclaimer: please do correct me if I am wrong! This feature request is just to my best knowledge and based on experience, and maybe this has been changed/fixed already.Looking at the release process, it just does not feel that way. Description - In Tags/Launch/whaever is en vogue these days, nowadays the "Approve & Publish to Production" does a direct deployment to PROD, leaving out STAGE, which may cause unwanted side effects for testers who regularily test functionality on a staging environment. It would be awesome if this step could implicitly do a STAGE deployemnt as well. Why is this feature important to you - When I get asked by a tester whether the functionality on STAGE is having all features from PROD (let aside new features in development), I can only shrug and say "well, ... it depends", since I do not know if other developers may have pushed recent features to PROD right away. How would you like the feature to work - either have an additional menu item l

Description - as mentioned in this thread, currently there seems to be no to_string function to case any other type into a string. "concat" seems to be a workaround, yet still I think this is a missing feature Why is this feature important to you - sometimes a schema field requires a string which will fail validation e.g., when a number is coming in. There seem to be a lot of other "to_xyz" type casting functions around, yet this may be one of the most essential ones. How would you like the feature to work - provide a new function "to_string" that converts any incoming type to its string representation Current Behaviour - no explicit function available. "concat" seems to work as a workaround

In Adobe Launch / Tags I want to have a full-text search for code and/or notes across all available properties to quickly identify if a specific code snippet / keyword is used anywhere. At the moment, search is only available per property.Having a full-text search across all properties would dramatically decrease the time required to find relevant rules/code. The full-text search should cover: - custom code- rule names- data elements- extensions- notes- library name- modified by- property name 

Description -When searching - Include the Rule Name in the results. (Or have the rule name as a tool tip) Why is this feature important to you -It makes certain searches much more usable. For example: Search on prop32 gives you the screenshot below. The results are not helpful.How would you like the feature to work -When searching .. Display the Rule Name -> With the Rule Component to distinguish multiple results. Could be via a tooltip when mouse over to keep the same layout. Or prefix the Rule name (which can be ugly due to space). Or use 2 lines in new formatting (header / description style)Current Behavior - See attached screen shot 

Description -Why is this feature important to you - Many times due to the bug in the code, APP can send erroneous hits to Adobe Analytics resulting in increase in server calls. As far as Native Mobile Apps are concerned, there are so many services they utilize in background and foreground. Some time due to coding issues, there may be erroneous hits to Adobe Analytics. It requires new release to fix the issue. But if Adobe Launch provides ability to block these server calls, it would be so helpful. I am currently facing issue where APP is sending background track action calls erroneously resulting in 30 Million hits a month.How would you like the feature to work - Please find the attached image. How about adding new event type suppress/disable  data along with modify and attach data.Current Behavior - It does not provide this feature.

Description -  I LOVE (yes, that's uppercase!) the Web SDK "Data Variable" Data Element Type in conjunction with the "Update variable" action. Especially with the new UI, it looks almost exactly like AppMeasurement, even better. What I am missing is a way to initialize the DE in a similar way an "XDM object" can be defined directly in the Data Element section, to set an initial state, and which you can build upon in your rules to temporarily enhance it. After the rules have completed, the initial state is reset. In my current setup with the ACDL (Adobe Client Data Layer), I need a standalone rule that is listening to "all events" and runs before any other ACDL triggered rule that further updates the variable, just to achieve this functionality. Or am I missing a step / functionality? As a workaround, I could likely also create a "custom code" DE instead, that defines the core data structure as JS object, and can then be merged with the variable part and the result used i

Description - Currently, Launch/Tags does not support a tagging nor folder functionality, especially in big projects leaving it to the implementer to use naming conventions to keep things tidy Why is this feature important to you - especially big projects easily get messy How would you like the feature to work - add a tagging + filtering and/or folder creation possibility, similar to what GTM provides Current Behaviour - nothing similar

Description -  Publishing Flow > [Development Environment] > Edit Library - Add a  "Update all/selected to latest Revision" button. Why is this feature important to you - To more easily update everything in an existing build. How would you like the feature to work - Within Publish flow, a given Development Environment build, where I have Data Elements, Rules, Extensions I have added to the build, where I can edit/save/build environment (The "Edit Library" view). I would like a "Update all/selected to latest Revision" button, where I can select all/multiselect all Resources currently listed and press the button and it automatically selects the latest revision.   In principle, this is similar to the "Add All Changed Resources" link at the bottom of the view, except only affect what is currently in the build or selected from checkboxes.  Current Behaviour - There is no such functionality, other than the "Add

Within Experience Cloud Data Collection (Launch), In the Publishing flow, I may have multiple Development Environment builds. I would like to have ability to either merge two existing builds to a single build. I imagine this to be on a Publishing flow level, with checkboxes on each build, and a "Merge" button at the top of the Development column. This would allow me to easily move everything from one or more builds into a single build. In addition, within a given build (where you can add/remove rules/DE's, Extensions, etc.) I would like to be able to select any/all existing items in the build and copy to another build. This would effectively me allow me to also do the first ask, but would still be nice to have both options.  .josh  

Currently, when you upgrade an extension, you get this notice:This has scared quite a few clients off of upgrading, because there really is NO going back. Especially for Adobe extensions, there is a strong need to be able to revert in case of issues (not to be snarky, but appMeasurement/VisitorID code updates have a history of finding major problems in the first month after release). Issues like Re: What are possible reasons why ClearVariable fails? make it clear why someone may want to move back. If you upgrade and you do see something break in staging during testing, you'd have no way to go back/compare/undo.

The new Update Variable action in the AEP Web SDK extension would be a lot more helpful if you could start with an existing XDM data element and update that, rather than having to start with an empty XDM object every time.In the scenario where you’ve got a lot of fields that you want to set on every event (e.g. domain, customer id, whatever), I’d want to start with an XDM object that’s already got all those fields populated, and then update that. Likewise, if I've got a lot of ecommerce events, I would want to start with an XDM object where the basic productListItems array is already defined, and then just update that with the relevant additional fields for the particular event (product view, basket add, etc)Currently, you have to start with an empty object in every rule, so you end up repeating a lot of work if you have rules that share a lot of fields.Another, perhaps better, option would be if you could just do the equivalent of the Merge Objects data element in rules. For example,

I'd like to be able to set up notification rules associated with when a library is submitted for approval, approved, and published. Launch admins would be responsible for setting up notification rules & settings.Notifications could be sent to an email group and/or to a Slack channel.

Description - Something that is in my opinion quite a waste of time is that with every save on a data element, rule or extension, it is closed and one has to reopen it. Why is this feature important to you - Efficiency, would save a lot of time when you are knee-deep in Launch and won't have to navigate back into the previous component. Works that way in every other desktop app How would you like the feature to work - Click "Save to library" without closing the element Current Behaviour - edit data element - Save to library -  where was I?! - ... - start filtering until found - open again - edit - save - back to where was I

Description - Today the Segmentation view has a table view of all segments created. The Name column is so small in widths that you cannot read most of the segment names and there is no way to change the column size. The only way to make the column size bigger is to hide other columns with the "Customize table" function. However, the system doesnt save your settings and you have to hide them every single time again.   Why is this feature important to you - This feature allows you to work with the segmentation list much more efficient. Currently when you have anything above 20 segments it is nearly impossible to efficiantly work with the list because there no folder functionality to group your segments and you can also not read the full segment names in the table view. Allowing for custom column widths will provide highe improvements in UX.   How would you like the feature to work - Allow drag-and-drop column resizing and have any hidden columns remain hidden upon page ref

Description - Our team is looking to have a view where we can see marketing channel overwrite capability in CJA similar to AA for initial adoption. We would love to be able to compare the overwrite with non-overwrite functionality so teams can leverage which view works best for them. Why is this feature important to you - Right now adoption will be harder due to the large discrepancies in some areas due to two different functionalities. How would you like the feature to work - It would have a way either through derived fields or a new feature to look at marketing channel overwrite or have the current marketing channel attribution in CJA. Current Behavior - Currently the channel overwrite is not available in CJA and creates discrepancies between both platforms. 

Description - AEP/Marketo Connector Good morning,  Use Case: Vanguard Marketo instance has FAS, IIG and Canada Data. The requirement is to send division specific Marketo data to its aligned AEP sandbox.  For example: - ABC Company XXX Marketo data to XXX AEP Sandbox. - ABC Company YYY Marketo data to YYY AEP Sandbox. - ABC Company ZZZ Marketo data to its own AEP sandbox.  Data in Marketo Engage does have the following identifiers: - Person ID: 2021111 - First Name and Last Name: John Wayne - Email: wjDuke@hollywood.com - Person Source: Adobe Audience Sync- Person Partition: 02.XXX Account authentication happens at the Marketo Sandbox (Prod/Dev) Munchkin ID Level. The AEP Marketo Source Connector does not allow to filter the data based on division-specific partitions in Marketo. Data needs to be partitioned before it hits the CDP to avoid overload. Please open an enhancement request for Vanguard to add filters in the Marketo Connector to facilitate partition spe

Description - with a PROD library URL, you can easily remove the .min.js extension to see the unminified library version, including every comment that was made, fully exposing all business logic.This should be disabled (on demand), or the unminified version should at least lie under a different ID Why is this feature important to you - exposing all business logic to the world is definitely not best practice How would you like the feature to work - have a checkbox that prevents the PROD unminified version of the library to be created in the asset cloud.Ideally, create a unique URL of the unminified version, that cannot be derived from the minified URL, yet to still be able to inspect this URL with external tools like the AEP Launch Inspector extension for Google Sheets. Current Behaviour - The unminified library, including all comments, is publically readable by removing the .min

Description - right now, the Web SDK send event action shows a checkbox that can be selected to do a "collect" request and improve the overall data quality.It would be amazing if this could be based on an evaluated Data Element that can be leveraged to conditionally enable this feature (without going the way through the on before event send callback) Why is this feature important to you - Right now, the setting has to be done statically which is too rigid How would you like the feature to work - allow using a data element that evaluate to true/false to determine whether this feature shall be toggled Current Behaviour - "stupid" checkbox that has to be preconfigured

Description - Currently, the ACDL does not support modifying the event object at a global scale, meaning adaptations or patches to the incoming data can be applied and work for every other ACDL-triggered that executes. One can push up an event listener to that specific ACDL event as custom code, that allows modifying the event and passing it into the rule actions by calling "trigger()". This is for instance the way AEM core components and Launch / Tags communicate together (a slightly overengineered approach that requires transformation of the incoming event data to make it actually usable inside of Launch, but is just my opionion). However, this works only on that single rule / event. Any additional rule that listens to the same ACDL event will not see these applied modifications. Why is this feature important to you - How often does it happen that for some reason data may be corrupted and a fix could be a small patch in Launch itself, rather than fixing the data proble

Description - I would be amazing if the revision comparison tool could toogle between "standard" side-by-side visualization (micro-changes, as is) into a more high level rule view.Meaning, the current version comparison tool helps to a certain distinct, but sometimes I would prefer if Tags could visualize the versions of the Rule, as a side by side view, but the same way the Rule look like when you regularily open them.   Why is this feature important to you - The holistic view on structure of the Rule helps me understand the functioning better than the minized view as is. How would you like the feature to work - Have a different view option in the side by side view that lets you toggle the views. In this split screen, it should be possible to see all custom code of that specific version like normal Current Behaviour - only the optimized/minimalisitic view exists Let me know what you think

Description - we would like to know how many attributes that have been ingested into AEP is actually in use for segment creation. Why is this feature important to you - it will let show the value of aep to our client and/or control the need of data ingestion How would you like the feature to work - we would like to consult the aggregated number of attributes that has been used in segment creation in one place in AEP. Additionally would be great to see the breakdown among the tables and  the breakdown among attributes activated into the destination and those that are not. Current Behaviour - we can access the segment one by one to extract this data, which is very time consuming

Description - We would like to enhance the filtering in the AEP UI. Why is this feature important to you - Having the ability to further drill down into filters via the UI, unlocks more capability for the users of AEP. How would you like the feature to work - Filter by audience on dataflow runs pages, adjust column sizing and filter for what is currently processing- Filter and sort by audience, start date, or end date on activation data page, and adjust column sizing. Current Behaviour - No current ability to do any of the above filtering in detail.

Description - Currently there is no way to specify the order of execution of extensions that are included in launch.js and run at the top of the page.Why is this feature important to you - We use a data monitoring technology that is deployed through Adobe Launch and needs to be the very first extension that runs when the library loads so it can properly monitor the data being collected on pages. As of right now it can't monitor all technologies consistently because the order of extension code is randomized at every publish and there is no way to specify that extension A should load before extension B.How would you like the feature to work - I would like to be able to specify either the exact processing order or be able to set an optional priority score (similar to rules) for extensions that are bundled with the core launch.js file.Current Behavior - Adobe Launch does not currently have a way to specify in the interface the priority of how extension code executes when the library initia

Description - Row level filtering from batch source connections Why is this feature important to you - Ability to filter out rows of data based upon specific filtering criteria. How would you like the feature to work - Utilize the flow service api to specify a row level filter parameter for all batch source connections. Current Behaviour - The ability to filter row level items is only available using Snowflake, Dynamics, Saleforce, and GBQ.   https://experienceleague.adobe.com/en/docs/experience-platform/sources/api-tutorials/filter