Adobe Experience Platform

Description - For a system like Adobe Experience Cloud Experience Platform Dynamic Data Collection Launch, by Adobe Tags, it is very important to provide a clear view on what has been changed when and by whom. This information is available already through the amazing Audit Event tab. However, it can be tricky to figure out what has changed due to the information being presented in a different place from the resource in question, like a Rule's Action. For example, looking for information about who changed a Rule's Action is difficult, because the displayed information would only work if every Action has a unique name: To help with that, I would like to propose the following enhancements: In the view above, always include the ID of the resource and allow to search for it Make the results clickable, so users can jump directly to the Resource in question Display Audit Events in the context of the Resource they belong to. For example, add another menu item below the existi

Description - Callbacks provide a tremendously helpful way to integrate Adobe Experience Cloud Experience Platform Dynamic Data Collection Launch, by Adobe Tags with other systems, like ticketing or messaging tools. However, the fact that we need to use an API to set them up means not many customers a) know about the feature or b) use it to its full potential. To help with this, please provide a way to create, manage, and delete Callbacks from the Tags interface. Why is this feature important to you - Because Callbacks have a lot of value, so everybody should use it a lot (me included) How would you like the feature to work - Add the option to create, manage, and delete Callbacks from the Tags interface within a Property, maybe directly in the left-hand menu? Current Behaviour - A lot of 🩸💦 and 😭

Description -At the moment rules are triggered in a sequence determined by the rule order number.  However, each rule executes asynchronously meaning that rules with a higher priority may finish after rules with a lower priority.   This can cause issues where there is a dependency between rules.  Why is this feature important to you -We are experiencing issues where there are dependencies between rules.  They are hard to spot because the are intermittent and are difficult to resolve due the the asynchronous execution.  How would you like the feature to work -I would like to be able to force rules set to different order numbers to wait for other rules. This would be similar to the "wait then" behaviour of actions within a rule. 

Description - A simple query takes an unexpectedly long time to complete. See examples below. This indicates that AEP Queries is just not ready for widespread, "production" use, really. Why is this feature important to you - 99% of writing a correct, working query is figuring out the way to write it. This requires a lot of iteration from a simple "SELECT * FROM table" to the final query. Querying speed is especially important here, so as to help the analyst improve upon the query until the final one is obtained. Any time spent waiting for a query to complete is time that could have been used to more productive use. Without this speed increase, Adobe can expect all of its AEP customers to flock to Google BigQuery and never look back. How would you like the feature to work - Improve the querying engine's processing from minutes to milliseconds. Current Behaviour - See examples. SELECT * FROM table LIMIT 10;  --> 2.5 minutes SELECT * FROM table WHERE table.eventType = "something"

Description - Strangely, there is no vertical scrollbar in the data governance table. Why is this feature important to you - The table almost always has a loooooooong list of rows. Scrolling with a scrollwheel is ridiculous (and noisy!). Scrolling with a trackpad is likewise ridiculous. A scrollbar allows the user to control how fast/slow to scroll, allowing for easier manual eyeballing of the row items. How would you like the feature to work - Show a vertical scrollbar in the data governance table. Current Behaviour - There is no vertical scrollbar in the data governance table.  

Description - It looks like the dataset preview overlay has been designed for large monitors and/or large resolutions. However, on a standard laptop screen, the preview overlay's table needs a lot of scrolling, and that causes the table's headers to be gone from the view. Why is this feature important to you - There is a lot of unnecessary scrolling to identify the column names (need to scroll up and down repeatedly). How would you like the feature to work - Freeze the table headers to the top of the table, so that scrolling down still allows the column headers to be seen. Current Behaviour - see screenshots:      

Description - Schemas that are in use by datasets cannot be edited directly. This contradicts https://experienceleague.adobe.com/docs/experience-platform/xdm/schema/composition.html?lang=en#evolution . Why is this feature important to you - Descriptions add human-readable metadata about what the schema is. While the schema might not change, including its name, there could be some wordings in the descriptions that need to be updated from time to time. How would you like the feature to work - Allow editing of descriptions directly, as expected. Current Behaviour - Schema descriptions cannot be updated without temporarily changing the schema name too, i.e. Edit the schema. Change the schema's name. Update the schema's description. Save the schema. Edit that same schema. Revert the schema's name to its original name. Save the schema. Notice the additional extra steps needed.

