Adobe Marketo Engage General

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!

Your AI tools just got a direct line to Marketo Engage.The Marketo Engage MCP Server is now Generally Available (GA), connecting your AI tools of choice directly to your Marketo Engage instance. You get access to more than 100 operations across forms, programs, smart campaigns, people and leads, emails, snippets, lists, and folders, all through the tools you already use.Specifically, you'll learn:What the Marketo Engage MCP Server is and how it works. Which operations and workflows it supports today. How early customers are already putting it to work. What it looks like in a live demo, straight from the Adobe product team. On-demand link: https://experienceleague.adobe.com/en/on-demand-events/marketo-mcp-server

In the Notifications UI, you can drill into SFDC and LaunchPoint errors one-by-one:But unfortunately there’s no bulk export, making it harder to track trends & fixes.  Hacker’s delightConveniently, the underlying endpoint /data/inboxRecord/retrieve supports get-everything requests, not just get-summaries and get-single-details. That is, though the UI lists only summaries – you click a summary to load its details – it’s easy to get the whole notifications “inbox” for offline crunching. Just open your browser console, click any notification in the list or the details pane[1], and run this JS:{ const sanitizer = new Sanitizer({ removeElements: ["br"], attributes: ["class","id"], dataAttributes: true }); const currentURL = new URL(document.location.href); const notificationsInboxURL = new URL(currentURL.origin); notificationsInboxURL.pathname = "/data/inboxRecord/retrieve"; const payload = new URLSearchParams([ ["sort", JSON.stringify([{ property: "

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

Browse the full archive of the Coworker for Marketo Engage and MCP Server 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. Sign-up for Coworker for Marketo Engage and MCP Server Officer Hours UI Updates, Starter Prompts, Skills Roadmap, Callable Agents, Marketo Optimizer Positioning, MCP Server Automation, RBAC Controls, Email Creation, Reporting - Coworker for Marketo Engage and MCP Server Office Hours - September 10, 2026 Coworker Rebranding, UI Updates, UX Issues, Program Validation Configuration, CX Coworker Integration, Callable Agents, Analytics Skills, MCP Server Enhancements - Coworker for Marketo Engage and MCP Server Office Hours - September 3, 2026 Roadmap Updates, Callable Agents, Campaign and Program Buildin, Permissions and API Quotas, Reporting Limitations, Data Movement, Connector Expansion - Coworker for M

Summary: The meeting covered the rebranding of Marketo AI to Coworker for Marketo Engage, UI and experience updates, current and upcoming AI skills, and Marketo Engage MCP Server automation enhancements. Key themes included clearer product alignment with Adobe’s CX Coworker strategy, improved workspace navigation, future personalized prompts, expanding campaign and program capabilities, and broader MCP tooling for prompt-based automation.AI-generated topics with timestamps1:41 — Product rebranding and positioning: Marketo AI has been rebranded to Coworker for Marketo Engage to align with Adobe’s broader CX Coworker strategy, while core functionality remains unchanged.2:59 — UI and experience updates: Users now land directly in a workspace/tree view instead of the previous chat-first experience, with asset search in the tree and updated permissions naming.3:50 — Branding and starter prompts: The interface includes updated branding labels and contextual starter prompts intended to suppor

Summary: The meeting covered the rebranding of Marketo AI to Coworker for Marketo Engage, UI updates, current UX issues, configuration options for program validation, future CX Coworker integration, callable agent development, new analytics skills, Marketo Engage MCP Server enhancements, and recording availability.2:35 — Product naming and UI changes: Marketo AI was renamed Coworker for Marketo Engage to align with Adobe CX Coworker branding, while core functionality remains unchanged; the landing page is also being removed so users enter the main home screen directly, with future personalized prompts planned based on user and instance activity.6:48 — UX feedback and issues: A navigation issue with collapsing the chat or skill panel caused confusion and unresponsiveness in some flows, and the team acknowledged it as an issue needing a fix.8:50 — Configuration and validation rules: Validate Programs organizational rules are currently configured through a settings icon using markdown tex

Summary: The office hours covered Marketo AI and Marketo Engage MCP Server updates, customer Q&A, and roadmap direction. Key topics included upcoming UI and roadmap changes, callable agents, campaign and program-building capabilities, differences between Marketo Engage MCP Server and Marketo AI, permissioning and API quota considerations, reporting limitations, data-movement constraints, and future connector expansion.AI generate topics with timestamps4:08 — Roadmap and product updates: John outlined upcoming roadmap visibility, UI changes, and near-term feature development, including callable agents, campaign and program building, and standardized data capabilities expected in the coming months.8:21 — Marketo Engage MCP Server vs. Marketo AI: The team clarified that Marketo Engage MCP Server is an external, prompt-driven interface where an LLM calls Marketo APIs, while Marketo AI operates inside the Marketo UI using built-in agent skills tied to user permissions.15:41 — Permission

Summary: The office hours covered Marketo AI access, governance, and product capabilities alongside the generally available Marketo Engage MCP Server. The discussion included setup requirements, API usage, reporting limitations, list import functionality, program validation, and planned enhancements to improve usability, analytics, and import workflows.AI Generated topics with time stamps3:13 — Office hours overview: The session focused on Marketo AI and the generally available Marketo Engage MCP Server, including Q&A and product walkthroughs.6:43 — Marketo AI access and permissions: Marketo AI is available through the My Marketo interface and is governed by admin permissions, generative AI terms, and existing workspace and asset permission structures.12:25 — Program QA and validation: The team demonstrated program validation using organizational rules and optional test plans for automated QA checks, though the walkthrough was partially limited by environment performance issues.16:

Summary: The meeting provided an overview of Marketo AI availability, access, and released capabilities, while clarifying how Marketo AI compares with MCP-based integrations. The discussion emphasized governance, permission controls, performance expectations, current product scope, integration trade-offs, and future opportunities to expand CRM visibility and cross-system orchestration.2:00 — Introduction and availability: Introduced Marketo AI office hours following GA launch, noting availability for eligible Marketo customers and admins with GenAI terms enabled.3:56 — Access and UI: Marketo AI is available as an admin tile in Marketo, with the beta UI expected to move to general availability soon.5:04 — Core capabilities: Released skills include Investigate Leads, Validate Programs, Import Leads, and Product Knowledge, supporting lead analysis, program validation, data insights, and documentation-based Q&A.8:16 — Safety, governance, and performance: Marketo AI remains permission-g

Make your mark at one of the biggest names in payments. We are looking for a Senior Marketing Operations — Growth & Acquisition is a business-critical role within the Revenue Marketing organization and will have a measurable impact on new customer pipeline and revenue growth. This person will own the end-to-end operational execution of acquisition marketing programs within a complex B2B2x sales model, working cross-functionally with Line of Business (LOB) stakeholders, analytics, creative, and sales teams to plan, deliver, and continuously optimize campaigns through the marketing automation system.This high-impact role requires a detail-oriented, results-driven marketer who thrives at the intersection of strategy and execution. The ideal candidate brings deep experience managing the full campaign lifecycle, from audience building and platform setup through launch, weekly performance optimization, and post-campaign debrief, and is equally comfortable driving day-to-day tactical deci

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!

💡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 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