Adobe Marketo Engage Classic Experience and Toggle Switch Deprecation for Select Design Studio Assets

[ndalvi]

After March 24, 2023, access to the Adobe Marketo Engage classic experience for the following Design Studio assets along with the ability to toggle between classic and the modern “New Experience” will be deprecated from all Marketo Engage subscriptions as we focus on delivering our modern user experience to all our customers:

1.  Landing Pages (List and Details View Pages)

“Publish to Facebook” functionality in Landing Page Assets is also planned to be deprecated. 

We have already brought some of our most popular Marketo Sky innovations to our modern experience and ensured that all the capabilities in the classic experience are available in the modern experience. And the response to the modern experience has been positive till now.

As Marketo Engage gravitates towards redefining the way marketers conduct their daily activities with higher productivity, improved ease of use, and optimized workflows, we would like to transition the user experience completely to the modern experience in a phased manner. This announcement is the first of many we will broadcast in this community as Adobe continues to help marketers succeed. 

Stay tuned for more exciting modern experience developments throughout Marketo Engage and help us with any feedback to improve your experience.

[ovhcloud_bg]

We are consistently getting errors about the time stamps when we switch from the classic to the new experience.  Is there a fix for this? 

[ndalvi]

Thanks @ovhcloud_bg for highlighting this. Is there an action that has been done on the dates before the switch post which you notice this. I am trying to get this reproduced so any indications on the actual scenario would be helpful to reproduce, debug and provide a solution.

[ndalvi]

@ovhcloud_bg I checked with the team internally and identified that this error occurs because of an invalid date has been set in the previous Marketo experience. Could you please check the date that you have inserted in the old experience is valid and if you correct it, the same gets reflected in the new experience and you get rid of the error? If that is confirmed, then our Modern UX experience does have proper error checks to avoid such date errors and once the old experience is removed, you wont face this error. Please help get back with any updates on this issue so that we can close the investigation that we have been doing internally. Thanks for highlighting this.