Product Communities

AEM Sites is evolving with multiple authoring and delivery approaches. Universal Editor is becoming an important option for new projects, especially those using Edge Delivery Services or headless architectures. At the same time, Page Editor remains supported and continues to be relevant for many existing traditional AEM Sites implementations.However, choosing between Page Editor and Universal Editor is not only an editor decision. It can also affect:Authoring experience Front-end development approach Performance expectations Content governance and workflows Templates, styles and responsive layouts Integrations and custom dialogs Migration and maintenance effortI would like to know the community's practical experience:For a new AEM Sites project, which approach would you choose—Page Editor, Universal Editor, or another authoring model? If you have an existing Page Editor implementation, would you consider moving to Universal Editor? Why or why not? For teams using Universal Editor with

If you have a follow-up question from the Skill Exchange session Reporting Hidden Gems: 10 Tips That Will Save Time and Impress Leadership with Daniel Clarke (@daniel_clarke) from EMMsphere that originally aired on August 5, 2026, you're in the right place! Leave your comment below and our speakers will do their best to reply. And if you see a question below that you know the answer to, don't be shy! We'd love for you to answer from your own experience and perspective. Have questions about another Skill Exchange session? You can see the full list of discussion threads here. On-Demand Viewing - This session is now available on-demand, you can find the recording here. 

If you’re part of our trial & looking for help in the community - you’re in the right place!  Access to the product is here: https://coworker-campaigns.experience.adobe.com/home If you’re on the waitlist and waiting to be approved, leave us a message here.If you’ve received access, and are in the product and actively trying it out - CONGRATS!!  You too, can use this space to ask questions, leave feedback or share excitement with anything you loved or what you’ve worked on - we’re here for all it 📣

Working with Adobe Experience Manager (AEM) queries? Try my new AEM Query Builder Converter to easily convert between SQL2 and Query Builder syntax and Convert SQL2 ↔ Query Builder in seconds. 🔐 Privacy-first by design❌ No AI involved❌ No customer/client data is stored🌐 Everything is processed directly in your browser✅ You can safely paste and work with actual client queries🔄 Convert between SQL2 and Query Builder quickly and easily 👉 Try it here: https://www.aemcq5tutorials.com/tools/aem-query-converter/ The goal was to create a practical tool that AEM developers can use without worrying about exposing sensitive query data. I’d love to hear your feedback! 🙌If you work with AEM Query Builder or JCR-SQL2, give it a try and let me know what you think, what could be improved, or what other features would be useful.Feel free to share it with other AEM developers who might find it useful.  

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:

Hi all,I'm currently having trouble integrating traffic data from Adobe into our marketing platform (Datorama) using the 2.0 API.With the legacy 1.4 API, we were able to apply multiple segments within the Extended Properties section to filter the data. For example, excluding business-related visits, upgrade journeys, and other traffic types. However, in the 2.0 API connector, I appear to be limited to a single segment and cannot add additional segment filters.Can anyone confirm whether this is a restriction of the 2.0 API, or if there is an alternative approach to apply multiple filters/segments within a single stream?Any guidance or workarounds would be greatly appreciated.Thanks,H

I made the following observation:In the Designer (FormDesigner.exe) for interactive forms, the preview window remained blank.Although the AcroRd32.exe process was launched in the background and the temporary PDF was created in %TEMP%, it was not displayed.A quick analysis revealed that the Windows Update KB5121003 had been installed the day before.Once it had been uninstalled, the problem was resolved.Is this behaviour known?

 If you've ever opened your browser's network tab while debugging an AdobeAnalytics implementation, you've seen it: a long, ugly request to somethinglike /b/ss/examplecompanyprod/1/H29-abc123 or /ee/v1/interact, packedwith query params or a JSON body nobody memorizes on purpose. Tools likeOmnibug or Adobe's ownExperience Platform Debugger will decode that for you -- nicely, even --so you can eyeball it and go "yep, that looks right."That's the thing, though: eyeballing it is the whole workflow. There's nostep where a machine checks the hit and fails a build if it's wrong. Youship a change, the tag either still works or it doesn't, and you find outwhen an analyst asks why last week's numbers look weird.This post is about what's actually inside these two hit shapes, and why Iended up writing a parser (and then a few more tools) instead of justliving with the debugger-and-eyeball loop.Two generationsAdobe Analytics tracking comes in two flavors depending on what'simplemented:AppMeasuremen

