Adobe Experience Platform

Description - Be able to define a well-defined process to manage the AEP artifacts in the code repository and then have an automated way to deploy them between environments easily.  Why is this feature important to you - As the project grows, it's not easy to manage changes between environments. A lot of things get manual and we lose track of what is in stage & what is in prod. How would you like the feature to work - Need a better-automated way and also a well-defined code structure. Current Behaviour - There are postman APIs to create & update artifacts, but that needs to get further enhanced to automate this well based on ongoing changes - add/modify/delete. Some artifacts will always be manual eg: new segments & updates, but few areas should be controlled well with code to maintain consistency eg: schemas & datasets, managing identities, and DULE labels & policies.

DescriptionWe just migrated from Adobe Analytics to the Web SDK, we are using the XDM Object Data Element to do the Mapping with the existing Data Elements. To decrease the amount of work required for that migration we found out that the best option was to do the Mapping at the value level for both eVars, pros & events.  Current BehaviourWe noticed that the Web SDK hits were sending empty string and empty object, what Adobe Analytics hits were eliminated by default. We did not have to worry about this before the Web SDK migration. How would you like the feature to workWe would like that the Web SDK just work the same way the Adobe Analytics was working, just discard all the variables that are empty or undefined.Why is this feature important to you Until now we were looking at the data only in Adobe Analytics and the reporting was working fine even without the non-optimized Web SDK hits, but now that we are trying to work with the Adobe Experience Platform, we no

I would like to know how to configure the debugger so that when inspecting event objects, I do not need to manually expand the payload.How do I do that? 

Description -While conducting our first real-life implementation case for data collection via the AEP Web SDK and the Edge Network, we wanted to rely on the out-of-the-box customer consent preferences:https://experienceleague.adobe.com/docs/experience-platform/edge/consent/supporting-consent.html?lang=en However, while experimenting with the different options available, we were facing major limitations with regards to the flexibility of handling the consent - in particular with the current consent object:  consent: [{ standard: "Adobe", version: "2.0", value: { collect: { val: "y" }, metadata: { time: "2021-03-17T15:48:42-07:00" } } }]  Mainly, I'm referring to these two limitations stated in the official documentation:#1 No granular consent handling:"Currently, the SDK supports only a single all or nothing purpose." #2 No overwriting of the collected consent:"Af

Description - Companies are able to develop and release both private and public Extensions to Adobe Tags to provide new capabilities. However, the process of making an Extension available internally or externally is complicated to a point where companies and individual community members (me included) refrain from doing so. While the development can be complicated on its own due to the mandatory Node JS tool stack, releasing an Extension (even internally) is even more convoluted and requires work with the APIs, managing Adobe IO integrations, and certificates/keys. To help with that, I want to propose an extension to the web interface of Tags to allow easier Extension management. Why is this feature important to you - Because I would like to see a more active community around providing capabilities for Adobe Tags. How would you like the feature to work - In an Extension-development Property within Tags, provide new menu items to manage Extensions. Specifically, I can think of options f

Currently, the Computed Attribute feature does not support fields based on the `relationship` XDM construct.If using one of those, you will get a 500 error upon publishing Why is this feature important to you:Ability to use relationship exists at schema level, you'd want to be able to leverage this across the product, including when building Computed Attribute for added flexibility. 

Description - Allow the audience rule to look at events "In the last x days of this month". Why is this feature important to you - In order to achieve "in the last x days of this month", the marketer must explicitly select the last 2 days of the month using the "From date to date" options. From month to month, the marketer must then change the last two days of the month. We need an option to set "last x days of this month" so that a marketer doesn't need to modify the audience rule month-to-month.How would you like the feature to work - Similar to the "This Month" and "In Last" options, we would like to be able to combine these two options ie. "In the last 2 days of this month". This option would be available in the drop down shown in the attached screenshot. So for the month of November, "In the last 2 days of this month" would look for events that occur on 11/29 and 11/30. In the month of February, this configuration would look for events that occur on 2/27 and 2/28; similarly f

