Release Notes: January 2026 release-notes-jan-26
Below you’ll find all the features included in the January '26 release. Check your Adobe Marketo Engage edition for feature availability.
The Release Notes specifically for Adobe Dynamic Chat can be found here.
Standard Release Cycle Features standard-release-cycle-features
The following features fall under the standard release cycle and will start to be released on January 30, 2026, with a phased rollout of remaining features over the subsequent weeks. Release features and dates are subject to change. Please check next to each feature for its status.
Non-Standard Release Cycle Features non-standard-release-cycle-features
The following features were released outside of the standard Marketo Engage release cycle.
Interactive Webinars interactive-webinars
-
Survey Pod: A new Survey Pod allows hosts to design and deliver structured feedback forms directly within a live session.
-
Resources Pod: The new Resources Pod replaces the previous Files and Web Links pods, providing a single, unified way to share resources during live sessions.
-
Enhanced Room Interface Experience: Enjoy a refreshed and more modern room interface, built on Adobe’s latest Spectrum 2 design framework, aligning with the visual language used across other Adobe products such as Creative Cloud and Experience Cloud.
Visit this page for full details.
Announcements announcements
-
Marketo Community Migration Complete: The new Adobe Experience League Community is now live! Several enhancements have been made to make your Marketo Community experience even better. Check it out.
-
Rest API ‘access_token’ Parameter Deprecation: The
access_tokenquery parameter used to authenticate Marketo REST API calls is being deprecated and will not be available after March 31, 2026. All new and existing integrations should authenticate REST API calls using the ‘Authorization’ header, as described here. -
SOAP API Deprecation: Support for the Marketo SOAP API will end on March 31, 2026. Services which use SOAP API capabilities should be migrated to the REST API.