Adobe Journey Optimizer

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

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

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

 Hi everyone,I'm a CS graduate with no prior experience in Adobe Journey Optimizer or Adobe Experience Platform, but I'm planning to prepare for the AD4-E606 Adobe Journey Optimizer Developer Expert certification.Could anyone recommend a beginner-friendly learning path, study resources, hands-on labs, and exam preparation tips? I'd love to hear how others approached the certification and what topics deserve the most attention.Thank you!

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.AI Assistant for Personalization Expressions helps translate that request into template logic you can review, validate, and use in AJO.What AI Assistant for Personalization Expressions Helps WithAI Assistant for Personalization Expressions is available from the AJO personalization editor through AI Assistant. It helps when you know the customer experience you want, but need help writing

Hi everyone -- my name is Ben Whitlock, Director of Marketing Platform Operations at Fanatics. We’re growing our Platform Development team focusing on AJO and AEP to bring richer, real-time journeys to our customers. I’m based in Jacksonville, FL and we’re looking for someone either based near Jax, or in the San Francisco Bay Area. Here’s a full job description: https://fa-exki-saasfaprod1.fa.ocs.oraclecloud.com/hcmUI/CandidateExperience/en/sites/CX_1/job/27651/Feel free to ask any questions here. If you think you’re a strong candidate, let’s talk!

Live stream show details:In this Experience League Live session, we dive into journey testing and validation tools in Adobe Journey Optimizer, so you can go live with confidence. Whether you're working with event-based or audience-based journeys, AJO gives you multiple ways to validate your logic before your customers ever see a message. We'll walk you through the ideal way to test your journeys before launch and show you how to take it further with the brand-new Journey Simulation.Join us to see how you can:* Choose the right pre-launch testing approach for your journey type, whether you need to trace profiles through branches or validate audience volume and branching logic at production scale, without sending a single message.* Create simulated users on the fly either manually or with agentic support for quick simulation via Journey Agent, automatically covering all paths in one click.You'll have a clearer framework for validating any journey with confidence, and hands-on insight int

I wanted to start a conversation around improving user experience (UX) and search visibility for digital aggregators operating in highly competitive seasonal markets. Specifically, when managing high-traffic regional travel portals, streamlining the booking funnel while maintaining local SEO relevance can be quite a challenge.For instance, looking at digital workflows in travel mobility hubs like Aruba, international travelers expect zero friction from the moment they touch down. By focusing on total pricing transparency, removing hidden fees, and minimizing terminal delays, platforms can dramatically improve conversion rates.A great example of this execution is how localized landing pages target inbound tourists looking for the Best Car Rental Deals at Queen Beatrix Airport (AUA). From an experience management perspective, integrating clear fleet filters, real-time vehicle availability data, and a 100% paperless reservation workflow directly impacts the customer success metrics.I woul

Adobe Experience Manager (AEM) and Adobe Journey Optimizer (AJO) together provide a powerful ecosystem for delivering personalized customer experiences at scale. While AEM manages content and digital assets, AJO orchestrates customer journeys using real-time data from Adobe Experience Platform (AEP)..

Overview:Enhance the navigation experience within the Adobe Journey Optimizer canvas by introducing modern, intuitive controls aligned with industry-standard tools.The current navigation model requires users to independently manage vertical scrolling, horizontal scrolling, and zooming through separate UI controls. This creates friction when working with complex or large-scale journeys.This idea introduces:Omnidirectional canvas movement via middle mouse click + drag Scroll wheel-based zoom functionality A more fluid, continuous navigation experience Current challenge:The existing navigation approach has several usability limitations: Fragmented navigation controls Vertical movement: scroll wheel or scrollbar Horizontal movement: bottom scrollbar drag Zoom: separate UI buttons Linear movement only Users cannot move diagonally across the canvas Requires switching between horizontal and vertical controls High interaction cost Multiple clicks and manual dragging required Navigation

