Marketo

As of the October 2026 release, the Adobe Marketo Engage Email Designer possesses nearly all of the core capabilities of the old editor, while boasting powerful new features like AI assistance, Image to HTML, Brand themes, and more. This is a big milestone, as now all users can confidently utilize a Designer that expands email creation functionality, integrates with modern tools, and enhances collaboration. Shared capabilities Let’s take a look at what features can be found in both the new Designer and the classic editor.   Feature Description Classic editor Email Designer Starter templates Out-of-the-box templates to jumpstart campaigns. ✔️ ✔️ Saved templates Reusable designs for efficiency. ✔️ ✔️ Use/create emails in programs Create email assets for specific programs outside of the Design Studio. ✔️ ✔️ Preview/send sample See how emails render before sending. ✔️ ✔&

In case you missed it, here's a recording of the new Email Designer Office Hours on August 27th, 2025.   This session introduced the AI Assistant for content generation in the new Marketo email designer. We demonstrated how to create full email bodies, subject lines, and preheaders using uploaded brand assets (PDFs or content briefs). The walkthrough showed how prompts, tone, and persona targeting shape AI-generated content and how marketers can iterate, rephrase, and refine outputs. The team addressed questions on sending proofs, testing workflows, using brand guidelines for tone and style, inline CSS customization, and HTML editing. Upcoming features like spam scoring integration and background image layering were also previewed.    AI-Generated Timestamps  Introduction and AI Assistant Overview 1:31  Uploading Brand Assets and Context Files 5:00  Generating Email Body Content with Prompts 8:40  Editing Text, Images, and Iterating on

In case you missed it, here's a recording of the new Email Designer Office Hours on Sept 10th 2025.   This session focused on content locking and governance in the new email designer. We demonstrated how to control edit permissions using fragments and templates, showing how admins can lock logos, headers, and footers while allowing limited edits to text or URLs. We detailed the difference between fragments (reusable modules) and templates (master layouts), explained governance options like “editable content only” vs. “read-only,” and clarified how changes propagate. The Q&A covered module migration, dynamic content rollout, HTML component locking, and upcoming reporting and cloning improvements.    Chapters  Introduction and Poll on Adoption 0:40  Creating Fragments and Enforcing Governance 2:30  Editable Fields and Locked Components 9:00  Publishing and Reusing Fragments 13:00  Creating Templates with Conte

In case you missed it, here's a recording of the new Email Designer Office Hours on Oct 8th 2025.   This session introduced two major enhancements: dark mode support and the new collaboration workflow in the Marketo email designer. Product development demonstrated how users can preview and define custom dark mode styles, toggle between light and dark mode, and adjust individual component colors. We clarified client compatibility (Outlook, Gmail, Mac clients) and best practices for logo visibility. The collaboration workflow demo showed how to tag teammates, add threaded comments, resolve discussions, and receive notifications via email and Marketo Pulse. Additional Q&A covered A/B testing timelines, dynamic content rollout, known Outlook bugs, and deprecation timing for the classic editor.    AI Generated Timeline  Welcome and Agenda Overview 0:09  Poll on Editor Adoption 2:32  Dark Mode Feature Overview 5:44  Editing

In case you missed it, here's a recording of the new Email Designer Office Hours on Nov 5th 2025. The session walked through the newest capabilities in the Marketo Engage Email Designer, including a live demo of Conditional Content alongside updates like Template Converter, A/B testing support, Brand Themes, and Image-to-HTML generation. See how these features streamline personalization, speed up production, and improve governance for modern email workflows.   AI-Generated Summary:   2:30 – 16:30 | Conditional Content (live demonstration) Walkthrough of how to enable Conditional Content on an email block and create multiple variants. Demonstrated selecting segments for each variant, adjusting images/content per variant, and understanding top-to-bottom execution order with a default fallback. Emphasized parity with V2 Dynamic Content but redesigned in a new, more intuitive UI. 16:30 – 23:30 | Conditional Content Q&A Covered how variant testing works through

What if I told you that you could generate a brand-compliant email template in seconds by simply uploading a screenshot? Well, thanks to the latest release in both Marketo Engage and Journey Optimizer B2B Edition, Marketing Ops can do just that.    Creating and updating branded email templates has always been a critical part of the campaign creation process. Yet, for many marketers, this process has historically been time-consuming and resource-intensive, often requiring manual HTML coding or reliance on agencies and IT teams. These traditional methods not only slow down campaign execution but also consume valuable budget and resources.    The new Image to Template feature transforms the way Marketing Ops build email templates. Instead of spending hours coding or outsourcing, you can now convert design files, such as screenshots, into brand-compliant, editable HTML templates in seconds. No coding. No waiting. Just instant results.     With drag-and-dr

    For those of us in marketing operations who are wired to crave efficiency, governance and time-saving techniques, Marketo Engage tokens have always been a critical part of our process. Until recently, tokens could be created at a local (program) level or at the folder level within Marketing Activities. Fast forward to today, in addition to still having your tried-and-true local tokens, you now have the ability to create instance-wide tokens that can be applied across any program or folder!    You can add and edit global tokens by going to the Admin tab, navigating to the left-hand side navigation tree and clicking My Tokens. Here you can drag, drop and edit token types, names and values to your liking. Note that you have to have admin permissions to access this. These tokens will now be available to use in any program when navigating to the program itself and clicking on the My Tokens tab.    When creating a global token strategy you'll want to think o

