Product Communities

How Adobe Dynamic Media Templates close the gap — delivering personalized content at scale from a single URL. For the designers, marketers, and developers who have to make personalization actually happen. The personalization imperative Personalization isn't a nice-to-have anymore - it's the default customers expect. As per this McKinsey study, 71% of consumers expect companies to deliver personalized interactions, and 76% get frustrated when this doesn't happen. And it pays: companies that grow faster drive 40% more of their revenue from personalization than their slower-growing peers.So the mandate is clear. The problem is delivering on it. The content scale crisis Personalized marketing demands creative at a scale no design team can hand-produce. Every product needs creative for every channel, in every language, for every audience, refreshed every campaign - and those factors don't add up, they multiply. Run the numbers for a single year: 8 products × 15 channels × 35 languages × 10

A lot came out last week. Here's a quick breakdown for anyone who hasn't dug into the release notes yet.Unified Review and Approvals connector This is the headline. A native connector for Workfront's approval workflow, create and update approval stages, add participants, send reminders, make decisions, retrieve approval status, and even get suggested approvers. Previously you'd need custom API calls to automate any of this. Now it's native modules, which means cleaner scenarios and easier maintenance.I'm planning to use this as part of a content supply chain automation :- Fusion watches for an approval decision in Workfront, then automatically triggers the downstream action in AEM without anyone manually checking the outcome. Will share more once it's built.New Fusion API endpoints Fusion now has a significantly expanded API for managing Fusion itself. You can programmatically list, clone, and export scenarios, pull execution history, manage connections, data stores, folders, and webho

We're launching the Adobe Workfront User Group – Seattle chapter, and we want you in from the start.Grab your coffee and join your Chapter Leaders, Chris Lew and Thomas Scott Adams, virtually on July 21 at 9amPT for the first gathering of Workfront users across the Pacific Northwest. Whether you're an admin, project manager, or just getting started with Workfront — this is your community.We'll make introductions, share the chapter's vision, and hear directly from you about what you want to see next. Come ready to connect with peers who get it.RSVP today! https://workfront-augs.adobe.com/events/details/adobe-workfront-wug-seattle-presents-wug-seattle-kickoff-meeting/

Dear AEP Community,Your time is precious, and we understand the importance of efficiency when it comes to troubleshooting issues with Adobe Experience Platform.That's why we're excited to again bring you our carefully curated collection of Top KCS (Knowledge-Base) Articles for June 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 AEP. Streamlining your troubleshooting process for maximum productivity. Empowering yourself with the knowledge to tackle any AEP-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 highly personalized digital experiences with AEP.Start supercharging your problem-solving skills today by exploring our Top KCS Articles! Take a look:Custom

Thanks to everyone who joined today’s workshop on Mastering Business Rules and Validation Logic in Adobe Workfront! The session was led by Adobe Workfront’s Tina Craig, Principal Business Consultant, Content Supply Chain, who shared several examples and best practices for using these new features to help with governance (and reduce the redundant reminders from admins)! Workshop Summary:Validation logic prevents form submission when criteria are met; business rules prevent object creation, deletion, and editing across system. Validation logic uses if-then statements on custom form fields; business rules are configured in the Setup area with broader scope (only available to customers on the Workflow Ultimate package). Practical examples like special character restrictions, character limits, date constraints, SLA enforcement, and multi-option selections were demo’ed.  Remember! Always test in Sandbox before production deployment to prevent workflow disruption. If you weren’t able to join

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 June 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:De

When using the Week view layout in a Calendar report it has an hour-by-hour grid for each day of the week. When objects without a time don’t fall into these hour slots the hour-by-hour grid shows blank, taking up a lot of empty space on the page. I would like the ability to hide, collapse or turn off the hour-by-hour grid when viewing a Calendar report when the hourly grid is empty or unused. 

Currently, the description field is not included in the summary panel of the Unassigned Work portion of the Workload Balancer.  It is visible in the “Assigned Work” section, however.  There is currently no way to configure the component that governs this specific display (per Adobe).  Requesting that the task description be added to the Unassigned Work summary, as resource managers often need to refer to context within that description to make their assignment decisions. Currently the only way for them to do that is to click through to the task details, navigating them away from the WL Balancer in order to gain the necessary context.

