Product Communities

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. 

Hi community,I would like to ask for help and advice regarding the following: is it possible to somehow export all Workfront configurations of a client's instance (custom forms, access levels config, projects config, etc.) and import it back to Workfront? In case a client won't use Workfront anymore, but might decides to use it again in the future, to avoid building things from scratch.Would love to hear similar experiences and best practices! Thank you.

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 📣

This feature only works with Campaign Orchestration?Enable change data capture for source connections in the API | Adobe Experience Platform

This is turn on. It collects automatically all clicks in AJO web campaigns in Offer Decisioning campaigns in Web? 

I need to delete two XDM schemas in a development sandbox and I've hit what looks like a closed loop. Hoping someone has been here before.What I'm trying to doSome field paths in our dev sandbox differ from prod by character case only - for example campaignUseCase1 in dev versus CampaignUsecase1 in prod. Since XDM field paths are immutable once created, I understand the fix is to rebuild the field group and schemas correctly rather than edit them in place.Where it breaksI can't create the correctly-cased fields while the incorrect ones exist, because both paths would land in the same Profile union and AEP rejects paths that differ only by case. So the old objects have to go first.But:I can't delete the field group - two schemas compose it. I can't delete those schemas - both are Profile (union) enabled. I can't disable Profile in the UI - the toggle is there but Save stays greyed out. I can't remove the union tag via API. PATCH on the schema with {"op": "remove", "path": "/meta:immutab

We’re always looking for ways to improve your experience in AEM Sites Optimizer and would like to speak with customers who are hands-on in the product. Who we’re looking for✓ Current AEM Sites Optimizer users✓ Users who work with content authoring, code authoring, or both✓ Users who have recently made an optimization using the recommendations provided by AEM Sites Optimizer What we ask of participants45 - 60 minutes of your time to share your process for completing a recent optimization and answer interviewer questionsTimelineSign-up window: Today through September 25 Interviews running this week and nextHow to participateClick here to schedule a session with our research team. Please reach out if you don’t see a time that works for you.Questions?Ask below — the product team will be monitoring this thread throughout the sign-up period.

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:

We noticed our original referrer data starting to get stripped which moved what would have been Natural Search traffic into Direct throughout the summer, but especially in early August. Are there any ideas on if this is related to the Safari 26 browser update tied to an iOS release, and are there any work-arounds to get that traffic back in under Natural Search in Adobe Analytics?

Previous, I had been able to generate an HTML5 output using the default DITA-OT template that Guides comes with. The result had been a folder of HTML, SVG, and PNG files.In the current version of Guides (5.1), the HTML5 output no longer generates anything except the primary index file with links to nothing. I have tried to generate an HTML5 output using both the Map Console and the Map Dashboard and both result in the same thing: two css files and one index.html file with links to nothing.What am I doing wrong? The default DITO-OT file in CRDXE hasn’t been changed, moved, or touched.

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

Hi folks,For some of the pages, I am able to see Visits is greater than pageviews. Ideally this should not be the case, right? as per my understanding. but at overall level pageviews is greater than visitsThis started happening when i changed expiry of evar from visit level to hit(i breakdown page name with day and noticed this)Some of the notes :1. I am visiting website → accepting cookies → pageview fires first → and then engagements as i make so it seems no action is happening before pageview2. I am sending page name and URL with all my engagements (scroll and link clicks) as i want to know what happened on which page. Also can you please let me know if this is correct or do i need to change something in my implementation.

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

Hi,what module do you use in Fusion to get a decision when it’s made on a new Unified Review & Approval document? I cannot find it in a regular Workfront Watch Events module nor in the dedicated Unified Review & Approval module. Thanks!

If scheduled batch data ingestion fails is there a way to schedule an email notification?