Product Communities

Did you know there’s a whole playlist of videos to help you get started with CX Enterprise Coworker Chat? Check ‘em out:https://experienceleague.adobe.com/en/playlists/coworker-get-started-with-chat

The future of enterprise work management is evolving and we’re excited to launch a new virtual event series focused on the latest Advanced Enterprise Operations (AEO) capabilities in Adobe Workfront.Throughout 2026, this series will explore upcoming enhancements and powerful new functionality designed to help organizations scale operations, improve governance, streamline planning, and drive greater business value across teams.We’ll use this post as the central hub for:Registration links for upcoming sessions Event recordings and replays Related resources and documentationEach session will feature product experts sharing demonstrations, best practices, use cases, and guidance to help you better understand and prepare for these capabilities. Upcoming sessions and topics include:[On-demand Recording] Driving Value: Introducing Advanced Enterprise Operations Capabilities in Workfront [On-demand Recording] Capture Smarter, Scale Globally: Custom Forms & Localization in Workfront [On-dem

Welcome to the September edition of the Workfront Wire!  This is your monthly roundup built just for Workfront customers. Think of this as your one-stop-shop for the latest news, updates, events, and everything happening across the Workfront world. Each month, we’ll bring you what’s new, what’s next, and what you should know to get the most out of Workfront, without having to dig for it. Let’s get into it, and we’ll see you again In October for the next edition of the Wire.  Workfront Skill Exchange On-Demand  The Workfront Skill Exchange sessions are now available to watch on demand! As you work through the recordings, you may find you have questions for our speakers, and we encourage you to ask them.  Discussion posts have been created on the Experience League Community for each session. Please leave your questions in the appropriate thread to chat with our presenters directly. Don't be shy! These folks have been in your shoes and are here to share their experience, so you don't have

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

Dear AEM Community,Your time is precious, and we understand the importance of efficiency when it comes to troubleshooting issues with AEM.That's why we're excited to again bring you our carefully curated collection of Top KCS (Knowledge-Base) Articles for August 2026, designed to help you resolve common challenges swiftly and effectively.Our Top KCS Articles are your shortcut to:Quickly identifying and resolving recurring issues. Accessing expert insights and best practices for AEM. Streamlining your troubleshooting process for maximum productivity. Empowering yourself with the knowledge to tackle any AEM-related problem head-on.Why spend hours searching for solutions, when our Top KCS Articles have already done the heavy lifting for you?Let us help you save time so you can focus on what truly matters – empowering you to provide a truly personalized experience to your customers with AEM.Start supercharging your problem-solving skills today by exploring our Top KCS Articles!Take a look:

Dear Adobe Campaign Community,Your time is precious, and we understand the importance of efficiency when it comes to troubleshooting issues with Adobe Campaign.That's why we're excited to again bring you our carefully curated collection of Top KCS (Knowledge-Base) Articles for August 2026, designed to help you resolve common challenges swiftly and effectively.Our Top KCS Articles are your shortcut to:Quickly identifying and resolving recurring issues. Accessing expert insights and best practices for Adobe Campaign. Streamlining your troubleshooting process for maximum productivity. Empowering yourself with the knowledge to tackle any campaign-related problem head-on.Why spend hours searching for solutions, when our Top KCS Articles have already done the heavy lifting for you?Let us help you save time so you can focus on what truly matters – creating exceptional campaigns with Adobe Campaign.Start supercharging your problem-solving skills today by exploring our Top KCS Articles! Take a

Canvas Dashboards are more than just another reporting option in Adobe Workfront. They offer a powerful way to visualize, understand, and take action on your work. However, since they function differently from traditional reports, many teams either avoid using them or never fully realize their potential.Watch the on-demand webinar for an interactive, practitioner-focused session featuring Skye Hansen, Lead Functional Architect at Merkle, and Matt Mitchell, Principal Product Manager at Adobe. Discover how to use Canvas Dashboards effectively with clear, practical guidance, without getting bogged down in configuration details.Skye and Matt will explain how Canvas Dashboards fit into the broader Workfront reporting landscape, highlight their advantages over other report types, and show you how to build dashboards that people actually use.Specifically, you’ll learn:How Canvas Dashboards integrate with the Workfront reporting landscape and the unique capabilities they offer beyond standard

Thank you to Karthik Muralidharan, Director, Strategy and Product Marketing, for the insightful presentation and demo on Adobe Brand Visibility! So many exciting things coming to the Generative Engine Optimization space!If you missed out, or want to replay the session, check out the links below:Slides Webinar Recording Check out the product yourself: play.bv.nowFeel free to use this space to keep the conversation going! Add your thoughts, follow-up questions or takeaways here and maybe let us know what feature you’re most excited about.If you missed it, check out the session we did in July with Darrel Smith from WK Kellogg and Emily Kellman-Kessel from Adobe.com. They shared their experiences of marketing in the world of AI. Also, save the date for September 22, for our next AI Search and Discovery Forum session – registration link coming soon!

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

I’ve been having some fun building new data visualizations in Coworker that don’t otherwise exist in CJA. It’s actually really fun, and once I’m successful, I turn the steps into a Skill in Coworker so it’s repeatable with just a prompt. Check it out: I wanted to build a box plot visualization. If you’re not familiar, check it out. In short, it’s a great way to visualization distribution. My goal was to better understand distribution of Product Views across the Products on adobestore.com. I started by asking Coworker if it knew what a box plot viz is (it did) and if it could create the Calculated Metrics needed to create one for Product Views (it could). Coworker then confirmed with me what Dimension to pull them for (we confirmed Product Name) and bada bing bada boom:Box Plot Visualization of adobestore.com’s Product Views across Product Names for August How cool is that?? I told Coworker to make it a Skill, and now I can create these box plots with a single prompt (for example I want

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

Thank you to all who attended our Southern California Chapter Workfront User Group Event today! We loved the participation and there was a lot of interest around this topic. We discussed bringing AI agents into Workfront, walked through a framework for evaluating whether an idea is worth building, choosing the right tool for the job, and honest lessons on what makes agents actually stick.For anyone who missed the event, the recording is linked here:   Also, if you want to keep the conversation going on AI in Workfront whether it be with API, MCP, Collaborators, Fusion, etc., feel free to post in the thread below or on our LinkedIn post recap.Olya and I would love to hold more events on this topic as well so your feedback is always helpful. Thank you,Becky Barus

The recording of today’s Experience League LIVE show is now available on Experience League.https://experienceleague.adobe.com/en/on-demand-events/exl-live-episode-08-26-26 In this Experience League Live session, we introduce Adobe Journey Optimizer Loyalty, a new orchestration layer that sits above your existing loyalty platform to turn static points ledgers into responsive, AI-driven experiences. Whether you're running a mature loyalty program or testing engagement tactics, we show how AJO Loyalty connects loyalty data to the same orchestration engine already powering your broader customer journeys. We walk through how always-on AI surfaces insights and recommends next-best tactics for your marketers, how to build challenges that gamify customer behavior and personalize rewards, and how to orchestrate loyalty messaging alongside the rest of your customer journey, all without replacing the loyalty management platform you already rely on. Join us to see how loyalty can move from a backw

Ever wished you could segment on just the products that matter, without dragging along everything else in the same hit or event?If you’ve ever wanted to segment on just the products that matter—without dragging along everything else in the same hit or event—this session is for you.Join us on Thursday, August 27, 2026, where Adobe Analytics Champions Mandy George, Lead, Digital Analytics Implementation and Reporting at Staples Canada, and Deborah William (Deb), Manager, Digital Analytics and Optimization at Deloitte Technology | Solutions - Brand, will show you how to put these capabilities to work.Together they’ll share:What sub-hit analysis in Adobe Analytics and sub-event analysis in Customer Journey Analytics are, and how they enable more precise product-level analysis Real-world use cases that turn these capabilities into practical reporting tools Best practices and pitfalls to understand before you dive in Whether you build dashboards, create segments, or support reporting for you

Project management in Adobe Workfront is about more than tracking projects, building timelines, and assigning tasks. It is about changing the mindset: Workfront can be a shared communication and reporting tool that helps teams understand what is happening, what needs attention, and why the work matters.Specifically, you’ll learn:How to use Workfront as a communication and reporting system, with project and traffic managers facilitating the flow of information rather than owning every routine task. How to use accurate updates, hours, statuses, templates, dashboards, and reports to communicate details and support better business decisions. How to tailor information to each audience, while managing notifications and cadence to avoid overload. How to keep improving after implementation by reviewing adoption, planned versus actual hours, workflows, and templates. View the on-demand webinar: https://experienceleague.adobe.com/en/on-demand-events/project-management-workfront

Hi all,I have recently gained access to the AJO feature ‘Optimize for AI Inbox’-feature for e-mails, which should make the text version of the e-mail optimized for an ai e-mail inbox, ultimately resulting in higher engagement. I find the feature super easy to use, and I like the use case as a simple step towards making our e-mail deliveries more AI-ready.A feature like this is very easy and interesting to perform a split test on, so I have already setup 2 separate split tests. Test 1: Bulk/One-off 50/50 split with around 50.000 customers in each treatment (Ecom sales e-mail)Result: No significance in either open rate or CTOR. Test 2:Always on survey/customer satisfaction e-mail. 50/50 split.Result: Low volume as of now, so too early to conclude. Disclaimer: I’m situated in Denmark (so are the customers from the test), and I’m aware of differences in european versions of email clients such as Gmail, where we don’t have full roll-out of the AI inbox feature yet. So I’m keen to hear from

Is your loyalty program actually driving growth, or is it just... sitting there? A static points ledger that doesn't talk to the rest of your customer journey? Join our next Adobe Experience League Live session on AI-Powered Loyalty Orchestration with Adobe Journey Optimizer Loyalty, where we're digging into exactly this problem. Here's what my guests Keara Fausett, Daniel Vivas, and Tyler Hoguewill be showing: ✅ How AI can surface insights and recommend next moves for your marketers, automatically ✅ Building challenges that actually gamify customer behavior (and make rewards feel personal) ✅ Weaving loyalty messaging into the rest of your customer journey, instead of running it in a silo ✅ Connecting loyalty data to AJO's orchestration engine — without ripping out what you've already built📅 Wednesday, August 26th 🕑 2 PM PT If you've ever looked at your loyalty program and thought "there has to be a smarter way to do this", this session is for you. Come join us.Register now: https://

If you have just gotten access to Adobe CX Enterprise Coworker, one of the first questions is usually: where do I start? Rather than trying to come up with the perfect prompt, I would spend 15 minutes experimenting with a few different parts of Coworker. The goal isn’t to get something huge done right away. It’s to get a feel for what Coworker knows, how it works, and where it can actually help with the work you do. Here are five things I would try.  1. Ask Coworker what it can do for you Start with: “What can you help me do with the Adobe applications and capabilities available to me?” This is an easy way to get oriented without first having to figure out which product, feature, skill, or prompt you are supposed to use. You’ll get a much better sense of the range of things you can ask Coworker to do.  2. Ask about something you work with Next, pick something from your day-to-day work and ask about it. For example:  “Find the audiences related to [loyalty program] and summarize how the

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

Shoutout to ​@SamTaylor, Principal Product Manager, Workfront Automation & Integration, for leading today’s event and sharing his expertise to highlight some of the latest features in Workfront Fusion! If you weren’t able to attend, a summary, links to the slide deck, recording, and additional resources are listed below.New Features Discussed: API-Based Scenario Promotion: New automated capabilities in Workfront Fusion replace the traditional manual clone-and-remap process, including a look at technical setup requirements, current limitations, and roadmap items. Fusion API Enhancements: Recent and upcoming updates for execution logging, detailed error reporting, and improved monitoring options. Webhook Security: New mTLS and OAuth support for stricter access control, along with a retrigger capability that makes debugging webhook-driven scenarios easier. Scenario Versioning & Restore: New tools for comparing scenario versions and restoring deleted scenarios/connections. Connecto

New to Adobe CX Enterprise Coworker or looking for resources? We will use this post as the community’s starting point and update it as Adobe publishes new resources. Product and community  Adobe CX Enterprise Coworker product page — product overview, modules, and current calls to action  Coworker Chat information and access page — current overview, access guidance, and common questions  Open Coworker Chat — sign in with your Adobe credentials  Experience League documentation  Coworker documentation hub — the official starting point  Create an email campaign — the complete build-and-review walkthrough  Coworker Chat overview — capabilities, building blocks, and the evolution from AI Assistant  Coworker Chat use cases — current prompt patterns for insights, audiences, journeys, and more  Analyze Customer Journey Analytics data with Coworker Chat — quick answers, deep analysis, permissions, and best practices  Coworker Chat UI guide — how to navigate and work in the experience  AI

Hello Community,I am preparing to kick-start my journey as an Adobe Experience Platform Analyst. With an analytical mindset and enterprise IT experience, I am drawn to how AEP solves complex data integration, segmentation, and omnichannel activation at scale.To accelerate my growth, I am looking for ways to gain practical exposure: Mentorship & Guidance: Any advice on the ideal roadmap for Adobe certifications (such as the AEP Qualified/Certified Expert paths). Hands-on Exposure: Open to volunteer work, entry-level internships, or shadowing practitioners on implementation use cases. Key Resources: Recommendations on community repos, labs, or documentation beyond standard Experience League tutorials. If you are open to connecting or have advice on where a newcomer should focus their first 90 days, please feel free to drop a comment or reach out directly. Looking forward to learning from this incredible community!

Most orgs running AEMaaCS at scale eventually split into a Platform team (Cloud Manager, pipelines, environment governance) and one or more Product teams (business logic, content). This split is healthy in principle, but in practice it creates constant friction around anything that touches deployment, migrations, bulk content transforms, scripted rule changes, because ownership of “who ships this” isn’t architecturally defined, so it gets negotiated project-by-project.I want to propose a pattern that’s worked well for us and ask whether others have converged on something similar (or better):The core idea: instead of arguing jurisdiction over a piece of work, split the artifact so each team owns a layer they already have legitimate authority over.Platform team owns the engine, a generic, reusable OSGi service deployed once via the standard Cloud Manager pipeline. It knows how to execute a class of change (e.g. template transformation, bulk property migration) but contains no business-sp

  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