When our Adobe leadership first encouraged us to use AI in our work, I was hesitant. I’m no Luddite – point me at any new gadget or a cool app that I can use in my job to make things easier, faster or just more interesting! So, it wasn’t a “resistance to change” thing. And I’m reasonably confident I’m not contributing to the creation of time-traveling cyborg assassins because I’m embracing AI prompts in the 2020s. (Don’t come at me, SkyNet.)   So what was causing me to drag my heels about AI as a tool?   It felt like…cheating. So – and part of using AI ethically is to be transparent about it as a source – I asked the AI tool that we use here in Adobe why using AI feels like cheating. It’s one of the first prompts I used. And its answers were illuminating to me: Cultural norms value hard work, skill, and effort; using AI to improve efficiency may seem like it skips these steps, even when thoughtful decisions are still involved. Uncertainty About Ownership: “When AI aids idea

As part of Marketo Engage's migration to Adobe Identity Management System (IMS), the product URL has changed and now includes a different domain: Old Domain: xxxx.marketo.comNew Domain: experience.adobe.com   Why This Matters Depending on how your VPN or proxy is configured, your network may dynamically assign a different source IP address based on the destination URL. Because the destination domain has changed, your previous routing rules may no longer apply—resulting in a different source IP being used than before the migration. This becomes a critical issue when IP restrictions are enabled, potentially blocking users from accessing Marketo Engage.   What You Should Do To ensure consistent access and avoid disruptions: Inform your IT department about the domain change. Review and adjust VPN/proxy settings so that the same source IP address (as pre-migration) is assigned when accessing: experience.adobe.com Other Marketo-related domains This will help maintain

Earlier this year, we posted that a newer version of the native CRM Integration daily synch component was on its way. After a brief delay, we would like to inform you that this version will be deployed to active sandboxes that have the native connector enabled over the course of seven days, beginning November 13, 2025. Once all active sandboxes are deployed, there will be a phased approach for Production instances where the newer version will be deployed as a limited GA plan, starting November 25.   Is there anything we need to do in order to deploy the newer version? There is nothing you need to do. It will be deployed directly to your subscription.   Is there any new functionality that will be offered with the new version? This version is a technical upgrade and offers the same functionality as the previous version. The key benefits are improved performance and efficiency.   Can we choose to opt out of the new version? No, this new version applies to all subscriptions.

Popping up different Dynamic Chat dialogues for known SFDC Contacts vs. SFDC Leads is a basic ask. It’s a smidge trickier than you might expect, though, for 2 reasons:   (1) you can’t sync SFDC Type from Marketo to the DC database(2) you can’t sync SFDC Is Deleted, another key component   Don’t worry, it’s still easy.   Mirror SFDC Is Deleted Create a custom Boolean field SFDC Is Deleted Mirror. Keep that field updated with a simple trigger campaign:   Sync SFDC Contact ID, SFDC Lead ID, and the new mirror field With the mirror field in hand, you have everything you need to reproduce SFDC Type in Dynamic Chat:   Build your audience criteria Now you can match SFDC Contacts:   And SFDC Leads:   Not too intimidating, right?  

The Forms 2.0 lightbox() method is fully functional, but commonly misused.[1] I’ve had a post in my drafts for ages — “Tips for a smoother lightbox() experience” — but in the meantime lightbox() has become unnecessary because all modern browsers support <dialog>.   IMO, the coolest things about <dialog> are: its built-in responsiveness: desktop and mobile browsers automatically position the modal correctly its native controls: the Escape key and back-swipe both close the dialog its easy styling: transform ::backdrop with any CSS properties   Secondarily, <dialog> minimizes the need for JavaScript. The JS in this post is only necessary because Safari doesn’t support Invoker Commands yet. In Chrome and Firefox, you can close and open the modal using HTML alone, no extra JS!   Here’s a modal Marketo form inside a <dialog>:   The markup is amazingly simple, just put the standard form embed inside a <dialog> and add a close <button&g