The Adobe Orchestrated Campaign Module (OCM) should allow filter criteria defined during the Build Audience step to be persisted and reused. Why is this feature important to you As an architect designing complex multi-step orchestration workflows, having to rebuild identical filters across different nodes introduces unnecessary friction, increases the time to value, and raises the risk of human error in audience targeting. How would you like the feature to work Once a user creates a filter in the Build Audience step, there should be an option to save or inherit this logic in subsequent Enrichment activities without manual recreation. Current Behaviour Filter criteria defined during the Build Audience step are not persisted or available for reuse in subsequent Enrichment activities  

Hi everyone! I’m Dr. Margareth Legaspi, and I’ve spent over two decades working in education at both the local and state levels. I’m excited to be attending Adobe Summit for the first time and am looking forward to learning more about Adobe’s products and initiatives, especially those impacting the education space.If there are other education leaders attending, I’d love to connect, exchange ideas, and hear about your experiences. Looking forward to a great conference! 

 We’re hosting an Experience League Live session on Wednesday, April 8th at 8:30 AM, focused on:New Use Cases for Customer Engagement: iOS Live Activities, Web Push, and Persistent MessagingAlongside Brent Kostak, Don Huynh, and Robert Calangiu, we’ll explore how you can extend Adobe Journey Optimizer to deliver more real-time, visible, and persistent experiences across new channels.💡 Topics include:• iOS Live Activities• Web Push Notifications• Message InboxIf you’re looking to expand your engagement strategy and get more value out of Journey Optimizer, don’t miss it.🔗 Register here:https://engage.adobe.com/ExpLeagueLive-260408.html?sdid=H822XBWW&mv=socialSee you there! 👏 

Personalization in customer engagement has matured considerably. Brands now segment audiences with precision, tailor content to individual preferences, and orchestrate journeys across channels. Most of that work focuses on what to send and who to send it to. Timing is often treated as an afterthought. That gap shows up quickly in practice. A healthcare provider sends an appointment reminder at 4 AM. An e-commerce platform fires an abandoned cart email at midnight. A bank delivers a credit card offer via SMS at 5:30 AM. Every one of those messages was personalized. The content was relevant. The audience was well targeted. The channel was right. But the delivery time was not personalized — and that single gap undid all the effort that went into everything else. Quiet Hours in Adobe Journey Optimizer addresses this directly. It introduces time-based exclusion rules that prevent messages from being sent during specific periods — across Email, SMS, Push, and WhatsApp channels — without requ

We recently discovered an issue in AJO. Logging details here for the community visibility so others can easily debug such problem Bug Title Sandbox Tooling failure when copying AJO Campaign Orchestration audiences between sandboxes.Product Product: Adobe Journey Optimizer (AJO) Campaign Orchestration Component: Sandbox Tooling. Expected Behavior Sandbox tooling should successfully migrate an audience package from a dev sandbox to a stage environment. If components such as merge policies are already present, the system should gracefully handle the conflict by prompting to overwrite or ignore the component rather than failing the import. Observed Behavior Attempting to import a package containing an AJO Campaign Orchestration audience fails during the upload. The import returns an OBJECT_EXISTS error ("PROFILE_MERGE was not created anew") for merge policies that already exist in the target sandbox. Additionally, it returns a NEBULA-100092-400 error claiming an invalid or missing namespac

I recently discovered an issue in AJO. Logging details here for the community visibility so others can easily debug such problem Bug Title AJO DEV Sandbox Allowed List failing to enforce domain restrictions for API-triggered campaigns. Product Product: Adobe Journey Optimizer (AJO)Component: Sandbox Administration / Email Settings (Allowed List) Expected Behavior When an allowed list is active at the sandbox level, email sending must be strictly restricted to the explicitly configured addresses and domains. If the active list is empty, zero emails should be dispatched from the sandbox. Non-allow-listed addresses must be suppressed natively before the send attempt. Reference: https://experienceleague.adobe.com/en/docs/journey-optimizer/using/configuration/monitor-reputation/allow-list Observed Behavior Despite an active allowed list configured in the DEV sandbox with specific test domains, API‑triggered campaigns are bypassing this restriction and sending emails to unapproved domains (e

