Adobe Experience Platform

Description - I want to create additional rules for marketing channels but it says rule 4. Even if i create one more it says Rule4 only. It might be a bug. How can I reference these if names are same.Why is this feature important to you -Even if i create one more it says Rule4 only. It might be a bug. How can I reference these if names are same.How would you like the feature to work - add edit option to rename the ruleCurrent Behaviour - no edit option

Description -In Adobe Experience Platform's Event Forwarding, there is a requirement that OAuth2 tokens must have a minimum expiration time of 8 hours. However, the system we use internally for authentication only allows tokens with a maximum expiration time of 1 hour. This creates a compatibility issue, as we are unable to use our tokens with Event Forwarding due to this restriction. Why is this feature important to you -This limitation prevents us from integrating our internal authentication system with Adobe Event Forwarding, which restricts our ability to automate and scale our processes. Removing this requirement would enable us to fully utilize Event Forwarding in our workflows. How would you like the feature to work -We would like Adobe Experience Platform Event Forwarding to support OAuth2 tokens with expiration times shorter than 8 hours. Ideally, there should be no minimum expiration requirement, or at least support for tokens with a 1 hour expiration, which is stan

When you click to create a segment, you get a popup with "compose audience" and "build rule" options, with "compose" being the default pre-checked option. This makes no sense! Composed audiences is a limited feature, designed for advanced users, for specific use cases.I bet if you look at analytics, 99.9% of the users go to "build rule".I actually thought Adobe would fix this a couple of weeks after "compose audience" being released. This annoys me and is bad UX with a simple fix. Please Adobe, make "Build Rule" the default option.

Testing AEP mobile SDK analytics with a focus on which events are firing in the beacon.When trying to find the custom event# to validate the custom events are firing correctly, its extremely difficult to see them in amongst all the reserved evars. It would be extremely beneficial if we had to have all of these events shown then at least they could be alphabetically listed to be easier to read.

DescriptionCurrently, in Adobe Experience Platform, the creation and editing of datatypes are restricted to the method by which they were created. If a datatype is created via the API, it can only be edited using the API. Similarly, if a datatype is created via the UI, it can only be edited through the UI. This limitation creates an inconsistent and fragmented user experience. The requested feature is to enable cross-platform creation and editing, allowing datatypes created via the API to be editable within the UI, and vice versa. Why is this feature important to youThis feature is crucial for maintaining a seamless workflow between the API and the UI. Different team members and projects may have varying preferences or requirements for using the API or the UI. Restricting editing to the creation method adds unnecessary complexity, slows down development processes, and increases the risk of errors. A unified editing experience would enhance productivity, improve collaboration, and

Currently, multiple conditions seem to always take an "AND" operator- for anything "OR", I go to custom code. It would be very helpful to be able to use "OR" conditions.For instance, if I needed to have a condition like "if the pagename is 'home' OR the page type is "product details", I would have to resort to a custom code condition, or creating multiple rules.

Description These days, the AEP sources data prep UI for calculated fields is lacking basic functions to (easily) transform incoming data structures like arrays through a computed field into a target structure of any kind which makes it really cumbersome to work with. Also, asterisk syntax is only supported in standard mapping fields.   Why is this feature important to you Well, the source data often does not match the XDM schema data and has to be brought into the right format. The provided functions are insufficient. The destinations data prep, however, seems to contain more functions to transform hierarchies.   How would you like the feature to work Let's start with something trivial like looping over arrays to transform their data.   Destinations Data Prep: transformArray([5, 6, 7], x -> x + 1) Sources Data Prep: ???   Current Behaviour - It seems impossible or at least extremely cumbersome to do even minimal transformations on any array or object data on

Description - When adding data to a dataflow, on tha Select Data Step, when we Uploade a Json that is bigger than what the first seen screen can hold, there is no scroll bar to look/verify the rest of the json.  Why is this feature important to you - Because it supposed to be there, is more like a bug than a improvement. How would you like the feature to work - It must have a scrool bar, that simple. Current Behaviour - There is no scrool bar.  

To be able to delete batches that is older than 30 days.Today those batches are not available in the view.

Today it is only possible to include the audience status. Including 'Segment name' and 'Segment ID' is useful directly in the .csv shared, if the receiver platform can't read off of the file naming, but can only evaluate input from the file itself.

Enable the option of configuring a source/destination account after it have been configured, such as changing and/or at least viewing the bucket name, folder path, fily type, include manifest toggle and compression format which is a part of the wizard when setting up the account, instead of having to create a new one.

Let me know your thoughts on cross platform / App tracking I have developed a Cross-Domain & Mobile User Tracking Platform 🧠📱💻In today's fragmented digital world, understanding our users across websites, apps, and devices is no longer a luxury—it's a necessity.That’s why I’m excited to share what I’ve built:👉 A privacy-aware, cross-domain + mobile user tracking platform Designed for marketing teams, data analysts, and tech-driven businesses that want a unified view of their users — no matter where they come from.🔍 What it does: ✅ Tracks users across multiple domains and platforms✅ Links mobile app sessions with web visits in real time✅ Offers a beautiful, customizable dashboard with rich filters, analytics, and export options✅ Supports GDPR-compliant tracking and real-time logs📊 Whether you're running multiple brands, client websites, or want to boost your personalization strategy — this platform puts identity resolut

Currently only unauthenticated calls can receive the location hint as a parameter on the call

Description - For all datasets, allow the ability to force lowercase all or certain fields. Why is this feature important to you - Currently, if the casing in matching keys doesn't match exactly, enhancement data from lookup and profile datasets isn't available in CJA. How would you like the feature to work - A toggle to force lowercase all fields in a dataset.  Checkboxes to force lowercase certain fields Current Behavior - Attributes can be forced lowercase once ingested via data view component settings.  However, this isn't possible before setting matching keys for lookup/profile datasets.

