Adobe Journey Optimizer

Hi All, Anyone implemented an Add to Calendar CTA in AJO email template ? Thankyou in advance!

Hi everyone,I'm investigating a behavior with Read Audience activities in Adobe Journey Optimizer and would like to know if anyone has experienced something similar.Scenario A profile meets the audience qualification conditions. The profile qualifies for the audience (confirmed in both Monitoring and Profile Snapshot Export). Batch audience evaluation runs daily at 18:00 UTC. The journey is configured with: Read Audience as the entry activity. Scheduled daily. Trigger after batch audience evaluation. 5-hour time window. Issue #1Journey A is scheduled to start at 21:00 UTC.Although the audience contains qualified profiles after the batch evaluation, no profiles enter the journey.Issue #2Journey B is scheduled to start at 21:30 UTC.A specific profile did not enter the journey on the day it qualified for the audience.Instead, it entered the journey 24 hours later, during the next scheduled execution.The strange part is that, at the time the profile entered the jou

Could somebody tell me what is wrong with this syntax? This is decisioning in code base channel. I did what is said in the documentation and it did not work. I asked support and they are working on this for two weeks and this still does not work 😍😍When I render this on the webpage there is fatal errorAny ideas??  [ {{#each decisionPolicy.7bd5011b-b607-4ce2-9d49-234e6a0c1c16.items as |item|}} {"offerDescription": "{{{item._orlen.Vitay.OpisOferty}}}"}{{#unless @last}},{{/unless}} {{else}} {"offerDescription":null}{{/each}} ]

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.We'll use a loyalty-tiered cart-abandonment journey as our example — one that has an event-triggered entry, a conditi

Is it? Its not explained in the documentation

What is the sample use case for that feature?I choose the audience -  people from US. Then I choose “inner audience” for the point 1  people from Texas  people from Miami  I understood correctly? 

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 Problem: Simulation still runs on hand-crafted data Simulation Mode solved where y

In order to request code base campaign for example in Kiosks I need to use Edge Network?

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

Hi there, i have a few URLs that contains semicolon “:” - example below, and upon clicking on the test proofs i received, the semicolon turns into %3A. Is this normal and any documentation i can show to support?https://www.test/?test=te:st:TeST:edm::test&utm_source=&utm_medium=edm&utm_campaign=testThanks!

Is it?

I do not see any option to change between HTML & JSONWhen I add image from AEM Assets in HTMLHow to add that html to JSON? 

We observed that after a subscriber clicks the one-click unsubscribe link in an AJO email, and a streaming audience (consent = N) triggers a journey whose Update Profile action sets a custom attribute (optin = false), the consents.marketing.email.val field reverts from N back to Y simultaneously with the Update Profile action's execution — even though the action is configured to update only the custom optin field and never references the consents field at allaccording to this post: https://experienceleague.adobe.com/en/docs/experience-cloud-kcs/kbarticles/ka-26352“Specific field values do not seem to update properly after running through an Update Profile node in a journey.” -- this is not the case for us, as the optin field gets updated with update action, however the consent field got reverted back to origin state although we haven’t had interacted or manually changed it from somewhere else. 

Lets assume that I createglobal ruleset: max 3 email per week sales xyz rulest: 2 emails per week Customer already got 3 emails per week but these campaigns were not assegned “sales xyz rulest”. If I create new campaign with “sales xyz rulest” and then global ruleset automatically excludes that customer from the sendout? How global and custom rulesets coexists? 

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?