Product ideas | Community
Skip to main content

Ideas

Filter by idea status

10000+ Ideas

Selliers
SelliersLevel 4

Auto update a journey expressions when an existing audience name is updatedInvestigating

We have experienced that expressions with audience names in the expression is not updating if the audience is changing name. This causes the expression to fail. since the audience "is no longer there". This causes problems for the users of the platform and the customers receiving communication. In bigger organizations like ours there are many different teams working in AJO at the same time, also in different countries. If there is an audience library to be used of many users, as part of staying under the audience threshold limitation, many user can use the same audience for different kind of activities. Both as inclusions, as well as exclusions in the organizations activities. And many will therefor also have the same audiences used in expressions. We see that this now causes big and surveil danger in using expressions in AJO Journeys. An audience name can easy be changed, planned or by mistake. And the consequences can be big when expressions then stop to work as planned, only because of a name change. The changer of the name might not even be ware of all the Journeys where this audience name is been used. Backtracking this can be a though and hard job, finding all the logical breaks that now has has come. We suggest that there is "another" connector in the expression builder that uses the ID for the audience rather than the name. Relaying on a name is not a good idea in general. You can showing the name in the creator, but in the back is should really be an ID that is used, something stable and reliable that doesn't change regardless of name and content of the audience. This discovered weakness can cause surveil damage to our customers, without anyone knowing.    

Selliers
SelliersLevel 4

PreFix possibilities in naming of audiences, Journeys and offers etcInvestigating

In bigger organizations with many users that uses AJO if can be difficult to make all use a common naming convention to structure the content created in AJO, like audiences, Journeys and offers. Even if we have the folder possibilities it is a good thing to have a good naming convention when searching or navigating trough the content. Even all know and understand this importance, it is hard to make all users follow this in there hectic daily work. The idea is to have the possibility to create a set of PreFixes of names that you as a user can use when creating content. F ex you just select the name of the PreFix by selecting it with a checkbox or from a dropdown, when creating things. When saving the PreFix will then be saved as the first part of the name of the thing you create. If you have operations in different countries you might want to have a country PreFix, in addition to f ex the department you work in. A set of naming PreFixes could then be f ex.No_SalesSE_SalesDK_SalesNO_SupportSE_SupportDK_SupportWhen creating audiences, Journeys or offers you select on of this PreFixes that will be part of the final name. As a user you can f ex name your audience "missed incoming calls oct 2025". The final name in AJO will, with the PreFix be: "NO_Support - missed incoming calls oct 2025" Now all users can from the name see and understand that this audience is not just about missed calls, but it is in Norway and it is missed support calls. This can off course be solved manually by having this as routines for all users. But as we all know it is hard to get all to follow routines like this, especially when resources coming and going over time. Therefor it would be a great feature to be able to administrate something like that from the tool itself. 

bjoern__koth
Community Advisor and Adobe Champion
bjoern__kothCommunity Advisor and Adobe Champion

Launch Web SDK Extension - Define a custom _id attribute in Experience Event calls or a deduplication key for identical events from different sourcesNew

Description - These days in Launch's Web SDK extension, it is not possible to manually override the "_id" attribute in Web SDK XDM object data elements. As a workaround, if one wanted to manually define this _id, one would have to code an alloy "sendEvent" and specify the _id there. The approach / idea resembles very much the hybrid tracking approach for client- and server-side, that many 3rd party vendors suggest these days, where a deduplication key can be specified that either drops or merges events with duplicate ids.   Why is this feature important to you Completeness of data and fastest possible data availability: Web SDK data relies on cookie consent which may not have been given by the users i.e., an order event may or may not be captured by the Web SDK this lack of order data significantly impacts the number of addressable members in an audience, that may be built upon CRM and commerce data while this commerce data can also be streamed into the Platform from the commerce or CMS backend through an HTTP API call, this will still likely be slower than the Web SDK data if you need it for immediate personalization (e.g., recommendation) but due to the immutability of Experience Events, sending order data from two sources, Web SDK + Commerce will affect the order events and revenue numbers in the CDP and connected analytics sources. right now, there is no deduplication key like other vendors provide in their Conversion API now, if we could manually specify the same _id attribute for all data sources, which ever event comes in first wins, and the other(s) with the same _id will be ignored in the CDP profile (while they are still floating around in the datalake)   How would you like the feature to work Either implement a deduplication key feature like other Conversion APIs or allow the _id to be manually overridden (with a clear warnings about the possible implications)   Current Behaviour The UI shows a big warning "The value for this field will be auto-populated when this data element is provided as the XDM object for a Send event action. This value cannot be overwritten."

Jennifer_Dungan
Community Advisor and Adobe Champion
Jennifer_DunganCommunity Advisor and Adobe Champion

Add the ability to filter Freeform table rows dynamically based on metric thresholdsNew

Description This question has come up multiple times in the last few weeks, and it probably surfacing in other channels as well, but there should be a way to filter the rows in a freeform table based on Metric Count. So only show items below X, or above Y, or between X and Y.   While we can filter rows manually via the "only show these rows" the values can change month to month, being able to only show rows based on a specific criteria seems like a basic function we should have, and yet don't as of yet.     Why is this feature important to you Values change month to month, so having to manually find and filter rows is a lot of effort that we shouldn't need. While, yes, we can use a calculated metric to change rows outside of a range using IF and Greater Than/Less Than logic (using a static 0 for outside our range), the rows, while no longer counting in the total, still show in the table.     How would you like the feature to work Either in the dimension filters, or possibly in the metric column settings, there should be a way to add a metric threshold filter: [metric] Greater Than (or equal to) X and Less Than (or equal to) Y, or just Greater Than (or equal to) OR Less Than (or equal to)     Current Behaviour Today we can only filter by text matches, there is no equivalent feature.

Rich Text Editing Options for Tasks Details > Overview > DescriptionNew

Description - Enable Rich Text Editing for Task Details > Overview > Description.Why is this feature important to you - It would give us more tools to emphasize and communicate key details in the instructions and provide better readability for the user assigned to the task. Better readability means faster turnaround and fewer mistakes.How would you like the feature to work - Give us the same formatting options that are here in Ideas, i.e., preformatted styles, text color, text size, font, insert/edit code, insert video, create table, alignment, indent/outdent. Current Behaviour - Only plain text can be used, so instructions for tasks that are more complex are created in Word and uploaded, then a note is added to the task to see the attached Document for instructions which is less efficient for everyone.__________________________________________________________________________________________________ Here's a lot more UX friendly example (overly styled/colored for emphasis): Description - Enable Rich Text Editing for Task Details > Overview > Description.Why is this feature important to you - It would give us more tools to emphasize and communicate key details in the instructions and provide better readability for the user assigned to the task. Better readability means faster turnaround and fewer mistakes.How would you like the feature to work - Give us the same formatting options that are here in Ideas, i.e., preformatted styles, text color, text size, font, clear formatting, insert/edit code, insert video, create table, alignment, indent/outdent. Current Behaviour - Only plain text can be used, so instructions for tasks that are more complex are created in Word and uploaded, then a note is added to the task see the attached Document for instructions which is less efficient for everyone. Thank you for considering!