Description -Why is this feature important to you - this helps in debugging in case of any failures.How would you like the feature to work - File name should be made available in list of fields available so that it can be mapped to a field in schema.Current Behaviour - No such information is available so that we can link a batch to a file name and use that for debugging.

In the current set-up, data files can be sent to the Adobe Data Landing Zone, which in AEP is considered as an external cloud storage.The file there can be sent encrypted and decrypted by AEP.Huge data files (over 1gb) can be zipped. Issue now is that unzipping and decrypting the data files are 2 distinct steps, where ideally both can be handled immediately together.Enhancement request: unzip & decrypting files via 1 command/step

Description - There is a helpful feature in Tealium IQ TMS where you can see visually in UI what is the exact order of operations of your various rules, and you can simply drag and drop to change their order. Why is this feature important to you - Helpful because we don't have to then go to individual rule to check the order priority we have set. We can see in UI directly and change it. How would you like the feature to work - A drag or drop interface for all currently enabled rules, which can be changed to different scopes easily.Current Behaviour - Rule ordering allows you to control the order of execution for rules that share an event. Each rule contains an integer that determines its order priority (the default value being 50). Rules that contain lower values for their order are executed before those with higher values. 

Description -Why is this feature important to you - The biggest challenge for the customers who are using Adobe experience platform is to manage the active profiles only in the profile store, to delete the profiles we use profile delete entity API, which is cumbersome process, the below idea will be useful to delete the profiles. How would you like the feature to work - This feature work based on the create the new dataset with active customers and delete the older dataset. this is the simple and easy way to delete the profiles.Current Behavior -Create the profile enabled dataset with same schema use for the current datasetSelect active profiles from the old schema into the new schemaDelete the old schema , will completely remove all the foot prints of the inactive profiles from profile store and all the places in AEPProfile store will rebuilt only with the active customers

With GDPR coming, the need for consent awareness of rules and actions is becoming more stringent.We have quite a lot of rules which stack up depending on a consent level of the user (e.g.):- strict -> only complete anonymous tracking allowed (eg. analytics beacon)- mid -> some user identification allowed (hashed)- low -> 3rd party pixels allowedCurrently we have to make for each of these levels a rule, take e.g. a simple page view:- level at least strict -> send out the analytics beacon- level at least mid -> send data to DMP- level at least low -> set a DoubleClick display PixelWhich ends up for quite a lot of our rules, we have to double or triple them...Some idea could be to have e.g. a consent check action in the action chain. If the check fails, the rest of the action chain is not executed anymore. This could combine the 3 rules above into 1 page view rule with this action chain:Actions: set AA vars -> send AA beacon -> clear AA vars -> check consent mid

Description - A Source Connector for messaging queus Why is this feature important to you - Backend system uses AMQP for eventsHow would you like the feature to work - A Connector to enable consuming AMQP events, as an alternativt to the HTTP Streaming ConnectorCurrent Behaviour - No current support

Hello, Right now it is not possible, when uploading files in batch for a record dataset, to make a full sync that can remove older batches of the dataset to be fully replaced by a new batch. The old batches can be removed from the catalog, but not from the profile when working with record datasets. This is a problem when we work with sources that sends a full snapshot of the data, because records existing in old batches that are no longer in the recent snapshot are not deleted in AEP (think about AI models where the objective users affected by the algorithm may change) Thanks and kind regards

Description - There use to be a visual indicator of previously published revisions, now there is no way to see at a glance those revisions that have been previously published - I have to hover over each revision which is a slow and painful experience 😞    

Description - Allow users to remove historical edits that were not published Why is this feature important to you - The version history can become littered with small edits that don't get published.  Being able to remove historical edits that were never published to prod will allow us remove unnecessary changes if we choose to.. (You could maybe lock this feature to an admin user?) How would you like the feature to work -  Any item in the version history prior to the current published version that has never been published should have an option to remove it from the version history. Current Behaviour - There is no option to remove previous unpublished versions. 