Choosing the wrong authoring model can impact content velocity, governance, and scalability. Here's a practical comparison to help AEM teams make the right decision.This guide breaks down the key differences in authoring experience, content governance, flexibility, scalability, and implementation considerations to help teams choose the right approach for their AEM EDS projects.Whether you're building marketing sites, enterprise platforms, or content-heavy experiences, understanding when to use each model can save significant time and effort. Read More:- https://www.aemcq5tutorials.com/tutorials/document-based-authoring-vs-universal-editor-in-aem-eds/ 

 The Problem StatementHow do we connect RT-CDP audience segments with CJA event data to analyze customer journeys, despite differences in identity stitching models and delayed audience data availability? Answer-If you are setting up Adobe Customer Journey Analytics (CJA) along with Real-Time CDP (RT-CDP), you might notice an interesting challenge.Both platforms handle identity stitching in very different ways:RT-CDP builds a real-time Identity Graph to link users across systems. CJA works on fast, query-based analysis using flattened event data (like web/mobile logs).So the key question is:How do these two systems connect?How does an audience created in RT-CDP match perfectly with web or mobile events in CJA?Let’s break it down step by step.Core Concept: Persistent ID vs Person IDWhen you configure a dataset (WebSDK or Mobile) in CJA, you define two important fields:Persistent ID → Identity Graph → Person ID(Raw Input) (Linking) (Final Output) Persistent ID (Input):

 Hey all,Most AEM teams trust the Dispatcher's deny-all approach, but are your allow rules as restrictive as you think?In this article, I explore how broad extension-based allow rules can expose internal endpoints in AEMaaCS and share practical hardening recommendations for a stronger security posture.🔗 Hardening AEMaaCS— Part 3: Why Default Dispatcher Rules May Expose Internal EndpointsCurious to see any similar experiences anyone had!

In enterprise-level system architecture, just as we prioritize seamless data integration and scalability, the physical real estate sector is moving toward high-performance structural frameworks that prioritize long-term asset stability.Effective asset management, whether in digital ecosystems or urban development—relies on precise compliance, secure infrastructure, and optimized environmental layouts. As we analyze market trends for high-utility residential projects, it becomes clear that modern vertical developments are increasingly integrating smart infrastructure to meet the demands of global professionals.For those tracking regional market expansions and physical asset deployment, evaluating Apartments for Sale in Lahore offers an insightful look into how LDA-approved vertical housing projects are utilizing modern engineering to provide sustainable, secure living environments.Integrating such physical assets into a diversified portfolio requires the same level of analytical rigor w

Most marketers initially think of Quiet Hours as a simple Do Not Disturb feature, a single switch that silences or pauses all outgoing messages during a set period. Turn it on for a journey, define the time window, and you're done.That mental model is close, but the real strength of Quiet Hours lies in how it handles messages, not just when they're queued or discarded, but what happens to them during and after the quiet period.Quiet Hours in AJO is configured at the action level, this means a single journey can contain multiple messages, each with its own Quiet Hours behavior: one message might be discarded, another queued for later delivery, and a third allowed to send immediately. All of these can coexist within the same journey, with each action behaving according to its specific purpose.Because the messages in a journey aren't all created equal. Some are time-sensitive, others can wait, and some may no longer be relevant after a delay. That's why a one-size-fits-all Quiet Hours pol

If your team has been building emails in Marketo for any length of time, you've probably felt the tension between scalability and speed. The classic Email Editor 2.0 gave developers tremendous control i.e. full HTML/CSS access, custom scripting, pixel-perfect layouts but it placed a heavy burden on technical resources and slowed down campaign cycles. The new Drag-and-Drop (DnD) Email Designer changes that equation significantly. Here's everything we learned from building a full modular email template system on top of it.Why the move to the new DnD Editor?Our team's primary drivers were reducing developer dependency and improving template consistency across global campaigns. The new DnD Designer shifts email creation into a visual, marketer-friendly paradigm one where non-technical users can confidently build and iterate on campaigns without breaking layouts or brand standards. Template architectureThe template is built using a section-based layout within the DnD Container system. Think

Watch the show recording: How to efficiently test, simulate and validate journeys before going liveLearn how to go live with confidence by validating journeys before activation. We'll cover the best testing approaches for both event-based and audience-based journeys, plus a first look at the new Journey Simulation capabilities.You'll see how to:• Choose the right pre-launch testing method for your journey type• Validate branching logic and audience volumes without sending messages• Create simulated users manually or with Journey Agent support• Automatically test all journey paths in a single clickPerfect for AJO practitioners who build, publish, and maintain journeys and want faster, more reliable validation workflows.Register now: https://engage.adobe.com/ExpLeagueLive-260617.html

Modern customer journeys rarely stay inside one system. They depend on loyalty platforms, billing engines, CRM tools, fulfilment services, and partner APIs. When one of those integrations fails, the reason behind the failure matters just as much as the failure itself.A temporary outage may need a retry. A duplicate request may need no action at all. A suspended account may require customer service intervention. But until now, custom actions in Adobe Journey Optimizer could detect that a call failed without giving journeys access to the structured error details many APIs already returned. What's New: Error Response Payload Support Custom actions have long supported success response mapping. When an API call succeeds, you can define the response structure, parse the body, and use those fields later in the journey.Previously, error handling worked differently. If a custom action returned a 4xx or 5xx response, AJO recorded the failure status, but it did not surface the response body even

Modern customer journeys rarely stay inside one system. They depend on loyalty platforms, billing engines, CRM tools, fulfilment services, and partner APIs. When one of those integrations fails, the reason behind the failure matters just as much as the failure itself.A temporary outage may need a retry. A duplicate request may need no action at all. A suspended account may require customer service intervention. But until now, custom actions in Adobe Journey Optimizer could detect that a call failed without giving journeys access to the structured error details many APIs already returned.AJO 26.1 changes that with Error Response Payload Support for custom actions. What's New: Error Response Payload Support Custom actions have long supported success response mapping. When an API call succeeds, you can define the response structure, parse the body, and use those fields later in the journey.Previously, error handling worked differently. If a custom action returned a 4xx or 5xx response, AJ