Description - It would be great if Adobe could give recommended schema-level governance labels on their own standard field groups to speed up labelling.   Why is this feature important to you - Applying field labels to the schema fields is a process that is new to many clients, especially to people from legal departments. With Adobe's recommendation to stick with standard field groups as much as possible, it would be amazing to give recommended labels for the fields contained in these field groups. That would surely make many people's live a lot easier and reduce the room for errors.   How would you like the feature to work - upon selecting a field in the Labels tab, show additional information like "often labelled as"   Current Behaviour - Every field has to be labelled, and no recommended label is given which is a cumbersome process.

Description - Introduction to HTML: Understanding the Basics of Web Development is a beginner-friendly tutorial designed to help you grasp the core concepts of HTML. This tutorial covers essential topics such as HTML structure, elements, attributes, and best practices. Whether you're starting your web development journey or need a refresher, this guide will provide you with a strong foundation to build and structure web pages effectively. By the end of this tutorial, you'll be confident in creating basic web pages and understanding how HTML interacts with other web technologies.Why is this feature important to you - This feature is essential because HTML is the backbone of web development, and understanding it helps in creating structured and accessible web pages.How would you like the feature to work - The tutorial should provide step-by-step explanations, real-world examples, and interactive exercises to reinforce learning.Current Behavior - Beginners often struggle wi

Description - It would be wonderful to have a feature to force all/specific fields to lowercase in datasets (similar to CJA component settings) Why is this feature important to you - When adding lookup datasets to CJA, if there's variance in casing the metadata isn't returned, even if the dimension is displayed in all lowercase. How would you like the feature to work - Radio button to force all fields to lowercase.  Checkboxes to allow only specific fields to be forced to lowercase. Current Behaviour - Can use data prep to lower case specific fields.  But that's not retroactive and only applies to one field at a time.

Description - Implement a storage view/tab inside "License usage" tab. Why is this feature important to you - We would like to know not only the percentage we are using, but, how this storage is distributed. For example, how much data does a dataset have. So we can know where we should optimise more. How would you like the feature to work - A dashboard that shows how much data does a dataset have. May be an average event weight would be appreciated. Current Behaviour - Currently we can only see the percentage and the estimation of last month for a dataset, not it's entire weight. Description:Currently, the "License Usage" tab only displays the overall storage percentage. This lacks detailed insights into actual storage distribution.Desired Feature:Implement a dedicated storage view/tab within "License Usage" that provides granular storage information.Specifically:A dashboard or a table displaying the total storage used by each dataset.(Optional) Include an average e

Summary:Expand the capabilities of Adobe Launch Data Elements by enabling them to return JavaScript Promises. This feature will allow asynchronous data retrieval and processing directly within Data Element configurations, enhancing flexibility and power for dynamic data handling.Problem Statement:Currently, Adobe Launch Data Elements are limited to storing static or computed values within the confines of Rules. While they are invaluable for capturing and managing data on web pages, their functionality is constrained by synchronous operations. Asynchronous tasks, such as API calls or event-driven data retrieval, require external code, limiting the tool's potential for multisolution integration and Extension Development. Proposed Solution:Introduce exiting functionality with Rules where Data Elements can return JavaScript Promises. This will enable asynchronous operations directly within Data Element configurations, allowing users to handle dynamic and async data retrieval without l

Description Currently, the search in Launch is barely useful, since it returns a very fluffy set of results, that quite often do not help finding what you are looking for. Quite often, the results just show a "... more" in the results list, but without actually giving you a chance to find what you are looking for.   This leads to developers rather not changing any DE names once in use to not break anything.   It would be awesome to be able to have more search features like "exact match" "regex match" case sensitive yes/no etc. Also, a optional dedicated search detail page that lists all the other results would be great! Ideally with a preview of the match.   Out of this need, external tools like the "Perpetua Digital Launch Assistant" are being developed, just addressing these shortcomings.   Why is this feature important to you Everybody knows you cannot just rename data element in Launch without potentially breaking things. Hence, whenever I want to rename a

Description - Due to Adobe's limitations on custom schema creation, we need the ability to generate audiences directly from a GCP bucket, similar to CSV import, as automating the CSV process is not possible.Why is this feature important to you - This is essential because we cannot automate the CSV process.How would you like the feature to work - We need the ability to create audiences directly from a GCP bucket, similar to CSV import.Current Behaviour -

Every event, condition and exception wich is saved in a rule is saved with a name. It would be a time saver, if it is possible to reuse saved events, conditions and exceptions in other new/existing rules.

Hi Team,as requested by customers, it would be great if there is a way to export all rules and elements for the purpose of maintaining the data dictionary and documentation.

Description - During a CSV import, there should be an option to either append the data to the existing dataset or overwrite it.Why is this feature important to you - This option is important because it prevents data loss and ensures proper data management. Without a clear choice between appending and overwriting, users might accidentally overwrite valuable existing data or create duplicate entries.How would you like the feature to work - When manually uploading a file with data for an audience, one of the steps should include an option to choose whether to append or overwrite the data.Current Behaviour - Currently, when manually uploading data, it's unclear whether the data is being appended or overwritten.

Description - We need to determine where a micro-audience is being used, such as whether it is part of a larger audience or journey.Why is this feature important to you - Audience cleanups will be easier since we’ll know which micro-audience belongs to which audience, preventing accidental deletions.How would you like the feature to work - In the selected audience window, in the Summary display whether it is part of other audiences.Current Behaviour - Currently, there is no straightforward way to determine if an audience is part of another one.