Get certified at Summit - we are ready with expanded testing capacity! Full passholders attending Adobe Summit 2026 can get certified for free by passing an on-site certification exam. All exams (except Adobe ColdFusion and Adobe Captivate) will be available. You may take as many different exams as you like, but you may not take the same exam more than once.  Testing hours are April 19-21 @ 9am-5pm PT and April 22 @ 8am-1pm PT. Seating is first-come, first-served. Find us at the Adobe Certification table on the 5th floor of the Venetian.  You must bring your own fully-charged laptop to take advantage of this offer. Free stable and secure Wi-Fi will be provided.  Learn more today! 

Welcome! 👋This Community thread is a space for everyone who watched (or is watching) this Experience League LIVE episode to connect, ask questions, and keep the conversation going. Share your takeaways, dive deeper into topics from the session, and help each other with real‑world tips and use cases. The Adobe team will be keeping an eye on the discussion and jumping in where helpful—so don’t be shy!

We have two custom actions in our journey. Based on these custom actions we personalize content in our channels.Eg:ProductCustomActionv1 and PriceCustomActionv1According to the setup, we first call ProductCustomActionv1 and then use the information in ProductCustomActionv1 to call PriceCustomActionv1 to find out the price and we use the price information in our channel(sms and email).Now if something changes in ProductCustomActionv1 and we created a new version ProductCustomActionv2 now we have to go manually to all steps within our journey to change the custom action reference. Instead if there is a custom action alias reference that is possible to set within the journey custom action configuration. then we don’t have to change anything within our journey.for ex: ProductCustomActionv1 is set with an alias pdtCustomAction, any new custom action I create I will also give the same alias then all the references of the custom action within the journey would automatically resolve. Please re

Hey AJO practitioners, One thing that keeps coming up when I talk to teams across the industry: staying on top of Adobe release notes is genuinely hard. Not because the documentation isn't there - it is - but because carving out time to check it regularly just doesn't happen when day-to-day work takes over. I built DXP Intel to solve exactly that. It monitors release notes across Adobe Experience Cloud solutions weekly, summarises what's new, and surfaces it in one place. You subscribe to the products you care about - Target, AEP, CJA, AJO, whatever's relevant to you - and only get an email when there's actually something new. No noise, no digest of nothing. Check it out → dxpintel.com Happy to hear any feedback - this is early days and I'm actively improving it.

Hi Everyone,I’m looking to connect with professionals who have hands-on experience in Adobe Experience Platform (AEP), Adobe Campaign, or similar marketing automation tools.Would love to understand how you are working on customer journeys, segmentation, and personalization use cases in your projects.Also curious to learn about real-time implementations and best practices followed in AEP/AJO environments.Happy to connect and exchange knowledge!Thanks in advance.

We’re excited to celebrate Satheeskanna Krishnan ( ​@SatheeskannaK ​) , who has been named the 2025 Community Member of the Year for the Adobe Journey Optimizer community!   Over the past year, Satheeskanna has been a steady and trusted presence in the AJO community, consistently demonstrating deep expertise and a commitment to helping members navigate complex challenges with confidence. What sets Satheeskanna apart is the quality and reliability of his contributions. He shares practical guidance generously, helps keep conversations moving, and creates space for others to learn and succeed. His steady presence and genuine desire to support peers have made the AJO community a more welcoming and effective place - an impact that reflects the very best of community leadership and makes this recognition well deserved.The Community Member of the Year recognition celebrates individuals who go above and beyond to support others, and Satheeskanna serves as a great example of these values. Pleas

Excited to co-host with  ​@DavidBarnes11 an open AEP / AJO community discussion on March 24 at 11 AM EST.This will be a fully audience-driven session - the challenges, blockers, and ideas we explore will come directly from the people who show up and share their experiences.If you work with Adobe Experience Platform or Adobe Journey Optimizer, bring your toughest questions:• What’s blocking you?• What limits are you hitting?• What do you wish the platform could do better?The goal is simple: learn from each other and tap into the collective knowledge of the community.🔗 Learn more & RSVP:https://lnkd.in/eYfJ8XWC💬 If you want to influence the discussion, message ​@Asheesh_Pandey or ​@DavidBarnes11 with the AEP / AJO challenge that’s keeping you up at night. ​​​​​@NimashaJain ​@Sukrity_Wadhwa @Stephanie Dam