Being able to quickly copy a templated launch property would allow for quick standups of scripts ready to launch analytics, experience cloud id service, target, ads, facebook pixels or all of the above. Our use case comes from wanting to get a standardized, unique script so we can quickly add adobe analytics to a number of websites. This is extremely helpful for clients/agencies managing many (100+) websites and report suites.

Description - Within CJA, the Platform Dataset ID can be selected in Dimensions, but the not the Dataset Description Why is this feature important to you - Having the Dataset Description helps a lot for our Analysis instead of IDs. How would you like the feature to work - Display Platform Dataset Description within CJACurrent Behaviour - Only Platform Dataset ID is available in CJA Dimensions

Description -Why is this feature important to you - On Daily basis we are moving 4 Extracts(Transaction,store,customer,Product) to Adobe storage. While sending extracts to Adobe storage,  we used to connect to Adobe storage manually and Delete those extracts once Archived to refresh with the new set of extracts(files). Since it is happening on daily basis and that to manually we have requested you for any possibility of Archiving files once Ingestion is completed rather deleting it manually by our team.Adobe Azure storage path-  https://4fbd3ac440stg.blob.core.windows.net/cdp Extracts name-Customer_Profile.csvProduct_Lookup.csvStore_Lookup.csvTransaction.csv ingesting data happening at 3am(BST) and 3pm(BST).How would you like the feature to work - it should work like once your ingestion is completed files should be moved to Archive folder (i mean once ingestion is completed files should be deleted after moving to Archive folder)Current Behaviour - We are deleti

Adobe DTM has one very useful feature - ability to search properties by ID. Since such ID is part of the container script, it helps locate the correct environment withing DTM if only the web site URL is known. Unfortunately Adobe Launch does not offer this option, I can only search properties by name. In my case, I have hundreds of properties, and often names are not always known to me, therefore locating correct Adobe Launch property becomes a challenge. I would like to have an ability to search by property ID in addition to searching by names. I hope Adobe team will make this useful DTM feature available in Adobe Launch.

Description - Parse JSON values into their own table rows in the network requests view, so that the values within the JSON can be more easily inspected/verified in downloaded Excel files.Why is this feature important to you - Verifying values within the JSON is very important to verify correct tracking, instead of seeing the long JSON string.How would you like the feature to work - The debugger automatically parses JSON values into their own (nested) rows in the network requests table.Current Behaviour - JSON values are one long string value, so in the downloaded Excel file, it is difficult to read the individual values properly without additional manual parsing. 

i would like to be able to turn development mode on and off in Launch Tags Client Side. i cannot copy data elements, rules from one property to another. For context, the property with it on, has never done any extension development (but might have wanted to at some point). The property i want to move it to, has it off.  If there is no custom extension development, why cant it be moved ? why was it designed in such a way that simple things like data elements cannot be copied over or rules (things that have nothing to do with Extensions).  

Currently if I select a data element from the pool it is just copies to the text field surrounded with %%. If for some reason I change my data element, I need to find all rules where I used it manuall and change it. If the element would be linked to the rule, a change in the data element name would be applied to all rules. One additional gain would be to be able to see where a data element is actually used.To be able to see where something is used would also be a good feature for events, conditions, exceptions and actions based on the suggestion here: Reuse events, conditions, exceptions in rulesCommunity Manager EditThis idea is also requested by the following ideasAutomatically Update Names of Data Elements Used in Launch Rules Automatically Update Names of Data Elements Used in DTM Rules

It would be good to have an option related to the rules' events to fire the rule only once per page. This way, even if you have multiple events or one event that can be dispatched multiples times on a page, it would be possible to automatically block the rule from fire more than once.

Description - Usage logs in CJAWhy is this feature important to you -  These logs would help find the what kind of changes have been made to connections similar to Adobe analytics Usage logs.How would you like the feature to work - It would be great if these usage logs are available in the UI of CJACurrent Behaviour - Though API to get these logs is already available, it would be great if it is a feature in the UI as well

Considering the move from Object-C to Swift, it is vital to prioritize the support for tvOS tvOS support on AEPCore, AEPIdentity, AEPLifecycle, AEPEdge and  AEPAssurance  https://aep-sdks.gitbook.io/docs/resources/upgrading-to-aep/current-sdk-versions#ios-swift 