Adobe's been promoting AEM Sites Optimizer as a GenAI-first layer on top of AEM as a Cloud Service, aimed at closing the gap between "the site is live" and "the site actually performs well." After checking it against Adobe's current docs, here's a practical breakdown of what it does and where teams should apply healthy skepticism.1. It's built around four pillars, not threeSites Optimizer identifies and diagnoses issues across:Technical SEO Core Web Vitals Accessibility Content engagementThat's a broader scope than most teams assume accessibility issues get flagged alongside performance and SEO problems, not treated as a separate audit process.2. It's not just "suggestions" , it follows an Identify → Suggest → Fix workflow, with one-click applyThis is the part that's easy to undersell: Sites Optimizer doesn't just surface a dashboard of recommendations for humans to manually implement later. It continuously collects and analyzes performance data, prioritizes opportunities by projected

Fellow AEM folks, The pressure to go "Headless" or "Hybrid" is real. Every client and every project seems to be asking for it. But is it always the right answer? The Good: For those who have made the leap, what was the biggest actual benefit you achieved? (e.g., developer freedom, faster site speed) The Bad: What was the most unexpected downside or complexity you faced? (e.g., content preview, author experience, cost) The Verdict: Is Headless AEM a must-have for future-proofing, or is it an overkill solution for most common use cases? When should a traditional AEM setup still be the preferred choice? Let's get past the jargon and talk about what really works (and what doesn't).

Per this https://experienceleaguecommunities.adobe.com/t5/workfront-ideas/allow-machine-to-machine-oauth-app-credentials-to-establish/idi-p/773411#M27023  and this https://experienceleaguecommunities.adobe.com/t5/workfront-questions/having-trouble-using-oauth2-configuration-to-establish-fusion/td-p/658811 it does not really seem like this is something we can achieve at the moment. I just wanted to check was anyone able to establish Server to Server auth between Fusion and Workfront? Thank you in advance.

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

When creating a new Team, users are only required to complete a few fields. Once the Team Name and Team Members are entered, the Team can be created.However, when a user subsequently edits the Team for the first time—for example, to add or remove a Team Member—they may receive the error message:“You must select at least one status in each category.”This can be confusing because the Mark as done section, along with the other fields requiring status selections, is not available when initially creating the Team. These fields only appear when editing the Team.The user must then scroll down to the Mark as done section and manually select at least one status under each category before they can save their changes. This can lead users to believe they do not have permission to edit the Team.Suggested Improvement:Instead of requiring users to select statuses the first time they edit a newly created Team, automatically select a default Closed status under each object in the Mark as done section w

Assim como fazemos as artes para publicaçoes das redes sociais, podemos fazer para publicacaoes

🚀 I’m excited to be speaking at the next Adobe Experience League LIVE session: Coworker Unlocked: Transforming CX Workflows with Adobe CX Enterprise Coworker!AI is evolving beyond helping us complete individual tasks. It's becoming a true teammate that can help organizations uncover insights, create audiences, optimize journeys, and automate work across customer experience workflows.Join the Product and Product Marketing team as we pull back the curtain on Adobe CX Enterprise Coworker and share:✅ How Coworker builds on the foundation of AI Assistant to help drive outcomes, not just tasks✅ The capabilities powering Coworker, including skills, plugins, and MCPs✅ Real-world use cases showing how teams can work smarter, move faster, and deliver better customer experiencesWhether you're a marketer, analyst, practitioner, or CX leader, you'll see how agentic AI is transforming the way work gets done!📅 September 24, 2026 | 8:30 - 9:30 AM PT👉🏻 Registration link here: https://engage.adobe.c

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