If you have migrated to the new Marketo IMS (Identity Management), you may have started to notice something: Many new features are getting unlocked to you as an admin user.  I am certain that you, like me, are excited about some of these new features we are seeing from Adobe that are making our lives as admins and marketers easier.   One of these features that has been unlocked is a “Merge Fields” feature.   When I first discovered this new Merge Fields feature, I became instantly excited because one of the issues that we have had as Marketo Engage Admins is with duplicate and/or extraneous fields.  Duplicate fields can result from a number of sources, such as errant Salesforce field setup, lax Salesforce admin field level security settings (many of which are unnecessary and can cause sync backlog issues), bespoke field additions, or fields created for prior use cases that are no longer needed.     Prior to this feature being launched, we faced

Join us for this AMA on December 3rd, 2025, from 9 AM PST to 10 AM PST, as our expert Ather R. (@Ather01) answers your burning questions about keeping your Marketo Engage database clean as Salesforce CRM Integration is being upgraded!   RSVP NOW   As a Marketo Engage admin, you know the challenge: your database needs to stay pristine and your Salesforce CRM integration needs to work flawlessly to meet the demands of both marketing and sales. When your data quality is solid and your sync is healthy, everything flows better—leads move faster, pipeline grows, and deals close quicker.   Bring your toughest database and sync challenges to this interactive Q&A session and get real-time answers from our Product team, who know the ins and outs of the Salesforce CRM integration upgrade.   Here are some example questions to give you an idea of what we'll discuss: What CRM features are you planning to add or improve upon? How much data hygiene should be done in Sales

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. While our engineers have been retooling the functionality, we made the decision to switch the scripting back to Velocity. Not only will this speed up the feature’s return, but recent feedback has shown us that the majority of users who utilized the new feature preferred the ease-of-use and workflow familiarity afforded by Velocity. We hope this change encourages adoption and simplifies the transition between the legacy email editor and the new Email Designer. Any tokens that currently utilize Velocity scripting will continue to work without interruption. Conditional Content for the new Email Designer is scheduled