This is a request to have the Emergency pipeline execution mode, currently available for AEM on-pem (Code Deployment | Adobe Experience Manager), added to AEM as a Cloud Service. 

Team,I have Group Admin access in Workfront and have gone through the reporting documentation. However, I haven't been able to create reports on my own and need guidance. If anyone could spare 30–60 minutes to help me create a few basic reports, I would really appreciate it.Additionally, we are currently using Workfront custom forms for request intake, which requires requestors to have at least Contributor access. My management has asked me to explore using a Microsoft Form integrated with Workfront as an request intake solution.If anyone has experience with this setup or can help with the integration, I'd greatly appreciate your support.Thank you!

Building customer journeys often starts with a simple idea."Send an offer only to Gold members.""Wait until 9:00 AM in the customer's local time zone.""Exclude customers who received the same campaign in the last 14 days."The business logic is usually straightforward. Translating that logic into a valid journey expression is where the work begins.Journey builders need to locate the right attributes, navigate complex schemas, understand expression syntax, identify the correct functions and operators, and validate the final result before it can be used in a journey.For experienced users, this can take time. For new users, it can become a significant learning curve. Focus on Customer Experiences, Not Expression Syntax Journey builders should focus on creating customer experiences—not memorizing syntax, searching through schemas, or troubleshooting validation errors.Journey Expressions Agent helps bridge the gap between business intent and technical implementation by combining attribute di

You open your journey inventory and see six, twelve, maybe hundreds of journeys sitting in one flat list — no grouping, no hierarchy, just an ever-growing scroll. Finding the right journey means scanning by name and hoping you remembered what you called it six months ago.That is the problem Journey Folders solves.  What Are Journey Folders?Journey Folders is a native organisational layer built directly into Adobe Journey Optimizer. It lets you create named folders, move existing journeys into them, and nest folders up to four levels deep — giving teams a scalable hierarchy that maps to how they actually think about their programmes: by region, business unit, campaign type, or lifecycle stage.Unlike tags or filters, folders are structural. A journey lives in exactly one folder. The folder appears in the breadcrumb, in the sidebar tree, and in every "move to" dialog — so the location is always unambiguous.  Step 1: Create Your First FolderIn the Journeys inventory, click the Create folde

Adobe Target Webinar | From Practice Field to Game Day: How the Packers Built a Winning Optimization Program Date: Friday, June 26, 2026Time: 10:00am - 11:00am PT Join us for this thought leadership collaboration between Adobe and the Green Bay Packers to learn how one of the NFL’s most iconic franchises built a disciplined, scalable optimization program using Adobe Target. In this session, you’ll learn:How the Packers moved beyond one-off tests to a program focused on insights, confidence, and long-term momentum. Real-world use cases from Packers.com and the Pro Shop, including hypothesis, test design, and results. Best practices for governance, prioritization, and measurement in a highly seasonal environment. How to prepare your organization for more advanced personalization capabilities​​​​​​​​. Seats are limited. Register today to be a part of this memorable experience. 

I like the Question asked by @Viktor Lazar  here The 2026 question is "what is the content supply chain that produces the experiences, and where does the component library fit inside it?" If New Age AI Architecture looks like this (taken reference from https://www.trainyfi.ai/post/aem-is-no-longer-the-brain-ai-is) AI Agent Layer   ↓Calls into:- AEM (content)- AEP (data)- Target/Journeys (activation)   ↓Continuous optimization loopI have a few key questions from an AEM developer’s perspective:How should AEM components be designed within this new AI-driven ecosystem? What should AEM developers specifically focus on when building solutions in this model? Where is the “working model” in practice, given that it no longer resides solely within AEM? How will this shift toward AI-driven orchestration shape the future role of AEM and its component architecture?Given that the “working model” is now distributed across AI agents, AEP, AEM, and activation layers, how do we practically design and al

Join us for the next session in our Adobe Analytics Certification Masterclass series focused exclusively on the Adobe Analytics Business Practitioner Expert (AD0-E208) certification.This hands-on workshop, guided by seasoned Adobe Analytics Champions, offers you the chance to get insider insights on the latest exam structure, key topic areas, real-world use cases, and expert tips to help you prepare efficiently and effectively for certification.Whether you’re just beginning your certification journey or looking to renew your credentials, this masterclass will equip you with the knowledge and confidence you need to succeed. Don't miss this opportunity to enhance your skills and connect with fellow professionals.💡 Bonus: We’re giving away Five FREE Adobe Certification Vouchers to lucky participants!💡💡Double Bonus: All active participants receive exclusive 33% discount on their next certification.📅 Date & Time:Thursday 18 June, 2026 11:00 AM GMT/3:30PM IST🏢 Key Takeaways: Underst

Please ping me at John@syncpointdigital.com if you are interested in learning more.