Adobe Journey Optimizer

As the travel tech industry grows, providing a seamless digital booking experience has become crucial for ground mobility platforms. Travelers landing at major international hubs expect a hassle-free transition from the terminal to their vehicles without dealing with hidden fees or legacy booking systems.In Pakistan, the digital shift is rapidly happening. For instance, when travelers are looking for a reliable islamabad airport rent a car service, their primary digital touchpoints are price transparency, instant confirmation, and localized digital payment options.From a digital experience perspective, optimizing this specific customer journey requires: Real-time Fleet Tracking: Keeping users updated on vehicle availability instantly. Simplified UI/UX: Reducing booking steps for overseas travelers who just landed after long flights. Data-Driven Personalization: Tailoring vehicle recommendations based on travel history and group size. What are your thoughts on integrating automated

Introduction In our previous post, Journey Simulation Agent — Cover Your Whole Journey in a Few Clicks with AI-Built Test Users, No Hand-Crafted Data, we showed how the Journey Simulation Agent generates a minimal, AI-built set of test users to exercise every branch of your journey — no manual profile construction needed. That post kept things simple: a journey with no event nodes.But most real journeys don't stay simple. They wait on events — a cart addition, a purchase, an app open, a custom behavioral signal. And those event-driven journeys have a few extra moving parts.This post covers those extra moving parts: how the Journey Simulation Agent automatically generates the test events your journey needs, matches them to the right test users, and triggers them in the right order — so you can go from draft to publish-ready without touching a single event payload by hand. The Problem: You Need Test Events for Test Users Here's where most practitioners hit a wall.The Journey Simulation A

Introduction A little while ago we introduced Simulation Mode — a way to test run a draft journey with lightweight, AJO-native Simulated Users before you ever publish. It was a big step: instead of pulling in AEP test profiles to try out a journey, you could spin up purpose-built test profiles right inside AJO.But Simulation Mode still left one job on your plate: you had to figure out which test users the journey needed, and you had to build each one by hand.The Journey Simulation Agent takes that job off your plate. It reads your journey, works out the minimal set of paths needed to exercise every branch, and uses AI to generate a realistic test user for each one, complete with the profile attribute values that path needs. Then it triggers them into the journey and hands you a single verdict: is this journey ready to publish, or not?This post walks through that end-to-end, using an example journey.  The Issue: Hand-Crafted Test Data Picture a welcome journey you've built for new membe

AJO is the channel marketers already trust to get every communication right — email, push, and SMS, orchestrated from one place. Adobe Target, meanwhile, has been the brain behind your best on-site moments — the right offer, the right visitor, the right second. That intelligence used to stop the instant someone left your site. Not anymore: AJO can now reach out mid-send, pull that same targeting logic straight from Target's Delivery API, and carry it into an email, a push notification, or an SMS — so the trust you've built on-site travels with every message AJO sends. Most teams have solved this the hard way before: rebuilding the recommendation logic inside the messaging tool, keeping two systems in sync by hand, and hoping the "top pick" in tonight's email actually matches what's live on the homepage. AJO closes that gap with Integrations — connect the Target Delivery API once, and any message template can call it at send time. The smartwatch a shopper almost bought yesterday shows u

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

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

 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

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

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

Adobe Journey Optimizer Business Practitioner Professional free online training with exam preparation. Have a question about the AJO Foundations course, AJO Business Practitioner Professional course, or the Certified Professional exam prep guide listed on the certification information page? Reply to this thread and a learning support specialist will respond to you.  We follow the Adobe Experience League Community Forum Guidelines in this discussion thread. If the response resolves your question, consider giving a Like to the learning specialist who replied. We appreciate the kudos! Questions outside the scope of the online courses and exam preparation guide will be directed to the main community forum page. 

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