Release Notes: May 2025
- Topics:
- Release Information
Below you’ll find all the features included in the May '25 release. Check your Adobe Marketo Engage edition for feature availability.
The Release Notes specifically for Adobe Dynamic Chat can be found here.
AVAILABILITY
Standard Release Cycle Features
The following features fall under the standard release cycle and will start to be released on May 23, 2025, 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.
| Feature | Status | Documentation |
|---|---|---|
| Template Compatibility for Email Designer: Email templates from the classic email editor are now compatible with the new Email Designer. | Coming Soon | Coming Soon |
| Trigger tokens for any attribute: Expanded list of trigger tokens to support using data from any activity attribute in Smart Campaign fields. | Coming Soon | Coming Soon |
Announcements
- New Analytics Feature - Public Beta: Advanced BI Analytics (formerly known as Revenue Explorer and Advanced Report Builder) began rolling out to all current Revenue Cycle Explorer users in mid-April. This new tool offers a flexible reporting and visualization interface on Marketo Engage data, providing granular details about progression, performance, and more. It features richer interactivity and visualization, faster performance, and a more seamless and intuitive user experience.
To access this feature, you must have purchased the Advanced BI Analytics add-on. Please contact the Adobe Account Team (your Account Manager) for details.
-
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 June 30, 2025. 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 Oct 31, 2025. Services which use SOAP API capabilities should be migrated to the REST API.