Release Notes: October 2024 release-notes-oct-24
Below you’ll find all the features included in the October '24 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 October 4, 2024, 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.
Announcements announcements
-
Bulk Extract API Update: We fixed an issue in the Bulk Extract API involving the columnHeaderNames option, which lets you specify custom column header names in the exported file. Previously, column header names containing non-ASCII characters could become corrupted.
-
Rest API access_token Parameter Deprecation: The ‘access_token’ query 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.
-
QR Code Deprecation: On October 4, 2024, the QR code feature used in push notifications and in-app messaging assets will be deprecated. This includes using QR codes for a new test device, as well as creating new assets with QR codes. Deprecating features with lower usage allows us to reallocate their resources to the overall maintenance of Marketo Engage.
-
Munchkin Changes
-
New Version: On September 17, 2024, Munchkin v.164 will begin rolling out to Marketo Engage instances that have the “Munchkin Beta” setting enabled in Admin > Treasure Chest. It’s scheduled to begin rollout to all other instances on October 29. This version updates Munchkin cookie creation. There are no changes in functionality.
-
Characters from URL Removed: ‘Visits Web Page’ and ‘Clicks Link’ activities created by Munchkin JS will now remove non-URL encoded control characters from all URL fields. This change is designed to prevent errors related to propagation of those types of characters into systems that don’t support them, and don’t have a valid use within Marketo Engage.
-