Adobe Marketo Engage

If you’re new to Marketo Measure and looking for a curated list of resources to help you get started, you’re in the right place 😀 Getting up to speed can feel overwhelming as there are plenty of help articles, documentation, and training materials available, but not all of them are essential when you’re just beginning. We recommend building a strong understanding of the fundamentals before diving further into the technical details. So, this guide narrows the focus to the key concepts you should review first. These resources will help you understand how Marketo Measure works, how attribution is structured, how data flows through the platform, and how to interpret reporting with confidence. Each link includes context on what it covers, why it matters, and what you’ll gain from it — so you can build clarity quickly and start using the platform with purpose!  Establish a conceptual, high-level understanding first: What is attribution? Start here for a stage-setting overvi

Marketo-integrated page builders like Stensul & Knak publish your pages as Marketo LPs. Published LPs fully support webfonts hosted in Marketo Design Studio, since they’re on the same domain. But what about inside the builder app, when you’re still previewing? There, you’ll have a problem. Even with the correct @font-face rule in your CSS, the font won’t load because of CORS restrictions:❌ Access to font at 'https://pages.example.com/rs/123-ABC-456/images/entypo.woff' from origin 'https://app.stensul.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.This is reasonable, of course. Marketo isn’t in the business of providing an easily abused font CDN to the public! There’s a slick workaround. You can’t control CORS headers, but you can (by definition) host a page with same-origin access to the fonts. By deploying such a page as a hidden IFRAME, you can shuttle the fonts to a parent page, even if the parent is on a differ

I created two versions of the same email: One using the old editor, built from my own custom template with HTML compiled from MJML One using the new WYSIWYG Email Designer The version built in the old editor is roughly half the size of the new one. With the new editor, I’m constantly hitting Gmail’s 100 KB clipping limit and having emails cut off, even when the visible content is minimal.What’s especially confusing is fragment behavior. When I update a fragment to delete content, the email actually gets larger, sometimes by 30 KB or more. From what I can tell, fragment updates are appending duplicate CSS and redundant markup instead of removing it.I’ve seen mentions that the old editor may be sunset in 2026, and I’m about to build a new nurture program. I’m concerned about being forced onto the new editor when it’s already difficult to keep emails under Gmail’s size limit.Am I missing something here, or are others seeing the same behavior with the new editor?

Marketo’s onValidate and friends stack like DOM event listeners: they run in the order they were added. But there are still major differences:In Marketo, the listener stack isn’t deduped. If you add the same listener function 3 times, it’ll run 3 times. In contrast, DOM addEventListener(event,callback) checks if the callback was already added and if so, doesn’t add it again. In Marketo, all listeners always run. There’s no short-circuit method like stopImmediatePropagation(). In Marketo, to stop submission you call submittable(). There’s no event-level preventDefault(). (Note onValidate — but only onValidate — respects the callback’s return value, kind of like DOM inline event handlers.)Adding (1) is an easy tweak that makes it a lot easier to manage advanced form behaviors with lots of coordinated components. Adding (2) is quite tricky[1] and I’ll cover that another day. Might even throw in (3).😏 We’re adding idempotence to the Forms JS APIIdempotence is a show-offy CS term for an ac

We started using Dynamic Chat and are finding some gaps in the reporting that we would love to have. Currently, the default just shows everyone that reached any goal within a dialogue. The issue is that 1 dialogue may have multiple different goals and not all are as  important as others (i.e. we have an MQL goal vs someone who is subscribing to receive content). We want to be able to see in the reports the conversations by goal to show over time how many people hit each different goal.What I’m also noticing is that the global reports are pretty good, but you cannot segment them at all by dialogue on that screen and it’s causing me to go into each dialogue to see it’s performance. I’d love a filter at the top for the different dialogues so you have it in 1 place and can view all the reports. I’d also like to have the ability to compare across different dialogues easier. For instance, we have so many people that engaged across all of our dialogues over time, but I’d like to see that 10 w

tl;dr: You gotta use the API to use the API. When browsing Marketing Activities, you’ll see the URL change to reflect Program IDs, Static List IDs, and Smart Campaign IDs:.../marketo-engage/classic/PG3350A1.../marketo-engage/classic/ST6331A1LA1.../marketo-engage/classic/SC9850A1ZN19In these cases, the first sequence of contiguous digits in the last path segment is the asset ID and can be used in the API. Above, you see Program ID 3350, Static List ID 6331, and Smart Campaign 9850. The structure works for Smart Lists as well. Other asset types like Forms and Emails also have their IDs in the URL. Not Campaign Folders, though!Selecting a Campaign Folder shows a tempting URL structure —.../marketo-engage/classic/MF2421A1— leading you to think the Folder ID is 2421. Nope, in this case 2421 is the “tree node” ID, which is a UI thing only. It’s not the same as the REST API Folder ID, which reflects the persistent structure in the database. Worse, the actual Folder ID 2421 can be located some

Modern browsers use the back/forward cache (“bfcache”) to accelerate simple ⇦ and ⇨ navigation. Confusingly, the bfcache is different from both the classic HTTP cache and the new Cache API, and its impact on 3rd-party JS isn’t widely measured. The bfcache is dynamically managed and cleaned up by the browser: it doesn’t have user-tweakable settings and can’t be directly turned off. There are also lots of different reasons that the same page might be bfcache-able on one visit but not on the next. This all gives the bfcache a black-box vibe. But the bfcache usually leads only to Good Things™ so people don’t worry about it, aside from some devs trying to make sites as bfcache-able as possible. Interestingly, Munchkin’s backward compatibility (pageview and link tracking still work with old browsers) conflicts with the bfcache design. This wasn’t deliberate, of course, but the product of different goals. In this recording, check out when visitWebPage and clickLink events stop being sent to M

