Adobe Marketo Engage

Back in 2020 when I was at Etumos I took the time to document that new UI’s tree sort order which was included in this blog post. When trying to lookup the full list today I noticed that there are some characters that were overlooked in that blog and also one anomaly that was not documented. Enjoy!-,;:!?.'"()[]{}@*\&#%`^+<=>|~$000011aaab_____a_a*Note the oddity in “_a” not showing after “_” for some reason even though “a” is higher than “_” in the single character sort.

We have quite a bit of dirty data in our Marketo instance integrated with SFDC. While we establish internal alignment on deduplication logic to run via SFDC, we’d like a way to identify and segment Duplicates within our database. It seems the field “Duplicate Fields” is not available to be used within a segmentation. Could this please be reconsidered? Thank you, Raven McFarlane

Journey orchestration has become a fixture in modern B2B marketing language. Most organizations will tell you they’re orchestrating journeys across channels, personas, and lifecycle stages.But if you look past the terminology, something doesn’t quite hold up.What’s often called “orchestration” is still, in practice, a sequence of campaigns — connected, yes, but ultimately linear. Optimized for engagement. Responsive to individual actions. And only loosely tied to how buying decisions actually unfold.That gap shows up in a familiar way: marketing activity increases, but opportunity progression doesn’t keep pace.This isn’t a tooling problem. And it’s not for lack of effort.It’s a design problem.We’re Designing for Activity — Not for DecisionsMost journey orchestration models still follow a predictable structure:A person engages → enters a nurtureEngagement increases → score increasesThreshold is met → handed to salesFrom a systems standpoint, that’s coherent. From a revenue standpoint, i

Hey Marketo community! 😊I just dropped a post in the Certification Group for anyone prepping for the Marketo Master Architect Exam (AD0-E563), with some studying and test-taking strategies.I thought I’d share the link here too 👇Would love any questions or feedback from folks who have taken it or are planning to! Thanks!  

When adding a custom HEX code to a background color in the new Marketo builder, the editor does not apply the color; you cannot hit select/enter to apply the settings. The only way I have found to actually apply the settings is to paste the HEX code into the color block, then arrow up or down to change the color to an adjacent color, then return to the original color I pasted to get the color to apply.When applying a background color to a component using a HEX code, the change doesn't take effect automatically and we need to press the Tab key for the change to apply.This isn’t very intuitive and we would expect that hitting enter or selecting the value would automatically apply the custom Hex code for a background color.

I’ve been reflecting on how campaign execution has evolved in Adobe Marketo Engage — workflows are becoming more complex with advanced segmentation, dynamic content, and multi-step engagement programs.However, QA processes often still rely heavily on manual validation, checklists, and last-minute reviews.This makes me wonder:Are we underestimating the risk of QA gaps in campaign execution? How confident are teams in catching issues before launch (especially at scale)? Does manual QA still hold up for more complex engagement programs? How do you balance speed vs reliability in your campaign releases?We have built a solution that could reduce manual efforts and ensure quality campaigns. But before that just trying to understand how others in the ecosystem are approaching this and whether this is a growing concern.Would love to hear your thoughts and experiences.

Marketo’s hardcore rules for native Pre-Fill make sense, in particular stripping the mkt_tok query param so people don’t accidentally send their own personalized link to someone else. But there’s one hiccup in the native implementation — an inadvertent bug, since it has no privacy or security benefit — you can fix with a little JS. What’s the bug? Well, even when Pre-Fill works perfectly on an initial pageview:[1]initial landing: Pre-Fill works Just refreshing the page breaks it:after refresh: Pre-Fill disabled Now, the technical reason for this is clear: the always-added stripmkttok.js removed the mkt_tok for safety. (Which, again, is a good thing.) So upon refresh, the page no longer meets the prereqs for Pre-Fill. But the UX is a bit punitive. The person refreshing the page in their browser — the page that just included their data — isn’t expecting the data to be gone. Merely re-pre-filling the form after refresh doesn’t pose any risk, long as there aren’t any side effects. You may