Hello, Workfronters! On October 29th, we're bringing a day built just for Adobe Marketo Engage and Adobe Workfront users to New York City, and we'd love to see you there. Spend the day with Adobe customers, admins, and practitioners sharing the real-world insights and best practices they've learned firsthand. Think brand and legal approvals, AI-ready governance, reporting with Workfront Fusion, smarter planning, and a bonus peek at the Agentic Marketing Garage. Plus lunch, a networking reception, and plenty of time to connect with people who do what you do. Here's a taste of what's on the agenda:How Qualcomm rebuilt brand & legal approvals in Workfront Getting your Workfront instance AI-ready Turning data into action with Workfront Fusion From PowerPoint calendars to real Workfront Planning Bonus: Agentic Marketing Garage Are you in the New York metro area? Come join us! Not local? Share this with a colleague in the area! Check out the full agenda and register today: https://reg.ad

Video is central to how organisations engage their audiences—personalised, accessible, and consistent across devices, channels, and regions. Adobe Experience Manager gives teams two ways to power those experiences: the proven Dynamic Media (Scene7) platform that thousands of organisations rely on every day, and Dynamic Media with OpenAPI, our API-first architecture for teams who want lightweight integrations and composable, developer-friendly workflows.Both are first-class parts of the Dynamic Media family, and we continue to invest in both. Which one a team chooses should come down to the architecture and integration model that fits them best—not a trade-off in what their content can do.That’s why this milestone matters. Over the past year, we’ve been bringing the rich video capabilities customers trust in Dynamic Media to the OpenAPI architecture. Today, we’re excited to share that core enterprise video capabilities have reached feature parity on Dynamic Media with OpenAPI.Rich Video

📣 Calling all CJA Hiring Managers 📣Are you hiring for Customer Journey Analytics talent? Adobe is hosting a special virtual career fair designed to connect hiring managers with emerging professionals who have already built a solid hands-on foundation of Adobe Customer Journey Analytics and have become AJO certified.Taking place on October 1, this virtual event will feature students from San Jose State University and the University of Virginia who have completed an Adobe CXO Bootcamp focused on CJA. These students have also completed the CJA Professional-level course AND earned their Adobe certification—making this an exclusive opportunity to meet candidates who are already developing job-ready Adobe Experience Cloud skills.If you’re hiring for an entry-level role or internship where CJA knowledge would make an immediate impact, this career fair is a great way to discover motivated, certified talent and support the next generation of Adobe practitioners.Interested in participating or

If you have just gotten access to Adobe CX Enterprise Coworker and want to learn more about analytics use cases, this session is for you. Coworker brings the power of agentic AI to CX Analytics — so your team can investigate business questions in plain language, automate analytical workflows, and uncover deeper insights, all grounded in the data you already trust.Join our product team on Thursday, September 17, 2026 for a live session on Coworker's analytics capabilities. In this session, you’ll: Discover key use cases for Coworker on CX Analytics Learn best practices and tips & tricks to get started See real world examples of Coworker's analytics capabilities being put to use[Webinar] Unlocking Analytics Use Cases in Adobe CX Enterprise CoworkerThursday, September 17, 20268am PTSave your seat here: https://events.teams.microsoft.com/event/58c38075-bcc5-4c31-8b03-d5ab51ff0bec@fa7b1b5a-7b34-4387-94ae-d2c178decee1?source=copyLinkLegacyShareEventDialog

If you have just gotten access to Adobe CX Enterprise Coworker and want to learn more about how Coworker helps put your analytics data to work in new ways, this session is for you. Coworker brings the power of agentic AI to CX Analytics — so your team can investigate business questions in plain language, automate analytical workflows, and uncover deeper insights, all grounded in the data you already trust.Join our product team on Thursday, September 17, 2026 for a live session on Coworker's analytics capabilities. In this session, you’ll: Discover key use cases for Coworker on CX Analytics Learn best practices and tips & tricks to get started See real world examples of Coworker's analytics capabilities being put to use[Webinar] Unlocking Analytics Use Cases in Adobe CX Enterprise CoworkerThursday, September 17, 20268am PTSave your seat here: https://events.teams.microsoft.com/event/58c38075-bcc5-4c31-8b03-d5ab51ff0bec@fa7b1b5a-7b34-4387-94ae-d2c178decee1?source=copyLinkLegacyShareE