Product Communities

 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

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 d

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. 

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 📣

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. 

Hello awesome community guys, I found one missing tool in AEM MCP arsenal. Ended writing a custom mcp server that runs on AIO AppBuilder as runtime action.Explained here https://medium.com/@bsaravanaprakash/one-missing-tool-in-aem-mcp-registry-and-how-to-build-it-on-aio-902cc13b1afaWith this learnt experience, I quickly identified couple more tools usecases on my custom mcp server.Optimized product image search - tool will first hit PIM to resolve to more accurate tags and then hits DAM querying customized tags. Returns accurate product images Taxonomy Resolver - our DAM is massive (3.4M) and taxonomy follows rules. freetext image search mostly timesout due to volume. So custom tool, that runs taxonomy rules, narrows dam folder path and then run Adobe MCP asset search using querybuilder.  Is there any more usecases you are able to find? Tool example, that is difficult with Adobe MCP registry, and qualifies for its own custom server?  Please do share, ready to flex my muscles.

Exited to host this even with Adobe AEP Product Manager.Join us for this virtual session where Adobe Product Manager will showcase the latest upgrades, features, and best practices for B2B use cases in Adobe Experience Platform and connect directly with Adobe experts and network with fellow professionals.Event is scheduled on June 24, 2026 at 3 PM CST.Register here: https://bit.ly/4g5Sp0r

As we know the External Lookup field fetches data using REST API and has been part of Workfront for some time. Although it can be game changer, the desired features are still not integrated.Authentication API Secrets manager Auto trigger the API.This post is to highlight one feature which would be great to have: auto triggering the API and showing the result. Why is this feature important to you?Many a times there are clients who ask for fields that are auto-populated based on other field selections. Other platforms offer this feature with their product but workfront is still tralling behind. With auto triggering enabled for External Lookup, it opens the door wide open for so many possibilities.  How would you like the feature to work?In the custom form editor add a checkbox to say - Auto trigger A new field should show to select the desired output of this trigger. Since data can be an array, we would select first object (example) On a Workfront object, this would translate to auto pop

Problem statement:Customers encountering blocking and duplicate-key failures during concurrent Update Data or registration-style operations currently have no Adobe-supported product feature to smooth write contention. Public guidance focuses on maintenance and scheduling, and product guidance does not recommend enabling SQL Server RCSI. ACC should provide native controls and diagnostics to reduce lock contention without requiring unsupported database isolation changes.Request:Provide native concurrency controls for ACC write-heavy operations on SQL Server so customers can reduce blocking and duplicate-key failures without changing unsupported database isolation settings.Possible sub-features:Queue/throttle mode configurable queuing/throttling for high-concurrency write paths, including registration or subscription-style calls Conflict-aware workflow scheduling/locking hints for Update Data activities targeting the same dataset; lock-aware diagnostics and admin visibility Application me

Hello everyone,I wanted to get your feedback and suggestions on steps to follow while starting on implementing analytics for AEM Adaptive forms in a headless setup.Since a JSON flows back from AEM, should AEM responsibilities just be restricted to maintaining standard field definitions and the rest of the tagging happens on the front end renderer (React) ?Any pointers would be greatly appreciated.

Personalization often starts with a simple customer moment, but turning that idea into working template logic can take time. You may need the right field path, helper, condition, date format, and fallback behavior.AI Assistant for Personalization Expressions helps reduce that friction by turning plain-language intent into AJO personalization template logic you can review, preview, and apply.Instead of starting with syntax, you can start with the outcome you want for the customer:Use the customer's renewal date, add one year, and format it as MM/dd/yy. If the renewal date is missing, do not show the date.It helps translate that request into template logic you can review, validate, and use in AJO. What AI Assistant for Personalization Expressions Helps WithIt is available from the AJO personalization editor through AI Assistant. It helps when you know the customer experience you want, but need help writing, understanding, or fixing the template logic.Generate new personalization expressi

In the first part of this series, we explored the essentials of Adobe Journey Optimizer (AJO) error codes—why they matter, how to approach them, and how quickly understanding these signals can transform your troubleshooting experience.In this second installment, we go a step further and include more frequently encountered error codes. We’re presenting a curated, in-depth table of even more AJO error codes you’re likely to encounter as you build, test, and launch omnichannel campaigns. Think of this guide as your “cheat sheet” for campaign health: If the mysterious codes below pop up in logs or UI banners, you’ll know exactly where to look, what likely caused it, and how to get unstuck fast.Whether you’re facing backend 500 errors, validation problems, or puzzling runtime glitches, this list breaks down each code’s context, root cause, and practical steps to resolve or avoid it. Keep this resource handy—it’s designed to help your ops, technical teams, and marketers spend less time stari

I was recently setting up a webinar campaign in Marketo and noticed registration numbers looked a little higher than expected. (In an ideal scenario, I should be happy about it, but contrary to it, I was skeptical!) When I dug into the records, I found that some attendees already existed in the database. Instead of updating those records, a few were being created as new leads because the data from the webinar platform didn't consistently match.What surprised me was how normal the situation was. Nothing was broken. The integration was working. The records just looked different enough to be treated as new people.It reminded me that duplicate leads often come from everyday marketing activities rather than major system issues.Lately, I've been thinking more about preventing duplicates before they enter Marketo instead of cleaning them up later.Some teams handle this with validation rules, while others use Marketo deduplication tools to help standardize and match records earlier in the proc

Adobe Experience Platform provides the foundational capabilities for collecting, unifying, activating, and analyzing customer experience data. But practitioners involved in implementation, production support, QA, migrations, and ongoing enhancements often need to move quickly between Query Service, dataset previews, Real-Time Customer Profile lookup, audience validation, and ingestion workflows.That day-to-day investigation can become difficult when business stakeholder question that requires more than a sample preview or a high-level UI view. Often, it is required to inspect a specific profile with hundreds of its attributes and events, extract and deep dive into a specific dataset, not just a preview and investigate all the profiles included in an audience, a capability not available in current AEP UI. In many cases, the question is not simply whether data exists, but whether the right data exists in the right place and can be validated efficiently.I faced these same challenges while