Violating the old Never Rewrite From Scratch rule (which, let’s be honest, is sporadically enforced) Microsoft created New Outlook in 2023. So far, it’s been a rocky rollout, with scant rewards for end users and mixed results for MOps.   On the bright side, email designers like the new rendering engine. You still need fallbacks for Classic Outlook, but more and more Microsoft shops will see your special effects. On the other side, the death of OFTs is pretty bad, but at least that’s a clean break.   More insidious are features ported over from Classic but subtly “fixed” in a non-backward-compatible way. Case in point: Microsoft decided to rewrite their iCalendar (ICS) parser. The new parser hews so tightly to the standard, RFC 5545, that previously supported ICS files now don’t show the Location field:   The specific area Microsoft fixed was the order of VEVENT properties and VALARM reminders. The standard is unequivocal here. A valid VEVENT must have its eventprop en

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 (//) in the URL, you should have received the following alert in Marketo Engage, with a Learn More link:   It is possible not everyone received or noticed the alert, as we recently discovered some existing API URLs have been generating 500 server errors, due to the API call itself. If you were affected by this, to resolve the error, you must modify the URL of the API call to change the double slash (//) to a single slash (/) where applicable.   Which API endpoints are impacted and should be modified?Any Marketo REST APIs that include a double slash (//) in the URL. What happens if we didn't make any changes prior to the deprecation date?Those specific APIs will fail; data synchs, Lead updates, or Campaign Triggers (depending on thos

Marketo’s new email editor is here—and it’s packed with features designed to make email creation smarter, faster, and more flexible than ever. In this article, we will explore what’s new to the designer and what’s coming soon. Here’s what you need to know.   ✨ AI Assistant: Smarter Email Creation The headline feature is the AI Assistant, powered by Adobe’s proprietary GenAI. This tool helps users generate everything from subject lines to images and full email content. You can tailor prompts for specific buying groups, marketing journey stages, communication strategies, and tones. Want a subject line with FOMO and an emoji? Just ask. Need content for decision-makers in an informative tone? The AI Assistant delivers. Key points: AI Assistant is currently English-only, but support for other languages is planned. You can use prebuilt prompts or customize your own. Text settings allow for deep personalization by audience, journey stage, and tone. Image generation is availa

If you’ve ever tried to include an “Add to Calendar” link in a Marketo Engage email and ended up with a broken calendar file, you’re not alone. One of the most common culprits? The {{member.webinar url}} token inside the Calendar File token type. It’s a subtle issue, but it can derail your webinar experience if not handled correctly.     Let’s break it down. The Calendar File token is a handy way to let registrants add your webinar to their calendar. It can include other tokens, like the webinar join link, so recipients have everything they need in one click. But here’s the catch: that join link token only resolves when the email is sent via a triggered smart campaign. If you send it manually or through a batch campaign, the token doesn’t populate. The result? A calendar file with a blank join link. Not ideal.     So how do we fix it? The answer lies in a simple program design tweak: create a smart campaign with a “Campaign is Requested” trigger. This campaign bec

A user had buggy 3rd-party JS causing forms to be submitted 2x. Unable to find the root cause in their stack of plugins, they tried a desperate fix: add an onSubmit() listener and stop submission if the listener runs a second time.   Like so: MktoForms2.whenReady(function(readyForm){ let stopFutureSubmissions = false; readyForm.onSubmit(function(submittingForm){ if(stopFutureSubmissions) { return false; } stopFutureSubmissions = true; }); });   Fine idea in theory, but that’s not how you stop form submission. The Marketo onSubmit() listener stack doesn’t care if you return false from every single listener! That is, it’s not like DOM event handlers where return false is interpreted as canceling the event.[1]   To stop submission, assuming you have complete control over the listener stack, simply set form.submittable(false): MktoForms2.whenReady(function(readyForm){ readyForm.onSubmit(f

  Overview of the List Import Process   There are 4 key steps when importing a list into Marketo Engage: Prep your list/scrub the data outside of Marketo  Prep work within Marketo Import the list  Validate and QA   Step 1: Prep List & Scrub Data   Move your data into an evergreen list import Excel template for all imports that should be created by your admin. Admins: Include required and optional fields as columns, matching Marketo field names for easy mapping with... Mandatory fields (e.g., Email) should be clearly highlighted - lists cannot be imported without these values!  Exclude unsubscribe-related fields; ensure field updates are blocked on Trusted/Untrusted List Imports. Each column = one field; align with your data dictionary. Use dropdowns/picklists within the excel for consistency and ease of use to the end user (e.g., Boolean fields with “TRUE”/“FALSE” only Delete records without email addresses. Remove duplicates on your l

      In the world of marketing automation, data is everything. But not all data is created equal—especially when it comes to list imports in Marketo Engage. If you've ever wondered what the difference is between a trusted and untrusted list import, you're not alone. Understanding this distinction is key to maintaining data integrity, compliance, and campaign performance.   What Are List Imports in Marketo? List imports are one of the most common ways marketers bring external data into Marketo—whether it's leads from a tradeshow, webinar registrations, or from external systems. But how that data is treated once it enters your instance depends on whether the import is marked as trusted or untrusted.   Trusted List Imports A trusted list import is one where the data source is considered reliable and compliant with your organization’s data policies. These imports typically come from: First-party sources Known partners or integrations Internal teams with verified

10 Unique Marketo Token Use Cases You Might Not Be Using Tokens in Marketo are one of those features that seem simple on the surface, but the more you work with them, the more powerful they become. Most teams use them for basic personalization (like adding a first name in an email), but that barely scratches the surface. With a little creativity, tokens can save hours of work, reduce errors, and make your campaigns more scalable. Here are 10 unique and practical token use cases you might not be using yet. At their core, Smart Campaigns are rule-based workflows that allow marketers to automate actions such as sending emails, updating data fields, scoring leads, or triggering notifications.Think of them as the "if this, then that" engine of Marketo. Here are some common use cases: 1. Dynamic CTA Text in EmailsTired of rewriting the same button across multiple emails? Store your CTA text as a program token. Update it once and it changes everywhere. It’s also an easy way to test variations

Have you ever used Marketo Engage Program Member Custom Fields? How about syncing Program Member Custom Fields (PMCFs) to Salesforce Campaign Member Fields (CMFs)? Yeah, that’s a mouthful. In this blog post, we’ll cover the specifics of how PMCFs sync to CMFs, some key considerations, and expected behavior so you can take advantage of this new powerful feature.    Pre-Requisites  Enable the Salesforce Campaign Sync in Marketo Admin  Create Program Member Custom Fields in Marketo  Create Campaign Member Custom Fields in Salesforce – NOTE! These fields would live on the Campaign Member Object, not the Campaign Object. Think of it this way: the Campaign Member Object contains data pertaining to the Campaign Member Record (i.e. the Lead or Contact), whereas the Campaign Object has fields that relate to the Campaign itself.     Setting Up the Sync  With the above complete, you can now map Marketo Program Member Custom Fields to Salesforce Campa

Mark your calendars! On Wednesday, October 22 at 1 PM CDT, the San Antonio Marketo User Group (MUG) is bringing you a powerhouse session:“Building a Center of Excellence for the Year Ahead” led by none other than Adobe Champion Carissa Russell. Whether you're looking to streamline your Marketo instance, refresh your strategy, or set your team up for scalable success in 2026, this virtual meetup is packed with actionable insights. Carissa will share her favorite tips, tricks, and frameworks for building a Center of Excellence that drives results and empowers your marketing operations.   Register Here : https://mugs.marketo.com/events/details/marketo-san-antonio-presents-marketo-san-antonio-presents-building-a-center-of-excellence-for-the-year-ahead/