Adobe Journey Optimizer

Description - To have a general error setup mechanisn where we can setup the users who should be notified in case of error. Why is this feature important to you - We can create custom action/activity at every stage in AJO journey design. But, it will be repetitive 'in case of error' configuration setup at every step in a journey.  There should be a general Admin setup available which notifies whenever there's an error.   How would you like the feature to work - 1) Create an option in Administration - Error Management. 2) Provide option to setup users who should be notified in case of error in a journey or campaign 3) Trigger email notification when systems runs into error. 4) Can provide OOTB email template or user can configure it.   Current Behaviour - Select option - 'In case of error' for each activity in a journey and define action to be taken.   Thanks, Jyoti

There is currently no option with a channel surface or email template to prevent additional channel surface applied URL parameters from being included in external domain based links.   For instance, we may wish to only have the additional automated parameters to be included with sender address based links and not externally facing links such as facebook.com.

Description: Being able to retrigger journeys for profiles where the previous instances have failed for whatever reason. With the event recording every single personalized attribute, these fields can also be retriggered.   Why is this feature important to you:  As of now we have a custom retrigger options with customer service without personalized fields. Whatever the reason might be a journey fails, it would be favorable to be able to just retrigger. Preferably when an event is triggered and a journey that is linked to that event is not triggered.   How would you like the feature to work: Overview of profiles who have an event on their profile but no journey that is linked to said event. Within the event there is the fields that are necessary that can launch the journey. Current Behaviour: Nothing happens with journeys that should be launched but are not.