Description - I am requesting the ability to see what users have accessed /  used CJA from a certain date.Why is this feature important to you - We are trying to track user adoption as well as justify use.How would you like the feature to work - Either an option present in an Admin tab similar to AA or something in the admin console functionality.Current Behaviour - Unable to see this information without tracking individual actions through the audit log and tracking use manually in real time.

Description - Adobe Experience Cloud Experience Platform Dynamic Data Collection Launch, by Adobe Tags minifies code when a library is built. That feature is super helpful for production environments, where site owners usually want to minimize the impact of loaded libraries. And that is great! Except for when you are actually trying to read the code afterwards. For example, minification turns my horrible, hacky, readable and commented code... into this horrible, hacky, unreadable and uncommented code: While the size advantage justifies the less readable code on production, practically every developer I've ever worked with complained about the minified code on any non-prod environment. If you just want to see what a piece of code does and why it won't work, minification does not help a lot. The usual solution is to remove the .min from the Launch library's file name, but that requires a) knowledge of the feature and b) some manual intervention, browser plugins, or other

Description - A better summary for each certification, with every part needed to study explained Why is this feature important to you - I want to get certifications and t's difficult to beginHow would you like the feature to work - GoodCurrent Behaviour - There is not really a good for study certification system @alnavarg @heku_ @_manoj_kumar_  @yansu  @3176980 

Description - It would be great if within Launch we could apply tags to rules and data elements to categorise. We have to get creative with naming conventions to describe what a rule does and what is firing within it. If I could tag a rule with "google ads" and filter all the rules where that tag exists, I can easily edit a pixel firing on those rules. Right now, I have to write it in the name or click into every rule. Other tag managers have this simple UX feature. Why is this feature important to you - It helps us organise our implementation, and saves a lot of time. QoL function. How would you like the feature to work - Explained in the description. Current Behaviour - As above - naming conventions have to do all of the heavy lifting.

Description - Unlike all other fields in the Cloud Connector, like the headers and query parameters, it’s not possible to load a data element into the URL.Why is this feature important to you - This makes it impossible to use the Cloud Connector for dynamic URLs, which is common practice in a lot of data streaming platformsHow would you like the feature to work - to have the possibility to add a data element in the URL, the same way as with a query parameterCurrent Behaviour - there is no possibility to do this, so requests with a dynamic URL have to be written in Custom Code

Description -Why is this feature important to you - It will help to create different criteria based segment. How would you like the feature to work -Requesting additional segment functions to make it easier to create all the segments from the AEP Segment Builder UI. Function Description 1: get the month of the date and equals it to the next monthCalculation 1 : month(date) = next monthFunction Description 2: perform calculation on integers such as subtraction and division. It would useful to input an integer without having the attribute (i.e. input 365 to divide for one year)Calculation 2: (integer – integer2) / 365(input integer)Function Description 3: get the month of the date attribute and equals it to the month of another date attributeCalculation 3: month(date) = month(date2)Current Behaviour - Such function are not supported

We would like all the existing Adobe Analytics dimensions (eVars[1-200], props[1-75], and events[1-1000], list[1-3]) to be automatically mapped using a supported or new schema mixin. In addition, this would be needed for product syntax eVars and events. This is important for existing implementations with a significant number of custom dimensions. It will ensure customers will not have to manually map every single custom dimension via processing rules. In addition, it will allow customers that leverage the raw data feed to use the AEP SDK.  At this time, only specific dimensions are automatically supported.https://experienceleague.adobe.com/docs/experience-platform/edge/data-collection/adobe-analytics/man... This is already supported for standard dimensions like products, commerce, and page details. https://experienceleague.adobe.com/docs/experience-platform/edge/data-collection/adobe-analytics/aut... For us, the raw data feed is critical for our

We are migrating to new Adobe Experience Platform Launch for all our mobile apps, and the list of properties in Adobe Launch is growing.  I do not see any ways to filter properties by companies, report suites, platforms, etc.  Can we get some filters for the property list?  Thanks!

Try to do a workflow with a query and a List Update activities  Then you have your results like that @campaignerforlife  @heku_