Busy MOps teams use a URL builder to manage tracking params (and sometimes for add-to-calendar URLs and other areas). They have a UI like this: And generate a copy-and-pasteable URL like this:https://www.example.com/landingpage?baseparam1=value1&utm_campaign=nosferatrix-or-treat-2025&utm_medium=email&utm_source=marketo&utm_content=logo&utm_term=defaultSometimes they’re built using Excel or a Google Sheet (ugh) instead of a separate web app, but the idea is the same.Problem: most such builders have at least one fatal bug. They do not properly support Marketo {{dotted.token}} syntax in query param values. This is bad, since tokens are a huge operational benefit on their own. Let’s say you want to use the built-in {{campaign.Name}} as the utm_campaign value: A naïve URL builder will mistakenly think {{campaign.Name}} is a literal value, as opposed to an interpolated variable, and will URL-encode it, breaking the URL in Marketo:https://www.example.com/landingpage?basepa

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

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

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

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/

Last updated date: October 28th, 2025   Hi Marketo Engage Community,    If you are a Marketo Engage admin, look no further! We understand that you’re under constant pressure to keep your database clean, efficient, and ready to deliver on the expectations of both marketing and sales teams. That's why we developed this practical, peer-led session, focusing on proven strategies and actionable checklists to help you push clean, reliable data to CRM—accelerating pipeline velocity and boosting revenue.   Hear from Adobe Marketo Engage Champion, Miray Vu (@miray), to understand the critical role of database hygiene in syncing Marketo Engage with CRM and empowering your organization to close more deals, faster.   In this On-Demand webinar, you’ll learn about: Why data hygiene matters for CRM integration and how clean data impacts business outcomes. Options for building a sustainable data hygiene process using Trigger/Batch campaign or Executable campaign, and how to i

As you read on, you might think I’ve contrived a situation with an infinitesimal chance of happening in real life, just for the love of blogging. But this just happened to a user who posted on the Nation!   So here’s the weirdest Marketo Forms factoid you may ever learn: if the 20th field added to a form has an empty name, you’ll get this generic error on submit: And inspecting the HTTP 400 response shows: { "message" : "checksum invalid", "error" : true, "errorCode" : "400" }     Hold on, a form field can have an empty name??? Well, no. An <input name> and <input name=""> are both prohibited by the HTML standard. A native HTML <form> submit will not send values for those inputs.   But while Marketo forms use standard HTML <input> elements — a very good thing, I always take care to say! — the data that goes on the wire is assembled using JS. (Most modern forms do this.)   The Forms 2.0 API lets you add a hidden field with an emp

We're excited to unveil our most prestigious annual recognition - the Adobe Champion Program class of 2025-2026! This celebration honors expert practitioners worldwide, showcasing a diverse community of thought leaders who inspire innovation across our ecosystem.   The Adobe Champion Impact Adobe Champions transcend product expertise to become true change catalysts. Our program provides exclusive opportunities to collaborate directly with product teams, shaping application futures while building global connections with fellow experts through knowledge-sharing and thought leadership initiatives.   2025-26 Program Expansion Achieving Adobe Champion status represents exceptional achievement, with record applicant numbers making selection increasingly competitive. Our expert judging panel carefully evaluates candidates for this prestigious recognition. This year marks our grandest expansion, adding three additional program classes to create our most comprehensive Adobe Champion c

  Q: When will the new editor be supported in all programs, so I can clone and move local assets? A: Support for the new editor in all programs is planned for the first week of April 2025. Q: Are Snippets still relevant, or should we switch to Fragments? A: Fragments are designed for the new email editor and offer greater flexibility with customizable content. Snippets are still available in the current editor but cannot be used in the new experience. Q: How do fragments differ from snippets? A: Fragments are customizable and can be edited directly in an email, while snippets are static and cannot be edited within the email. Q: Can Fragments be shared across Workspaces like Snippets? A: Not at this point Q: How do I add editable fields? A: Editable fields are part of customizable fragments.   Q: How can I see if our instance has been migrated already to IMS?A: If you are logging to your Marketo instance from experience.adobe.com then your instance is migrated   Q: Can em

You see a series of Unsubscribe Email activities, roughly 5 minutes apart, covering more or less all the emails someone received:   Each one’s Details show they used the List-Unsubscribe header:   Turns out that’s standard behavior of the newish Manage Subscriptions feature in consumer Gmail.   When you go to Manage Subscriptions, Gmail shows you addresses that’ve sent enough marketing email to be trusted, which it then considers a “Subscription”:   Clicking on a Subscription shows emails from that sender that are still in your mailbox:   If you click Unsubscribe on the Subscriptions tab, Gmail visits all the List-Unsubscribe URLs in sequence, waiting 5 minutes between URLs to ensure it doesn’t exceed rate limits. This is mentioned, in a dumbed-down way, in the docs:   Since every Marketo email has a unique List-Unsubscribe header — if it didn’t, we couldn’t track Unsubscribe Email at the asset level! — all emails are individually unsubscribed. This