Welcome to the Adobe Marketo Engage Community! Connect with peers to ask questions, share best practices, explore release updates, and contribute ideas that shape the future of Marketo.
Recently active
Opens and clicks have long been considered the gold standard for measuring email performance, thanks to their simplicity and broad accessibility. But in recent years, the gap between these metrics and real human behavior has grown rapidly. Today, relying on basic metrics like opens and clicks can be misleading. Why? Because they track technical signals, not real human behavior. Why Email Metrics Often Don’t Reflect Real Human Behavior Here’s the reality: Opens are recorded when a tracking pixel loads, and clicks register when a link is requested. Neither proves that someone actually read your email, paid attention, or intended to engage. Factor in modern email bots, security scanners, and privacy tools, and what looks like an “engaged” audience can be a mix of real humans and automated systems. As marketers, it’s crucial to grasp not just how this skews standard email engagement metrics, but also the ripple effects it can have on revenue and the sales funnel: Compromised A/B Test Resu
Hi Marketo Community!I was a speaker at the Skill Exchange sharing about how you can prepare your Marketo Engage for AI (and how you can use AI to help you in this work). The link is here, but I’m also curious to learn how the community is using the new AI features and what you have implemented so far!
I would like to provide feedback regarding the new Marketo UI experience. The Classic UI offered a highly intuitive and user-friendly design, particularly through the use of distinct colors and visual indicators for different actions and functionalities. These visual cues significantly improved usability and helped users perform tasks such as QA, campaign management, and navigation more efficiently.In the new UI, many of these distinguishing visual elements appear to be reduced or absent. As a result, the interface feels more uniform, which can make it more difficult for users to quickly identify actions, workflows, or important sections during day-to-day operations.I would encourage Adobe to consider preserving or reintroducing some of the key usability features from the Classic UI, especially the color differentiation and visual clarity that many users relied upon. For a large number of existing users, the Classic UI remains more intuitive, efficient, and user-friendly than the curre
💡This solution uses the same tech as toggling images in Email Editor. I’ll omit some details you can read about over there. You might be surprised that WebFonts (via CSS @font-face) are supported in Apple Mail for desktop and mobile. Those apps comprise at least 20% of email opens; using some methodologies, as much as 60%. Even the low end, IMO, doesn’t match the common take that “few” end users will see your fancy fonts! Yes, you must fallback forcefully for Outlook. But it’s totally doable: this month (August 2026) I’ve seen WebFont-enabled emails from CDW, Dolby, London Review of Books, Malwarebytes, Mural, Salesforce, Verizon, and Zapier. As with toggling images, you can easily add a WebFonts toggle to Email Editor 2.0:A little Email 2.0 template code high up in <head>:<meta class="mktoBoolean" id="enableImages" mktoname="Enable WebFonts" true_value="http:" false_value="'none'" default="true" /> <meta http-equiv="Content-Security-Policy" content="font-src ${enabl
We all know Outlook blocks images by default, yet there’s no native way to preview without images in the Marketo UI. Turns out it’s super-easy to add a toggle to Email Editor 2.0:Only takes a little Email 2.0 template code high up in <head>:<meta class="mktoBoolean" id="enableImages" mktoname="Enable Images" true_value="http:" false_value="'none'" default="true" /> <meta http-equiv="Content-Security-Policy" content="img-src ${enableImages}"> And this <style> right after:<style>:root:has(meta[http-equiv="Content-Security-Policy"][content="img-src 'none'"]) { --images-disabled: "images";}:root:has(meta[http-equiv="Content-Security-Policy"][content="font-src 'none'"]) { --webfonts-disabled: "webfonts";}:root:has(meta[http-equiv="Content-Security-Policy"][content="img-src 'none'"]),:root:has(meta[http-equiv="Content-Security-Policy"][content="font-src 'none'"]) { body:before { font: small-caption; display: inline-block; padding: 6px; content:
Managing and retiring segmentations in Marketo can be an unnecessarily time-consuming process.Today, when a segmentation needs to be unapproved, archived, or deleted, administrators must manually remove every dependency listed in the Used By section. This often requires opening each individual asset and disconnecting the segmentation one at a time.For email assets, the process can be even more complex. Administrators may need to remove dynamic content, create drafts, reapprove assets, and perform additional cleanup before the segmentation can be detached. In larger instances with many programs and emails, this can become a significant administrative burden.My suggestion is to enhance the existing Used By functionality. Since Marketo can already identify every asset that references a segmentation, administrators should be able to select some or all dependencies and authorize Marketo to remove those references automatically.A potential solution would allow administrators to:View all segm
Happy to see the flow details of a smart campaign is now available in REST API. Much appreciated for considering our enhancement request and implementing it. Thank you very much on behalf of our company Ingram Micro. Few things to enhance it further. The Wait step details are too lengthy and it’s “bit tricky” to identify which option is the configured one through API. The “value” key can be considered for the identification, however it would have been great if there is any specific key that explicitly denotes which option is configured like “configured: true”, since instead looping through each “value” key, developers can depend on that explicit key. Sample Response for reference:{ "success": true, "errors": [], "requestId": "1234", "warnings": [], "result": [ { "id": 1234, "name": "Testing", "description": "", "flowId": 1234, "flow": { "steps": [ { "id
Hi Team,We have a custom object related to closed leads that we use for a nurturing campaign. Currently: The custom object is linked at the Account level. As a result, all contacts associated with the account receives the email. Our goal is to have only the specific contact associated with the closed lead receive the email. We plan to eventually update the custom object relationship to the Contact level. Interim solution:Since the custom object already contains a Contact ID, is there a way to: Match/filter the Custom Object Contact ID against the Marketo Lead/Contact ID, or Use another Smart List-only workaround to exclude contacts who are not associated with that specific closed lead ? Any guidance on an interim solution would be greatly appreciated.Regards,Akshat
Only so many “banes of your existence” before the term is meaningless. But form-level Custom CSS (Form Settings » Form Theme » ⚙) makes the cut for me. That Custom CSS box enables multiple bugs:Styles meant for all forms are isolated within the form. They persist if cloned, but are lost when someone starts a form from scratch (and they will!). Styles meant for one or a subset of forms[1] are erroneously cloned to other forms, where they have to be overridden by sloppy !important rules. Style changes aren’t propagated, by definition. It’s impossible to know whether a form uses the latest CSS.In my scarily long experience, it’s impossible to coordinate Custom CSS with page-level and site-level <style>s and <link>s. The correct place for form styles is an external .css stylesheet. Conventional approach: Custom CSS is empty, <link> loads external stylesYou can simply <link> external styles before calling loadForm():<link rel="stylesheet" href="https://pages.exam
Browse the full archive of the Marketo Engage New Email Designer Customer Office Hours. These recurring office hours sessions feature Adobe experts from the Marketo Engage product organization walking through new features, answering live customer questions, and sharing best practices. Register for future New Email Designer Customer Office Hours Brand Themes Setup, Variants & Theme Application, Tracking, Permissions, Dark Mode, Custom CSS, Fragments & Mobile Rendering – 7/15/26 Auto-Save, Test Profiles, Dark Mode, Fragments, AI Images & Outlook/Gmail Rendering Fixes - 6/17/26 AI Assistant Brand Kit — Setup, Content Generation, Brand Alignment Scoring, Image Generation & URL-Based Email Creation - 3/29/26 Expert Code Editor for Outlook Fixes, Brand Themes Bugs, Fragment Propagation, API Docs & Preview/Simulate Content - 3/25/26 Brand Themes Sharing, Fragment Padding Bugs, Outlook Background Images, Dark Mode & Old Editor Sunset Timeline – 3/11/26 Te
First things first, what is an API? API stands for Application Programming Interface, which is a set of definitions for building and integrating applications. API uses the standardized method of transferring data that lets you connect and facilitate data transfers between two platforms even though they are built on completely different platforms / tech-stack / architecture. APIs essentially serve as a layer of abstraction for the programmatic access of the data present on the back-end. Marketo APIs Marketo exposes its REST (Representational State Transfer), SOAP (Simple Object Access Protocol) APIs (Application Programming Interfaces) to allow the remote execution of many of its capabilities. Marketo also has a rich library of JavaScript APIs to perform actions / get data on the client side (more about Marketo's client side JavaScript APIs in another blog, we'll focus on REST/SOAP APIs in this one). Apart from being able to help integrate third party systems wi
We're starting a Marketo implementation where Salesforce integration won't be ready 6-12 months (internal dependencies, not our choice). Rather than wait, we're exploring and planning to:Launch Marketo standalone (scoring, nurture, events, preference center) Design everything CRM-ready (fields, lifecycle, program statuses, naming) Validate scoring before routing leads to sales Connect SFDC later as a "Phase 2 switch-on"For those who've done this:What did you build BEFORE CRM that you were glad you did? What caused rework when you eventually connected? Any "I wish I'd known this earlier" advice? How long standalone was enough to validate your scoring model?Context: Large global B2B firm, but focus is for regional firm.
Hello! I am working on a new Marketo instance and creating our folder tree per Adobe’s recommendations.The issue I am running into is that our instance is split into partitions based off of the business area; as such, I’d like the same proposed folder example in each partition, but Marketo does not allow the same folder names. The only resolution I have currently is putting something like:A - Active Marketing Programs [for the first instance]and continuing with a letter in front like that for all folders. Wondering if anyone else has encountered this issue and what they did to make names unique. TYIA!
Hi everyone,I’m facing an issue with Adobe GenStudio and would appreciate some guidance.I have Admin access, and we have completed the setup steps mentioned in Adobe’s documentation.However, when I go to the Brands section, I’m unable to click the Create Brand button. Instead, I see the following message:“No brands to use — yet. An administrator is currently completing setup. Brands will appear here when available.”I have already checked the available settings and permissions, but the Create Brand option is still not enabled.Could anyone please confirm:Is there any additional setup required before creating a Brand? Does the user need a specific role or permission apart from Admin access? Is any backend provisioning required from Adobe?Any help or suggestions would be appreciated.Thanks!
Hi there!I’m looking for a hands-on Senior Marketing Automation Specialist to own the day-to-day operations of our Marketo Engage instance, supporting two of The Freeman Company’s brands.This role will be the execution engine behind our owned-channel campaign activity, partnering closely with campaign marketing teams to build, launch, and report on Marketo programs across email, digital, and events.The position is eligible for a hybrid schedule, generally requiring work in-office and/or on-site at events 2–3 days per week. The ideal candidate will be located in Philadelphia, PA or Dallas, TX.If you’re interested, or know someone who may be a great fit, please feel free to reach out or applyhere.
They’ll tell you it can’t be done. But they didn’t count on the power of having no social life.[1] Marketo’s Dynamic Chat is an able alternative to third-party apps (indeed, it’s technically a separate app that syncs bidirectionally with Marketo Engage). But one thing it lacks is hidden field support which is so key for attribution. Many of our clients don’t notice this gap because they use API-based reporting to see chats in the context of full journeys.[2] But for those without such a solution, the fact you can’t even pop the current page’s UTM params (let alone data in cookies/local storage) into fields is frustrating. Quick look before I slam the hoodEach Dynamic Chat dialogue is a sequence of mini HTML <form> elements whose data is routed over a persistent websocket, rather than a traditional HTTP POST. I really like this implementation because it keeps HTML semantics — you can see the <form>, <input>, and <button> — but gives way better performance than if
Issue Description:While testing the Marketo UI Beta, I noticed an inconsistency between different rich text editing experiences. When creating a new Snippet, the editor continues to display the legacy Rich Text Editor toolbar and icons. However, Rich Text Tokens are using the updated Rich Text Editor experience with the new toolbar design and iconography.Current Behavior:Snippet editor continues to use the legacy Rich Text Editor UI. Rich Text Tokens use the updated Rich Text Editor experience.Expected Behavior:The Snippet editor should use the updated Rich Text Editor experience, consistent with other rich text editing areas such as Rich Text Tokens.Question:Is this expected behavior because Snippets are not yet included in the Rich Text Editor migration, or should this be tracked as a UI Beta issue? Impact:Creates an inconsistent editing experience across Marketo UI Beta components.
Velocity’s quirky treatment of null could drive a mortal mad. As a language aimed at web developers rather than “real” developers, VTL attempts to smooth over Java’s strict typing: it allows comparison across types[1] and blends false and null into a form of falsiness. We can work with or around those features. But it gets weirder: in versions including Marketo’s install[2], Velocity also prohibits creating new null references at runtime. There’s no real workaround for this one; ironically, to avoid related bugs, you must follow poor programming practices! Take a person with a single Opportunity:Field Datatype Value LodgingType String "commercial hotel" Host String " Zaan Hotel " PointsProgram String null City String " Amsterdam " Meals Boolean false (Whitespace around the LodgingType and City is deliberate. And null is really null, not an empty string.) Here’s the raw output of ${OpportunityList}:{LodgingType=commercial hotel, Host= Zaan Hotel , Poin
Hey Community! 👋If you’ve been looking for a dedicated tool like add_smart_list_rule_constraint in the Marketo MCP server to update the existing or a new smart list by applying the “Add Constraints” you won't find it listed in tool searches in the Marketo Engage MCP operations list.However, the capability is fully functional and easy to use it’s just absorbed into update_smart_list_rule. 🔍 How It Works Behind the Scenes There is no separate callable tool for constraints. add_smart_list_rule - Creates the rule shell. update_smart_list_rule - Handles the constraint via its constraints array parameter. 📌 Important Note: While the Marketo UI allows empty constraint values, the Marketo API requires at least one value when saving. Passing a default value (like 'Web service API') satisfies the API requirement and can easily be updated later!Has anyone else been experimenting with the Marketo MCP server? Let me know in the comments! 👇Take a look on the discussion I had with the Claude
Under the Hood: Comparing the Official MCP Toolset to the REST APII’ve lived and breathed the Marketo REST API for years. In fact, I was so deep in the weeds that I actually built my own custom Marketo MCP before the official one existed. Back then, I was limited strictly to standard REST endpoints, since that was the only systematic way to work within in Marketo. So, when I finally got my hands on the official beta, I was dying to know: how does this new AI toolset actually stack up against the "old reliable" REST API?Whether you’re looking to supercharge an AI assistant for your team or just trying to figure out which integration path won’t break your workflow, understanding these gaps is huge. Let's dive into where they overlap, where the REST API still reigns supreme, and those cool spots where the MCP pulls off tricks the REST API can’t do at all.Just a heads-up: all of this is "as of now." Since the MCP is currently in beta, things can, and most likely will, change. Knowing the a
With the announcement of the beta program to leverage an MCP server to your preferred AI tools, I was curious if any users have started to leverage this for their organizations yet? I am looking forward to trying the beta but need to receive signoff from our internal teams before we get the greenlight.
In your experience, what are the main reasons a Marketo lead scoring model fails to deliver expected results?
We sometimes see people trim()-ing Strings in Velocity before comparing them, like:#if( $lead.Region.trim().equals("Northeast") ) Without evidence that leads or apps have added extra whitespace around values, worrying about trim() here is likely overkill. If data is validated via picklists or reliable apps (e.g. you can easily trim Marketo form fields before submission[1]) you’re just forcing Velocity/Java to allocate memory for new Strings. Some people trim() before isEmpty(), in case a value consists of only spaces:#if( $lead.LastName.trim().isEmpty() ) The real flaw in both cases isn’t the concept of trimming, it’s that the types of whitespace trimmed by trim() are very limited and don’t represent the real-world whitespace that janks up databases. For example, U+00A0 NBSP isn’t covered by trim() since it only removes ASCII whitespace! In my experience, NBSP is a bigger wtf-how-did-that-get-in-there offender[2] than basic spacebar, so you want to catch it. So rather than trim(), use
The meeting provided a detailed walkthrough of Marketo Engage’s brand themes feature within the e-mail designer, with Deepthi demonstrating how to create, configure, and apply themes across templates and e-mails. The session covered theme setup, color palettes and variants, typography, spacing, buttons, dividers, grid settings, and structure-level theme application, while also highlighting the flexibility to unlock component styles when customization is needed. Participants asked questions about permissions, rendering, custom fonts, mobile behavior, tracking, CSS, image issues, and training needs, with Joe capturing follow-up items to support broader adoption and troubleshooting.08:51 – Fragment and conditional content limitations: Questions covered template-level conditional content, fragment preview behavior, saving fragments from templates, and propagation of fragment updates. 08:51 – Theme styling and rendering issues: The group discussed theme background image limitations, MSO scr
This Email Designer Customer Office Hours session focused on recent Marketo Engage Email Designer updates, including auto-save, reusable test profiles, send proof workflows, fragment creation, workspace sharing, Velocity scripting support, and dark mode customization. Deepthi and Joe also addressed customer questions and troubleshooting needs around fragment bugs, conditional content, rendering issues across Outlook and Gmail, AI image generation, and mobile stacking flexibility. Key follow-ups included continued testing and fixes for fragment-related issues, clearer documentation for rendering and dark mode limitations, and customer-provided screenshots or HTML examples to support troubleshooting ahead of the next office hours session.AI-Generated Timestamps0:08 – Session overview: Joe and Deepthi introduced the Email Designer office hours session, covering content preview, test email workflows, dark mode features, and customer Q&A. 2:40 – Auto-save and test profiles: Deepthi revi
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