Description -More and more website are being built using Single-Page Application (SPA) architecture. With a SPA website, when a user moves between screens it does not cause a full refresh of the page.  This causes Data Elements that have a Storage Duration set to "page view" to live beyond what the user experiences as a page view as these data elements require a full refresh from them to be cleared. Why is this important -Within SPAs, data elements set to "page view" duration can actually live for the whole session, meaning there is little difference between between the "page view" and "session" duration. This has the potential to cause odd results/confusion (e.g. it may not behave like someone selecting "page view" might expect). How would you like the feature to work -The simplest solution may be for Adobe to display a notification/warning about SPAs near the storage duration field when someone selects "page view".  The notification could directing people to use t

Description:Add indicator that track and report on rule execution metricsCurrent Behavior: Currently when Launch rules get fired the tool does not keep track of number of times and duration. Why is this feature important to you?It will be valuable if the marketer have this data on the spot with in Launch, that will save time and add efficiency. How would you like the feature to work?The feature request is to add indicator that track and report on rule execution metrics, so the marketer can use the information to monitor and manage the tag performance.  

Description: Add a configuration file export option at Launch property levelCurrent Behavior: Currently as we mage rules with in Adobe Experience Platform Data Collection – Launch. We do not have option to export the configurations of rules, data elements in CSV or any other format.Why is this feature important to you?The export option will provide value in efficiently analyzing large sets of configurations.How would you like the feature to work?The feature request is to add a configuration file export option at Launch property level, so the marketer can get quickly inventory lists along with the configurations in CSV format.

Description - Currently in AEP we have only schemas migration API from one sandbox to another. So, for moving my other configurations like source connectors, Dataset, Identity services etc. We need to reconfigure them again other sandboxes which eats lots of time and hamper schedule by a significant margin.Why is this feature important to you - In order to quickly develop and test in Sandbox and move to Production for quick deployment.How would you like the feature to work - if we configure every entity within one AEP sandbox and test it , post its working as per business logic. We can go ahead and create a JSON package export for that entity(like source connectors or identity services configuration etc) and we can quickly import that JSON package in other sandboxes and test in current sandbox and go for deployment. Current Behavior - Currently there is no facility except schemas in AEP. We can surely work on such feature which can quickly deploy segments and other services config

Description - AA debugger has recently introduced a new behavior where it creates internal redirects for every server call. It's unclear why it needs to do so. A lot of similar debuggers out there don't affect the network tab logging. This has to be either fixed to not disturb the Network tab logs, or add an option to completely disable the AA debugger. Why is this feature important to you - While we use AEP to replace the Launch/DTM libs, its AA debugger is not comfortable to use for more technical people. We prefer to have our logs printed to the console, so we use something like the AA debugger Chrome extension. When the AEP debugger creates phantom AA hits, other debuggers report them as real, complicating the process for us. How would you like the feature to work - It should either stop creating hits in the Network tab, or have an option to completely disable its AA debugger with the network hits interception feature in the debugger. Current Behaviour - No way to di

Description:Connect to SFTP source and read a GPG encrypted file to ingest into Adobe Experience Platform Why is this feature important to you:Clients averse to using cloud data storage for PII data force data transmission via SFTP with encrypted data files.  These processes may be legacy applications that are hoard to change.  Data privacy and security policies are hard to change.  This seems like such a basic capability - that is available in Campaign - why not AEP? How would you like the feature to work :UI/API to connect to sourceUI/API to open encrypted file with key pair with option to translate csv to JSONRead the data stream from the opened fileReturn a JSON object with decrypted data Current Behaviour -None.  Feature available in campaign is not available in AEP. Current process would be to decrypt the file on the SFTP server then ingest into AEP, which is not compliant with security policies.

Its very difficult to understand if a rule is succeeding or failing based in Debugger Edge logs. It does not seem to chronologically display or display in association with starting, confirmation or return values. there are redundant things displayed and hard to find what you need. I think all that's needed is, grouped by Rule- Rule Name- Did it pass for fail- what data was available to the rule- what data was sent to a platform  

Segments created in the UI and API cannot be edited other than the original source. Facilitate management of Segments, bulk creation and allow adjustments in the UI.