Form spam is one of those problems every Marketo user eventually runs into. Bots fill out forms with nonsense data, junk email addresses pollute your database, and sales teams lose trust in inbound leads. The challenge is that most anti‑spam solutions trade security for friction—CAPTCHAs, extra fields, or aggressive validation rules that hurt legitimate conversion rates. The good news is that you can stop a large percentage of form spam without adding visible friction by using logic inside Marketo Forms 2.0 itself.One effective approach is to add lightweight screening criteria inside the Forms2 onSubmit function. This lets you evaluate a submission in real time before it’s officially accepted. You might check signals like suspicious email domains, mismatches between country and phone format, empty hidden fields that should contain values, or submissions that arrive faster than a human reasonably could. Instead of outright blocking these entries, you can quietly divert them into a secon

 Marketo Sales Insight (MSI) is one of the most powerful tools designed to give sales teams actionable visibility into lead behavior and intent—but most implementations fail to deliver value.Why? Because MSI isn’t a tool you simply “turn on.” It only works when:Your data is solid Your sales team actively uses itA successful MSI rollout goes beyond technical deployment – It requires:Data readiness System configuration Sales adoptionYou are essentially rolling out both a technology implementation and a behavior change program for sales.This guide outlines a practical, phased approach to help you implement MSI effectively.At a glance: MSI Implementation TimelinePhase 1–2: Strategy + Data Phase 3–4: Workflow + Setup Phase 5–6: Pilot + Training Phase 7–8: Rollout + Optimization Phase 1: Define Goals & Success Metrics (Week 0–1)To ensure a successful implementation, it’s important to start with strategy—not technology. Before configuring the integration, clearly define why MSI matters. K

 B2B marketing is in the middle of an important shift. For years, demand generation has been anchored in person-level engagement: lead scores, MQLs, nurture streams, and campaign performance. Those capabilities remain foundational. Engagement begins with individuals, and personalization at scale depends on understanding individual behavior.But enterprise buying decisions are rarely made by individuals. They are made by committees, cross-functional groups with distinct priorities, influence levels and risk tolerances. When marketing performance is measured only at the lead level, we risk mistaking isolated interest for collective readiness.The opportunity in front of us is not to abandon lead-centric marketing. It is to evolve it, connecting person-level engagement to buying group intelligence so that marketing can orchestrate consensus, not just capture attention.Engagement is personal. Decisions are collective.Every opportunity starts with someone. A technical evaluator downloads a wh

“We’re consistently seeing only one pageview per visit,” noted the Marketo admin. “We can’t be offending everybody, so maybe something’s up with our cookie banner?” She was right, people weren’t abandoning immediately. Rather, broken cookie consent JS was blocking the Munchkin _mkto_trk cookie for everyone, but not blocking Munchkin itself. How not to manage cookie consentThe code, like others of its type, was jaw-droppingly intrusive: it redefined document.cookie and proxied cookieStore to eavesdrop on set-cookie calls. (A crazy thing to just drop into a site, not that tricks used by other cookie apps[1] are much better!) _mkto_trk was on its cookie blocklist, but munchkin.js was always loaded + initialized. That leads to a half-baked outcome where:a person lands on the site from an email link, which attaches the mkt_tok to the query string to identify the Marketo record Munchkin generates a random session token value saving the token to a cookie is blocked by the consent JS the token

Get certified at Summit - we are ready with expanded testing capacity! Full passholders attending Adobe Summit 2026 can get certified for free by passing an on-site certification exam. All exams (except Adobe ColdFusion and Adobe Captivate) will be available. You may take as many different exams as you like, but you may not take the same exam more than once.  Testing hours are April 19-21 @ 9am-5pm PT and April 22 @ 8am-1pm PT. Seating is first-come, first-served. Find us at the Adobe Certification table on the 5th floor of the Venetian.  You must bring your own fully-charged laptop to take advantage of this offer. Free stable and secure Wi-Fi will be provided.  Learn more today! 

We appreciate the addition of Adobe Express image editing within Marketo Design Studio, as it enables faster, lightweight image adjustments directly in the platform.However, we’ve encountered two governance gaps that create risk for enterprise customers: No permission‑level controls There is currently no way to restrict or govern access to Adobe Express editing features by permission set in Marketo. This makes it difficult to limit usage to trained users or admins and to align with internal brand and compliance requirements. No in‑product warning about global image updates Editing an image in Design Studio updates that image everywhere it is currently being used (emails, landing pages, templates). This behavior is not obvious to users and can unintentionally alter live or previously approved assets. Requested enhancements:Add permission‑based controls to enable or disable Adobe Express image editing by role. Introduce a clear UI warning or banner when users attempt to edit an image t

This customer office hours session focused on addressing user questions and gathering feedback on the new Email Designer, with particular emphasis on template sharing, brand theme management, and known content structure issues. The discussion provided clarity on current system behavior while reinforcing the product team’s longer-term roadmap direction. AI Generated Timestamps:Welcome & Session Overview 0:08 Template & Brand Theme Sharing Across Workspaces 1:16 Fragment Padding Issues When Syncing Themes 3:10 Brand Themes as Independent, Shareable Assets 4:26 

This Marketo Engage New Email Designer Customer Office Hours session focused on discussing the upcoming Expert Code Editor capability and gathering early customer feedback. The session opened with an overview of the agenda and an emphasis on open dialogue rather than a product demo, followed by live Q&A.AI Generated TimestampsWelcome & Session Overview 0:08 Expert Code Editor :58 Troubleshooting & User-Reported Behavior 33:29 Publishing Unpublished Email Templates Issue 35:56 Wrap-Up & Next Steps 36:36 

