Adobe Journey Optimizer

Hi Team,We have a client who has an AJO license, but currently all their customer journeys, campaigns, data, and related assets are built and managed in SFMC . The client is interested in migrating everything from SFMC to AJO and wants to explore whether AI Agents can be leveraged to accelerate or automate this migration. As a services organization, we would like to understand the feasibility and approach.Could you please help us understand the following:How can AI Agents help in this migration scenario? What capabilities can AI Agents provide during the migration process? Which activities can be handled by AI Agents, and which will still require human intervention? Please outline the responsibilities of AI-driven automation versus manual effort. What are the key considerations before committing to the client that this migration is achievable? Are there any technical limitations, dependencies, risks, or prerequisites that should be evaluated upfront? What are the recommended steps f

Does it work for outbound channles in journeys?

Hello ALL,I have a question regarding the new Dataset Lookup node in Adobe Journey Optimizer (AJO).ScenarioI have configured a Dataset Lookup using the following lookup key:Lookup Key: 123Sample dataset:Column1 (Lookup Key) Column2 Timestamp 123 Yes 6/26 123 No 6/26 123 Yes 6/25 QuestionHow does the Dataset Lookup node behave when there are multiple records matching the same lookup key?Specifically:Does AJO return the first matching record, last matching record, most recent record based on timestamp, or is the behavior non-deterministic? Is there any documented logic or prioritization used when duplicate lookup key values exist in the dataset? Are duplicate lookup keys supported, or is the lookup key expected to be unique within the dataset?ObservationIn my test, when the lookup key 123 matches multiple records, the journey consistently evaluates to the "Others" condition rather than the expected paths.I would like to understand:Whether this is the expected behavior

When I try and add an asset to a content template in AJO I get this red warning symbol. When browsing for the images we can see them but as soon as you choose it, it then fails. This is a new AJO instance and we cannot get it to work with any AEM Cloud assets. We also have Assets Essentials which works but don’t want to use that as all of our assets are in AEM.  Steps to replicateAdd image block Browse asset Browse through AEM DAM (can see assets) Add asset Error I assume this is a permission issue somewhere but cannot find the root cause.

SetupAJO B2C Landing Page with a native Form (appType=AJO_B2C). The form's target dataset uses an XDM ExperienceEvent‑class schema (capturing email opt‑in / consent). The streaming inlet behind the form is XDM pass‑through (no Data Prep mapping stage).GoalCapture each form submission as an ExperienceEvent. Since ExperienceEvent requires _id and timestamp, I've added both as hidden fields on the form.ProblemThe hidden _id / timestamp fields still require a value, but the form designer only lets me set a static "Default value" (optionally sourced from URL parameter / cookie / referrer). There's no native generator, so I'm stuck between two bad states:No default → the form doesn't render/submit correctly. Static default → every submission carries the same _id (events overwrite each other in the dataset/Profile) and the same timestamp (frozen, doesn't reflect the real submission time).I also confirmed that a timestamp default in MM/DD/YYYY format fails form validation — it must be ISO‑8601

Lets assume I have labeled data with labels: X , Z , K , A , DUser has only assigned labels: X , ZDoes this this mean that user only sees X , Z attributes in personalization window?

Hello AJO Community,According to https://experienceleague.adobe.com/en/docs/journey-optimizer/using/orchestrate-journeys/about-journey-building/audience-qualification-events , there is a potential lag of 30min for Streaming Audiences to enter journeys with the Audience Qualification node and if you need real-time entry, a unitary event should be used. But what about Edge Audiences with the Audience Qualification node? Does that not allow for real-time journey entry or is there a similar lag there as well?

I created such an decision policy: The error is like this:  Similar example is show here in the documentation: https://experienceleague.adobe.com/en/docs/journey-optimizer/using/decisioning/experience-decisioning/decision-policies/use-decision-policy

A clean and welcoming reception area can set the tone for visitors and clients when they walk into your business in Tega Cay. It’s the first place people see, and it’s crucial for creating a positive experience. A tidy and organized space reflects professionalism and attention to detail, which can leave a lasting impression.Effective maintenance of this area doesn’t just impact how visitors see your business; it also contributes to an inviting atmosphere that can increase the comfort of guests and motivate your team. Prioritizing cleanliness shows clients and employees alike that you value their presence and wellbeing. for More Info: https://qualitycareuae.ae/ 

Documentation is totally terribly explained.  Could somebody explain what is this location in the web channel configuration?Web channel configuration. Does it map to Decision Scopes in Web SDK? If yes then why Adobe could not name it Decision Scopes??? 

Just saw this tab on a tutorial here: https://experienceleague.adobe.com/en/docs/journey-optimizer/using/decisioning/experience-decisioning/decision-policies/create-decision I have AJO Ultimate. What am not seeing this?

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

Question 1: Seed list can be added on a channel configuration or in the specific journey / campaign? Question 2: When test profile is added to the seed list then the content of the specific email is based on that test profile details? 

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

Hi all, I have a bit of an urgent ask. We’re trying to track email opens and if a user does not open an email we want to add them to a suppression audience. When looking into this, it seems like the interaction type = open event gets triggered automatically even if an email is not opened. We’ve tested this with 5 different profiles and noticed the same behavior.  Has anyone encountered this issue and what could be a potential way to resolve this. Thanks

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

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