Release Notes: February 2026 release-notes-feb-26

Below you’ll find all the features included in the February '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 February 20, 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.

Feature
Status
Documentation

Email Designer - Folder Actions: Parity with the old email editor.

  • Share and archive folder actions for Email Designer assets.
  • Share folders across workspaces, right-click on a folder to create a new asset, move assets via drag-and-drop.
Released
n/a
Email Designer - API: You can now use API calls for the Email Designer.
Released
Marketo Asset API
Email Designer - AI Assistant Image Generation: Now, in addition to Firefly, you can use Nano Banana models to generate images with the AI Assistant for email content.
Released
Create content for a specific section of your email

Announcements announcements

  • SEO Feature Deprecation: On Tuesday, March 31, 2026, Marketo Engage will deprecate the Search Engine Optimization feature (SEO). If you don’t actively use SEO, you don’t have to do anything. If you have used SEO recently, you have the option of exporting your data. Learn more.

  • REST API Merge Leads limit: Beginning March 31, 2026, calls that include more than 25 IDs in the leadIds parameter of a Merge Leads API call will result in a 1080 error code, and the call will be skipped. Jobs requiring the merger of more than 25 records into one should be split into multiple jobs to ensure the success of those calls.

  • 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 July 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 July 31, 2026. Services which use SOAP API capabilities should be migrated to the REST API.

recommendation-more-help
94ec3174-1d6c-4f51-822d-5424bedeecac