Adobe Journey Optimizer

Currently when within an Offer Decisioning call deduplication is required between decision scopes a Round Robin principle is applied between scopes, meaning that every scope in turn gets an Offer assigned, even if the first scope in the decision requires two or more Offers. It should be possible to first return all Offers required for the first scope before turning to assigning Offers to the next scopes.Applying the Round Robin principle causes sub-optimal Offer assignments to scopes. An Offer with a higher priority gets assigned to the second scope in the decision instead of to the first scope. The order of the scopes in the decision is in that sense not respected.

Currently Offer Decisioning context parameters cannot be used to personalize content. It should be possible to use Offer Decisioning context parameters in content personalization.In some cases we want to differentiate content based on context parameters of the Offer Decisioning Request. E.g. language parameter : customers can use our apps in a language that differs from the language known in their profile, we want to propose content in the language that they are using the app in. We must avoid having content in a different language from the language the app is used in.

Currently the language parameter in the content definition screen is not of any use. It is not possible to have more than one content per Offer per Placement, even if they are in a different language. So content differentiation on language needs to be done through if statements in the same single JSON per Placement. It should be possible to define a content per Placement per language.We need to have the same content always in two languages, Dutch and French. It would be most logic to be able to indicate in the language parameter in which language the content is defined. Now this language parameter is not of any use in the content definition screen. Adding the possibility to define a content per Placement per language would also simplify the JSON definition of the content because additional if statements can be avoided.

Currently Offer Decisionig Simulations via UI can only be executed for customers flagged as 'test' customers. It should be possible to execute Offer Decisionig Simulations via UI for all customers without having impact on for example capping parameters. It should be posible to execute an Offer Decisioning request and seeing the result without impactig customer profile, this means as a real 'simulation' via UI (not realistic call).There is no way in the UI to check a customers' eligibility or Offer scores for specific Offers. In case of complaints or inquiries on what Offers a customer sees, we need to be able to simulate the customers' situation without impactig it to understand what is happening. This means not influencing the future behaviour of the Offer Decisioning for the customer itself. E.g. A customer should not reach the capping of an Offer because we simulated the behaviour of the Offer Decsisioning for him or her.

Currently there is no UI support at all for writing Ranking expressions (no operator suggestions, no profile attributes lists, no offer attributes lists, …). It should be possible to get some UI support when writing Ranking expressions.Avoid having to know all eperators and all profile and offer variable names by haert to more easily develop Ranking expressions.

Currently a fall back-offer is obligatory. Fall-back Offers should be optional so that an Offer Decisionig request can be empty when there is no persoalized Offer to propose.It should remain an option not to propose anything to the customer if there is no personalized Offer to be proposed.

For developers it is not possible to edit the html of a fragment. In ACS this was possible via Edit - HTML. Once you have created the fragment via the Designer, if the code is not working as it should, you should be able to edit the html as well. That is how developers usually work. The feature should work something like in ACS where you can add the edit HTML option somewhere. Current behavior is create a new fragment, but that is not ideal.

In AJO we cannot delete fragments which should not be used anymore. There is an archiving option.  Next to archiving my team would like to have this feature to clean up fragments which should never be used anymore This should only be possible with certain rights, not for every user. Current Behaviour = Archiving all fragments which should not be used anymore. Any ideas?

Description - Sorry if the subject was a bit cryptic  😀 When creating email content we often have content to be shown to only a set of customers e.g. has not downloaded our mobile app or belongs to this VIP customer group. In todays dynamic content there is always a default option, so we cannot use the built in functionality to include/exclude customers to receive this specific topic.  We solve this today using a IF statement in the HTML code or add a Offer. It works but it's not as easy as adding a dynamic rule. And we see it might be more complicated the more offers we will add to the email content.  Why is this feature important to you - We are going to start using fragments and several offers with in our email content. having the possibility to add a dynamic content to be shown only to some customers without having a default item will make it easier for not-so-technical content creators to generate email content.  How would you like t

Description -* In an enterprise context, there are multiple users who will open and may make changes to a canavs. Having an inspectable history of changes that have happened will enable the ability to pinpoint which last change may have caused negative effects to the canvas' outputsWhy is this feature important to you - This will increase agility for our canvas teams and improve our debug speed.How would you like the feature to work - When inside an actual canvas, navigate to Canvas Properties, expandable section to show version changesCurrent Behaviour - Only able to see "Last Updated By" and "Last Update" on the Journeys > Browse UI

Description - We have noticed that when two users have the same canvas open, and they are both making changes to the canvas (co-editing), changes are not saved between both users at the same time. As a result, we've tried to enforce discipline where one user has the canvas open at a time and users who finish editing a canvas closes that window/tab, in order to not affect future users' changes to the canvas. However, this does not always work well. It would help to know when the canvas is receiving active data from a users' session, so that I can proactively reach out to that user internally to ask them to close their windows/tabsWhy is this feature important to you - We have lost work due to "loss of changes" because of the lack of co-editing supportHow would you like the feature to work - It would help if there was a way to show when another user has the canvas active. This could look like how the Google Suite/Microsoft Office shows active sessions from other users. Current Behav

Description - while in emails you have bcc functionality that allow the company to have a copy of the exact message sent to the client , in push and sms there isn't a way to do that Why is this feature important to you - we work with insurance and banks and it really necessary to have copy of the end client.How would you like the feature to work - i think the best is the save the data in temporary dataset for a month , and let us to export it with the destination feature then delete it. as i was told, this feature was in the former campaign product Current Behaviour - no record at all

Description -I need the AEP/AJO system to identify proactively journeys or experiences that may not be behaving as planned.  For instance if a customer is receiving an email multiple times or reentering a journey multiple times due to a design flaw,  Why is this feature important to you:We had a journey trigger 3-20 times to the same customers and there was not way to spot this issue within the application, however all the data is within the system.  Teams design with the best of intentions, however I want the application to help monitor performance for ongoing solutions/automations.   How would you like the feature to work -I would like AEP/AJO to flag this to an Admin to identify if this behaviour is aligning with the intended Journey.  If the admin approves, then this alert can be dismissed.   I want the AI assistant to alert us. I would like to be able to set a global guardrails that flags customers who have reentered a journey

Description - Ability to organize campaigns in foldersWhy is this feature important to you - Having multiple brands and teams in a single sandbox, organizing and filtering becomes difficult.How would you like the feature to work -Given audiences have a folder functionality, we would like the ability to organize campaigns across our many operating entities by folder. Current Behavior—No folders for campaigns.