Adobe Journey Optimizer

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

Hi, It would be good if we can deploy Fragments from one sandbox to another e.g, from a sandbox in our lower environment (Test to Prod). Why is this feature important to you - We develop our email fragments in Test before adding them to Prod, it will save us time and make sure code is exactly same in both sandboxes.How would you like the feature to work - Deployment from one sandbox to another, similar functionality as with Journeys (Copy to Sandbox)Current Behavior - I have created several Fragments in our test sandbox and are now looking at promoting them to Prod as of now is a thorough, manual and slow process.  

Description - We'd highly appreciate an option to restore key objects in the product. At the moment majority of users would like to have ability to modify objects like Decisions/Offers/Journeys etc., however there's no way to restore changes applied to them or even to lookup previous version/status of those objects.   Why is this feature important to you - since high volume of users has ability to modify all others objects (mentioned above), and there's no ownership of those objects it's very easy for someone to break others objects, either by accident or because of similarities in naming convention. We need to have this ability to restore to previous version, ability to protect them from others (sharing options) would also be useful.      How would you like the feature to work - many options:  1. simple     - API endpoint with lookup to previous versions of the object, and ability to append JSON response into another call to update that object to pr

  Description - I would like to have alerts on all the journeys and would like to made aware when these journeys fail. We as of now have no other option other than manually check them. This then leads to journeys being broken for a longer time without us knowing. I am aware that alerts are used for failure of ingestion or when a certain threshold is crossed. I think it should also work with journeys on a individual level.   Why is this feature important to you - In the current situation we are not made aware if journeys fail due to any circumstances. this means that customers have a suboptimal experience. How would you like the feature to work - We would like to receive a push notification in the UI and preferably with an email when failed journeys pop up. In the ideal situation we would be able ourselves to set up when an alert is triggered based on how many journeys it fails. Current Behaviour - We currently do not receive any alert and have to manually check ove