Adobe Real-Time Customer Data Platform

Description - When creating an audience within audience builder, we sometimes will use other audiences as a baseline. When we go to look at the available options to use, it does not group them by the folder structure that we have created, meaning the audience you’re looking to use is harder to find. We want to make the folder structure available for use within the builder search menu Why is this feature important to you - A big part of RTCDP for my team is the ability to reuse audiences. We have created a folder structure to make it easier to find the audiences that we want to use as "building blocks" in our new audiences that we create. If we cannot navigate the folder structure in the Audience Builder (AB) UI, then it becomes almost obsolete. Additionally, since we will have multiple teams operating and creating hundreds of audiences in our platform, it is much too difficult for our users to look for the correct audience "building block" in an unstructured AB. How

Description -Why is this feature important to you - In. last 3/4 years of working with various use cases I have delt with, a very common use case I came across is creating segment using some date field where the audience building criteria is:date is before current timestampdate is after current timestamp For last 3/4 years, I have been handling this type of requests/requirementsusing data distiller Query Service Only ORhave an additional field "status" and requesting data source to derive and set the value or adding computed field mapping in the dataflow during ingestion  All these options create an additional complexity. As users of AEP is mainly expected to be marketers, I think for this type of simple use cases, reaching out to IT team pushes the capability AEP in bad place - I have seen people raising eyebrows.  There are so many features getting added in AEP every month. Can't we expect an enhancement in AEP Audience Builder UI to be able to do t

Description - It would be beneficial for stakeholders building audiences in AEP, if it was possible to only show eventTypes within the enum list, that are currently populating data. Not including all OOTB eventTypes that are available.   Why is this feature important to you - This would avoid any confusion of creating audiences using eventTypes that are not currently populating data with the tenant's instance of AEP.   How would you like the feature to work - Ability to customize the enum list for eventType   Current Behaviour - eventType enum list populates all OOTB values

Description - Ability to persist splits of an audience Why is this feature important to you - Usage of experimentation within audiences (test/control/holdout) are important to measuring KPI's of an auidence.How would you like the feature to work - When a split of an audience is performed, have the ability to select the persistence of the audience based upon a system and or use defined time based value.Current Behaviour - Audience splits are available in Adobe RTCDP audience compositions, but the split of audiences are not retained after the split is performed.  

Description -When you go to the profile and select one profile and go to Events tab. We see events old events first, if we have bunch of events it is very difficult and time consuming to see the latest events.Why is this feature important to you - To save time when we want to see the profile events.How would you like the feature to work - we should have sorting feature on events and pagination as well .Current Behaviour -When you go to the profile and select one profile and go to Events tab. We see events old events first, if we have bunch of events it is very difficult and time consuming to see the latest events. 

