Adobe Journey Optimizer

We are experience that maintenance of Tags is hard do to access rights, especially deleting Tags. It must be easier to change the name and/or to delete a Tag that is not wanted or not just any more. It the Tag feature shall work and be trusted by the users the Tag must be spelled right be generic and have some sort of structure. This is work that is always going on - and the need of change and maintenance will always be there. We see misspelled words, not generic enough  and the list includes many tests. This is hard to change and make the tool full of "bad data" - and the user experience will drop over time.  During the development of AJO there has come better features regarding deleting audiences. When deleting a audience it will be checked it this audience is connected to another audience and/or a journey. If so you get a error message and info about that connections there is regarding the audience you want to delete. We see the need of the same mindset here rega

Currently even Offers with a Ranking score of 0 will be sent back as a response. It should be possible to avoid sending back Offers to the customer based on the value of the Ranking formula (e.g. if the value is 0).Some conditions need to be generally applied without having the risk that someone forgets to apply them. Therefore these conditions are not put into the Offer eligibilities (recurring risk to forget them) but they are put in the ranking formulas so that they are automatically generally applied.

Develop an AJO native connector with Sinch for Instant Messaging (conversation API), likewise, it exists for the SMS Sinch OOTB connector already.Currently, this integration is only possible through the implementation of Custom Action in AJO. This leads, above adding extra effort for custom solutions, to having a different approach for SMS and IM despite using the same destination with Sinch platform. 

helloi think that this is a legitimate request from the client : want to log each message content that was sent to their customer.let say they send to the customer SMS that alerts him that he has some action to do until some datethen , when you have the log with what you sent the customer can not argue that he wasn't alertedsame goes for promotions - if the client claim a discount you can prove what exactly sent to him.since this a lot of data to store , the common practice is to save it with expiration date on some storage that our client (not the end customer) has access to it for let say a monththen it is our client responsibility to download it in this period of time, then Adobe remove itNir

I would like to be able to see all dependences that a audience has at all time. Audiences is the beating heart ot the solution and I therefor need to see where these is used to have good control. Today when trying to delete a audience we get a error message it it is in use somewhere. I would like to have more information regarding this. Like showing exactly where it is used, in other audiences, in offers, in Campaigns and in Journeys. This is an extended version of todays error report when trying to delete a used audience. I would also like to be able to manually run this check on every audience just to se it here is any dependencies to this audience.  

Description -Why is this feature important to you - Twilio is one of largest providers, and there is no way to directly send Whatapp messages in AJOcurrently AJO can send only JSON messages while  Twilio (and maybe other providers) accept only application/x-www-form-urlencoded How would you like the feature to work -  built in action for WhatsApp or have the ability to send application/x-www-form-urlencoded with custom action , not just JSON Current Behaviour - According to the documentation for Adobe Journey Optimizer, when configuring a custom action, the Content-Type header is set by default and cannot be deleted. However, the value of this header is expected to be in JSON format. This indicates that the native support for sending payloads is primarily designed for JSON content types, and does not mention direct support for application/x-www-form-urlencoded or multipart/form-data. Therefore, the answer to the question is that Journey Optimizer does

Description - device information (user Agent) in the tracking dataset   Why is this feature important to you - It will give us ability to track if users are more on Mobile or Desktop. Also help to debug in case of clicks not reaching landing pages if the failures are related to mobile or web browser. It will also help to ghost opens (Apple Mail Privacy) from real openers   How would you like the feature to work - Getting the details into tracking dataset. Add a report on a breakdown of open and clicks per operating systems, devices and browsers will be a plus   Current Behaviour - None   Thanks, David

Description -In the context of reporting, the control group holds significant importance. Why is this feature important to you -It is an important marketing KPI in reportingHow would you like the feature to work -We want to compare the same target group/audience who fulfill the same criteria. Then we will compare the contacted vs not contacted customers by sales Kpi. That not contacted customers will be flagged and frozen in the control group. Current Behaviour -It is not available at all for Journeys. I've come across several posts where Adobe has mentioned that this feature is currently unavailable.

In the customer profile UI there is currently no possibility to quickly check Offer eligibilities (for all active Offers). It should be possible in the customer profile UI to check the eligibility of Offers.Operational efficiency when performing testing or investigation tasks required for a customer inquiry.

Currently there is only one fall-back Offer per decision, even if in the decision there are multiple Placements involved. It should be possible to indicate a fall-back Offer per Placements.If there is more than 1 Placement involved in a decision but there is only 1 fall-back Offer per decision, it means that some Placements will not be used as a potetial promotion. This can be sub-optimal in the communication strategy towards the customers.

Currently context parameters can already be used in Offer eligibility rules but only via the API and not via the UI. It should be possible to also use them via the UI.Full use of the UI potential in daily operations, without having to create ourselves an API interface fur daily operational tasks.

Description - the Journey Optimizer > Browse UI has fixed column widths. This causes problems to quickly assessing information of the Journeys on this UI. Having the ability to resize column widths to my preference will enable agility in navigation and speed to workWhy is this feature important to you - Our naming convention is complex due to a lack of folder structure in the Browse UI, and thus the ability to navigate quickly to our Journeys is limited because the title of the Journeys are cut off. In addition, other columns, such as "last Updated By", or "Published by", get cut off because of how the UI resizes column widths to account for window widthsHow would you like the feature to work - I'd to "drag and drop" the column width to my likingCurrent Behaviour - column widths are not modifiable. They do resize to account for window width, but this does not provide me the agility I would like.

Description  We have a front-end developer who is developing e-mail blocks in HTML that we save in the Adobe Library. This is a nice function because this makes it easier the re-use components of an e-mail.Unfortunately, it is not possible to add it to the library with a contextual attribute in it. I understand that I can't use a field that belongs to a specific event in e-mails with other events, but still, I would like to save it.Now our front-ender is creating the HTML components, but then the marketers still need to add the contextual attributes manually. This takes a lot of extra time and is more sensitive to errors.So my request: I would like to save HTML components WITH contextual attributes. Why is this feature important to you: to easily build new e-mails and edit existing ones without making mistakes or spending a lot of time again.  How would you like the feature to work:  I would like to save HTML components WITH contextual attributes.   Current Be