Adobe Journey Optimizer

DescriptionI would like to be able to choose one or several attributes as Journey Exit Criteria. Why is this feature important to youThis feature is important because I don't necessarily want to create more audiences since it takes more time to do that and I'm also concerned about the audience guardrails.I don't want to have to create a custom event since it's more time consuming and requires different roles/competence/AJO permissions to do. How would you like the feature to workI would like to use attribute as exit criteria by using operators to either say that the attribute should equal a defined value or be more/less than a defined value or be compared to another attribute or to a certain date or time. Also, being able to say that if a profile's attribute changes in any way from the time the profile enters the journey, then the profile should exit the journey.

DescriptionI think it would be a huge improvement to the email designe if we could ensure that elements in the email is mso optimized WITHOUT breaking the visual editor. For a lot of companies, it is not necesarrily developers who work with the emails and thus a visual editor is needed for flexibility in the workflow. However, the visual editor will break as soon as you start to change anything in the source code thus leaving you unable to ensure mso optimized CSS as well as favicons and other stuff.  This is important since it will allow for a stronger use-case of the visual email editor and ensure democratization of the email design role (in my opinion).   I imagine this feature to work in a few ways: Make sure that email designer itself adds mso optimized css lines OR allow to split html and css so that you can code the css yourself but stay in the visual editor.  Currently, if we try change minoir things such as mso tags or favicons we are forever

To be able to maintain and change item used in emails from a centralized place it would be nice if we can be able to use Email Fragments into other Fragments. It you create a button that is common to use or f ex a table of Social Media symbols with links that you could and would like to use in different context in a different setup - regarding the mail that you are sending. Standard fragments like buttoms, social media symbols and links, could be stored and used into other fragments (that is the one yoy actually drags and drop when you create a new email). When a symbol or a button color must be changed you can just go into that one "small" fragment - change it, and the change is replicated into all the fragments where this is used. Nesting of standard items (fragments) to be used as building blocks in other segments will lift the email possibilities a lot. And the maintains will be must easier it we can centralized some building blocks common used. <It is like HTML and CSS - make c

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

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

Description - Provide a tool similar to Drift Email OR change the DNS structure to allow Drift Email to plug into the email engine like it does with Marketo   Why is this feature important to you - We handle 100k replies a month automatically with Marketo+Drift Email to ensure compliance as well as route Humans back to sales reps. Works VERY well. It has saved us thousands of hours of rep and team time (60k/yr).   AJO does not provide this because of the use of CNAMEs which breaks Drift Email and causes other issues with setup. Current offer to forward replies to an email box at ringCentral does not scale. We don't have 20 people to filter through the replies every day. In addition, if we send on behalf of sales reps, they would all get the OOO and bad replies which makes them angry and wastes their time.   How would you like the feature to work - Change DNS structure to allow Drift Email https://www.gethelp.drift.com/s/article/How-to-Integrate-Drift-with-Marketo https:

Description When we create a segment, we have to wait till the next day till the segment is filled. But many times, we actually want to use the segment instantly and check the number of customer profiles in the segment. The only way to do this quickly now is to do an API call, but that's not a marketeer-friendly solution. We would expect a button to build up the segment instantly or for it to be done by saving the segment, as available in other (ESP) software.  Why is this feature important to you  To be able to work fast with segments and don't have to wait days. If you now create a segment and make a small mistake, you probably discover it the next day. But then you change it and have to wait another day till the segment is filled again.  How would you like the feature to work - Instantly build the segment instead of doing one batch a day, or have a button do the batch right away.     

Description - I would like the option to have one step in a journey where customers are entering into a segment or exiting from a segment from this step. Why is this feature important to you - This would help with orchestrating the journey so customers could at some point (depending on previous steps) enter into segment as part of the journey and that segment could then be used to trigger another journey or offer. I've used this feature in other tools and I find it very handy to connect journeys to each other at different points in time. They could also enter into a segment which excludes them from all email communication for X time for example, and then exit that segment whenever the journey says so. How would you like the feature to work -  1. I would like to have a node/step in a journey that only adds customer to a segment. The segment in itself is only set to accept customers coming from a journey and doesn't have any further requirements when being built.  2. I would l

Basically, this feature allows you to make modifications to a launched Campaign while messages are in the process of being deployed. These changes will then be applied to all un-sent messages.   Think about we realize that we need to modify the subject line for some reason or any other content, we would suspend the Campaign then change the subject line and run the campaign again with the Pick Up Changes option.   That would avoid to cancel the campaign and create a new one.   Also, the only exception to this rule can be an Event-triggered Campaign. In that scenario, we wouldn't need to first suspend the Campaign before running Pick Up Changes.

Once a journey or a Campaign has been launched, it would be of a great help to have the info of the process until is completed.   E.g.    Message Creation             START               FINISH           COUNT                                         DD/MM/YYYY    DD/MM/YYYY   ###   Content Calculation           START               FINISH           COUNT                                         DD/MM/YYYY    DD/MM/YYYY     ###   Personalization                  S

  Hi, I see we have a need to change when and how often a Journey is scheduled after it has been published. Insted of having to create a new journey just to change when journey is set to schedule, with all the impact it has to current profiles in the journey. I would like the possibility to change when and how often a published journey is scheduled. Example: from As soon as Possible to Daily at 10 PM, or from Weekly Mondays to Weekly Tuesdays   A scheduled journey, is a published journey, so today to make a change to a scheduler I need to create a copy or a new journey version.