Marketo Release Notes | 2025-10

What do the 2025-10 Marketo updates really mean for your team?

We break down what matters, what to act on, and where it impacts your marketing operations.

Features

• Email Designer – Template Importer (Beta): Import email templates from the classic email editor to create templates compatible with the New Email Designer in the Design Studio. Template import
• Email Designer – Brand Themes: You can now define brand themes within Marketo Engage. Styling configurations can be reused and applied across email templates and other email assets for brand consistency. Brand themes
• Email Designer – Conditional Content: Parity feature for the new Email Designer, allowing you to achieve email personalization beyond tokens. Conditional content
• Email Designer – Image to HTML Converter: Upload a compliant PNG/JPEG image file of an email and it will automatically be converted into HTML for use in the new Email Designer. Convert images to HTML templates
• Email Designer – Clone Email Action: You can now clone an email into another program folder in Marketing Activities and quickly reuse existing emails.
• Email Designer – A/B Testing: Parity feature for the new Email Designer, allowing you to perform A/B tests to see which types of content receive the best response.

Announcements

• Salesforce CRM Integration Upgrade: A new version of the native CRM integration will be deployed to active sandboxes that have the native connector enabled over the course of seven days, beginning November 13, 2025. Get full details in this Community post

• REST API Double Slash Deprecation: On September 16, 2025, Adobe transitioned to a more modern hosting infrastructure for REST API URLs that leverages newer technology, adding security and scalability. If your subscription has been using APIs with a double forward slash (https://experienceleague.adobe.com//?lang=en) in the URL, please read this Community post for next steps.

• Switching Back to Velocity Scripting in the new Email Designer: Adobe Marketo Engage released a feature called Conditional Content for the new Email Designer this past June. The feature was powered by Handlebar scripting instead of Velocity scripting, in an effort to provide a little more flexibility in your dynamic content. But when we discovered it was causing some tokens to be resolved incorrectly, we decided to temporarily disable it. Learn More

• Marketo Engage Identity End of Life: In August 2025, Adobe began phasing out support for Marketo Engage Identity (logging in via login.marketo.com). To prevent interrupted access to Marketo Engage, you must transition to Adobe Identity no later than September 30, 2025.

  • IP Restrictions Deprecation: Support for Restricting Marketo Logins Based on IP ended on July 30, 2025. The feature will remain operational until the transition to Adobe Identity is complete. A new location-based access control feature for Adobe Identity in the Adobe Admin Console is coming soon.

  • Single Sign-On (SSO) Deprecation: Support for Marketo Identity SSO ended on July 30, 2025. The feature will remain operational until the transition to Adobe Identity is complete. Single Sign-On for Adobe Identity in the Adobe Admin Console must be configured separately. For setup steps, see Set up identity and Single Sign-On.

What this means for you and your team

Email Designer template importer is mostly a migration aid, not a strategic capability. It reduces rework if you still have legacy templates, but you should treat it as a cleanup project: validate rendering, tokens, and modular structure before scaling. Good for faster adoption of the new designer; risky if you import outdated design debt.

Brand themes is a meaningful operational win. It centralizes styling and can cut repetitive template maintenance across regions, business units, and campaign teams. This helps governance and brand consistency, but only if you define ownership and change control; otherwise, one theme becomes a shared point of failure.

Conditional content and A/B testing bring the new Email Designer closer to parity, which matters if you’ve delayed adoption because of missing functionality. Conditional content can reduce token sprawl and improve relevance, while A/B testing supports better optimization. Still, keep the logic simple and document it well to avoid hard-to-debug personalization and inconsistent results.

Image to HTML conversion is useful for accelerating template rebuilds, especially during migration projects, but it is not a substitute for proper email engineering. Expect cleanup work, accessibility checks, and responsive QA. The real value is speed; the limitation is that messy source assets usually produce messy output.

Clone email across folders is a small but practical productivity gain. It helps teams reuse approved emails without recreating them, which is useful for complex folder structures and distributed teams. The governance risk is version drift, so you still need naming standards and clear ownership of master assets.

Salesforce CRM integration upgrade is the most operationally important announcement. Any connector change can affect sync behavior, field mappings, campaigns, and downstream reporting, so test in sandbox before it reaches production. Use this as a chance to review sync dependencies and document fallbacks.

REST API double slash deprecation is a technical housekeeping issue, but it can break custom integrations, scripts, or middleware if you’ve hardcoded old URLs. Audit API usage now rather than waiting for failures. This is a good reminder that platform stability depends on disciplined integration hygiene.

Velocity scripting rollback shows the new Email Designer still has maturity gaps. If you relied on conditional logic, you need to confirm what actually works today and what has been disabled. The lesson is to avoid overcommitting production workflows to newly released features until behavior is stable.

Adobe Identity migration is the biggest governance and access-control change. If login, SSO, or IP restrictions are not handled properly, your team can lose access or create security gaps. This is less about marketing performance and more about business continuity, so coordinate admins, security, and IT early.