Description - Schema less event data collectionWhy is this feature important to you - Using a schema less approach to data collection will allow event data collection without having to defined all of the event attributes for an event.How would you like the feature to work -  Ability to defined a schema as event based data collection with an identitfer(namespace(s), _id, and timestamp.  The metadata of the event(s) does not need to be defined upon the schema.Current Behaviour - When defining event based data collection within the XDM experience class we need to define all of the attributes which are expected to be collected by a producer.

Description - Currently the RT-CDP UI (Sources, Segments, Destinations) are embedded within the AEP UI (along with data catalog, query services etc). This creates a lot of confusing on the positioning of the platform. While RT-CDP is an Application Service (or Application), this is the only applciation which does not have a separate UI like CJA and AJO. So customers are getting this intutively. Also RT-CDP would be accessed by many agencies and digital advertsing teams inside a client organization. Imagine bigger clients with 100's of marketing teams globally. It becomes a nightmare to enable good adoption across the board.Why is this feature important to you - It would intutively enhance adoption of RT-CDP across all segments of users (like agency, ad teams)How would you like the feature to work - There has to be a simple UI for RT-CDP separately. This should have RBAC as well. This should be offered as a separate Application under the solution-switcher menu.Current Behaviour - The UI

Description - Currently there is no way (as far as I know) to view the rule setup (the UI definition) of a segment which is created with an PQL expression (and without an ansibleDataModel) through the API. Why is this feature important to you - We are currently automating the creation process of multiple batch / edge segments, across different sandboxes. Since we are not able to reverse engineer the ansibleDataModel, we are creating the segment with a PQL expression. This gives us a segment which we are not able to look at in the same way as manually UI-created segments How would you like the feature to work - Maybe generate the ansibleDataModel based on the PQL-expression automatically (if the ansibleDatamodel is missing in the request). Also it would be nice if we could set a UI_read_only-flag on the segment, so we can assure that it is not changed by the users in the UI. Current Behaviour - Segments created through API with a PQL-expression (where ansibleDataMode

Description - Currently it is not possible to handle tags through the APIWhy is this feature important to you -  The administration of tags on segments/audiences is important for us since we are trying to create the same tags in CJA. This is not possible at the moment, since we cannot make a lookup on the tagId, to get the name(value) of the tag. How would you like the feature to work - I would like CRUD operations on segment/audience tags available through the APICurrent Behaviour - Adding tags and listing tags can currently only be made through the UI.

Description - The ability to disable specific audiences from valuation instead of disabling/deleting ALL or no audienceWhy is this feature important to you - This allows customers to more dynamically select audiences when evaluating. How would you like the feature to work - Have a toggle to select which specific audiences to be included/excludedCurrent Behaviour - It only disables the audience evaluation for all or no audience. 

Description - Event Expiration based upon eventTypeWhy is this feature important to you - Ability to define an expiration of an event Type will allow for the expansion of dataSet TTL.  Only a TTL can be defined at a dataSet level.  This creates multiple dataSets with different eventTypes.  While this will work for some use cases it not substainable.How would you like the feature to work - Create a TTL for an event Type at a dataSet level and or at the Unified Profile store level.Current Behaviour - Each dataSet can be defined with a TTL which is managed by Data Hygiene or an Adobe Support resource

Description: Presently, the Data Science services section only accommodates Customer AI, primarily utilized for generating propensity scores for diverse profiles. However, it falls short in empowering customers to deploy their personalized machine learning models. This limitation necessitates a reliance on alternative tools, hindering the full utilization of data resources.Why is this feature important to you: The integration of this feature is crucial as it opens avenues for deriving tailored insights from data, aligning precisely with the unique requirements of each customer. The absence of the ability to deploy individual machine learning models constrains the potential utility of the available data, impeding the generation of valuable, customer-specific insights.How would you like the feature to work: We propose the enhancement of the RT-CDP (Real-Time Customer Data Platform) by incorporating the capability for users to deploy their personalized machine learning models within the D

Description - We are using the profile API to enhance a users profile with a CDP solution. Currently when we generate a token (In Adobe Target), which is then inserted into the CDP solution, it needs to be regenerated and replaced every 90 days in order for the functionality to continue undisturbed. Why is this feature important to you - The implications of someone not remembering to do this very manual task is large and in an age where personalisation is at the front of most strategies surely this is a small enhancement that would be deemed necessary for implementation in order to minimise risk for customers How would you like the feature to work - Where Profile tokens are being generated for implementation purposes it would be great to have the ability to choose the timeframe you want the token to expire (i.e. 6,12,24 months) or make it possible to set it as never Current Behaviour - Currently the profile API token expires after 90days, a new token must be generated and replace the

Description - The segments UI in AEP (RT-CDP) currently does not have a folder structure to manage the segments. For large customers, having folders and RBAC for the folders are important from RT-CDP use cases perspecive.Why is this feature important to you - Large customers create 10s of 100s of segments and folder taxonomy makes it easier to group by campaigns, geo, teams etc.How would you like the feature to work - There should be a folder view for the segments (like Audience Manager) and sub-folder structure to house the segments. It should also have RBAC for governance. Folders and sub-folders should be displayed in the search results to easily locate the placement of the segments.Current Behaviour - List and pagination based listing of all the segments created