Marketo Release Notes | 2025-08

What do the 2025-08 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 – Reporting: Email Performance and Email Link Performance reports now show data from emails created using the new Email Designer.
• Email Designer – Autocomplete Removal: The Autocomplete option in the token personalization editor was pointing to erroneous objects and has been removed. There are no plans to reimplement it at this time.
• Email Designer – Email Preview Optimization: Some users were experiencing slower load times when trying to preview their email in the email/email template/fragment details page. This experience has been optimized for up to 60% faster load times.
• Email Designer – Template Fixes: Some out-of-the-box templates were having rendering issues (e.g., not rendering correctly on certain browsers/dark mode, images misaligned, CTA buttons misplaced, and a few more). These are all fixed with this release.
• Email Designer – Content Locking Fix: Previously, if an email template was created with content locking and the template was used to create an email, content locking would persist even when the email was reset or "change design" was selected. This issue is fixed with this release.

Announcements

• 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 reporting for the new designer finally closes a basic operational gap: you can measure performance without keeping separate reporting habits for old and new email tools. That matters if your team is migrating templates or standardizing on the new editor, because it reduces shadow reporting and manual reconciliation. Still, check whether your dashboards, naming conventions, and attribution logic line up before you trust the numbers.

Autocomplete removal is a small but useful cleanup. If it was returning the wrong objects, removing it is better than leaving a misleading helper in place. The downside is less convenience for token work, so your admins may need stricter token governance and more disciplined validation to avoid broken personalization.

Preview speed improvements and template fixes are mostly productivity gains, but they matter in high-volume operations. Faster previews save time for campaign builders, especially when multiple reviewers are iterating on emails. Fixes for browser, dark mode, image, and CTA rendering reduce launch risk and rework. The business value is real, but only if you update or re-test shared templates rather than assuming legacy assets are safe.

Content locking behavior is now corrected, which is important for teams using controlled templates. Broken locking after reset or design changes can create hidden governance issues and unexpected edits. This fix helps protect brand consistency, but you should still review template inheritance rules and permissions so content control is intentional, not accidental.

Adobe Identity migration is the major operational priority. If you miss the deadline, access disruption is a real risk, not a theoretical one. This also affects login governance: IP restrictions and Marketo Identity SSO are being retired, so your security model needs redesign inside Adobe Identity and Admin Console. Treat this as a project, not an admin task. It touches user access, SSO, security policy, and support readiness, and it should be tested well before the cutover date.