This customer office hours session focused on helping users transition from the classic email designer to the new email designer, with particular emphasis on migrating existing email templates. The session addressed a key adoption barrier identified through customer feedback: the ability to reuse years of investment in legacy email templates.Welcome & Session Purpose 0:08 Introduction to Email Template Importer 0:12 Audience Poll: New Email Designer Usage 0:42 Customer Adoption Insights 2:04 Introduction to Email Template Converter Feature 2:43  Navigating the New Email Designer 3:10 Template Conversion Workflow Overview 3:54 Marketo Templates & Out‑of‑the‑Box Options 4:36 

This New Email Designer Customer Office Hours session focused on addressing customer questions and feedback regarding the new Email Designer, with heavy emphasis on migration readiness, feature gaps vs. the old editor, Outlook compatibility issues, and brand/theme constraints. Customers expressed both interest in the new experience and concern about losing advanced capabilities. The product team reinforced that adoption will remain voluntary, with a strong commitment to closing critical gaps before broader migration.AI-Generated TimestampsIntroduction & Office Hours Purpose 0:08 Template Sharing & Brand Themes Across Workspaces 1:16 Outlook Compatibility Issues (Buttons & Background Images) 26:59 Brand Themes vs. Background Images Limitations 28:11 Migration Strategy & Custom Coding Gaps 28:47 Editor UI Feedback & Navigation (Columns Placement) 29:52 

 You should already know a non-default domainLevel (for example, an .io or .ai domain) requires customizing the Munchkin embed code. Easy on a 3rd-party site, where you already control the embed code; on a Marketo LP, you must disable Munchkin at the template level (Template Actions » Disable Munchkin Tracking) and substitute your custom version.[1] Another case for disabling auto-Munchkin and injecting it yourself is managing cookie consent.[2] And today’s case: if you’re using (as everyone should) a Redirector LP for email links to downloads, where the next-hop URL is passed via the URL hash, you must use custom Munchkin to see the logs you expect. Why use the hash, though?First of all, using the hash, like https://pages.example.com/download#https://assets.example.com/my.pdfoffers better caching than using a query param. The hash is never sent outside the browser, so a cached version of https://pages.example.com/download can be used.[3] But more important, Marketo defines the “web pa

We’re excited to celebrate Sanford Whiteman ( ​@SanfordWhiteman ), who has been named the 2025 Community Member of the Year for the Adobe Marketo Engage community!   Sanford continues to be an invaluable presence in the Marketo community, consistently showing up to help answer questions, share practical tips and tricks, and keep conversations moving in a positive, productive direction. His reliability and deep knowledge make him a trusted resource for members at every level. What truly sets Sanford apart is his generosity and integrity. He offers thoughtful support purely to help others succeed—never to promote himself—and takes an active role in caring for the health of the community by flagging issues and ensuring solutions are clearly marked. His loyalty to the Marketo Engage community, combined with his enthusiasm and merit, has earned the respect of fellow members, advocates, and Adobe employees alike. Sanford has become a true community legend, making this recognition well deserv

Smart Lists offer a dizzying array of filters (In Past, In Past Before, In Date Range, that stuff) for Date and DateTime fields. Yet you can’t natively check if the current system time — that is, the time a campaign is triggered — is within a certain time range on a certain day. Even if you save {{system.DateTime}} to a field, native filters lack hour-of-day and day-of-week awareness. Obviously, you need both to determine if a form came in during business hours and should be promptly Alert-ed to sales vs. Wait-ed until next business day.[1] Luckily, there’s a workaround for Fills Out Form triggers via a little JS. Create a helper fieldFirst, create a new String (not Date or DateTime) field Filterable Form Timestamp. Add the JSThen add this code to pages with time-sensitive forms:MktoForms2.whenReady(function(readyForm){ const minIncrement = 30; // easier filtering than every minute const ianaTimeZone = "America/New_York"; // working hours in this timezone readyForm.onSubmit(funct

If we have duplicate email address but the title is different in the Marketo while the name is same and email address too is same so does this having any affect in Marketo or we can use. Please suggest.

If you feel comfortable navigating Marketo Measure basics, this next set of resources is for you!  Assuming you understand core concepts like touchpoints, attribution models, and standard reporting, it’s time to go deeper — refining your data, strengthening reporting accuracy, and expanding how the platform supports your business decisions. At this stage, success is less about learning what Marketo Measure is and more about optimizing how it works for you. That means understanding the difference between Buyer Touchpoints and Buyer Attribution Touchpoints, implementing thoughtful suppression rules, validating channel mappings in Salesforce, ensuring revenue and spend data are configured correctly, and leveling up your reporting across both Discover and Salesforce. You’ll also explore advanced topics like custom attribution models, sales activities attribution, dynamic field behavior, ABM capabilities, and strategic use of key fields for more sophisticated analysis. These resources are d

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?