Adobe Journey Optimizer

 Issue SummaryWe are using a common footer fragment across multiple email templates. The footer receives a variable (welcomeText) from the email template and renders it using triple braces ({{{welcomeText}}}).When the welcomeText variable contains HTML tags such as <br>, <sup>, <b>, or <p>, the email validates successfully.However, when the variable contains an HTML anchor tag (<a href="...">...</a>), the email validation fails with the following error:welcomeText of email variant is malformedSteps to Reproduce Define a variable in the email template: {% let welcomeText = "<a href='https://google.com'>Google</a>" %} Render the variable in the email template or a content fragment using: {{{welcomeText}}} Save or validate the email. Actual ResultThe email validation fails with the following error:welcomeText of email variant is malformedExpected ResultThe welcomeText variable should accept valid HTML anchor tags in the same way it accepts o

Issue SummaryWe are using a common footer fragment across multiple email templates. The footer receives a variable (welcomeText) from the email template and renders it using triple braces ({{{welcomeText}}}).When the welcomeText variable contains HTML tags such as <br>, <sup>, <b>, or <p>, the email validates successfully.However, when the variable contains an HTML anchor tag (<a href="...">...</a>), the email validation fails with the following error:welcomeText of email variant is malformed  Steps to ReproduceDefine a variable in the email template:{% let welcomeText = "<a href='https://google.com'>Google</a>" %}Render the variable in the email template or a content fragment using:{{{welcomeText}}}Save or validate the email.Actual ResultThe email validation fails with the following error:welcomeText of email variant is malformed

We are using a common footer fragment across multiple email templates. The footer receives a variable (welcomeText) from the email template and renders it using triple braces ({{{welcomeText}}}).When the variable contains HTML tags such as <br>, <sup>, <b>, or <p>, the email validates successfully.However, when the variable contains an HTML anchor (<a href="...">...</a>), the email validation fails with the error:welcomeText of email variant is malformed  Steps to ReproduceCreate a variable in an email template: {% let welcomeText = "<a href='https://google.com'>Google</a>" %} Render the variable in the email or fragment: {{{welcomeText}}} Validate or save the email. Actual ResultThe email validation fails with:welcomeText of email variant is malformed Expected ResultThe variable should accept valid HTML anchor tags in the same way it accepts other supported HTML tags such as <br>, <sup>, <b>, and <p>, allowing the

How are organization planning for changes to AJO platform which take you by surprise? Are there any pre-release notes that your Account Manager shares a month before new releases? Or is a there a release plan that you have aligned with your Account Manager so that new releases are first done in DEV environment and then pushed to PROD a week or so later. 

Hi, Trying to setup a Journey for a time sensitive cart abandonment scenario. Created a Streaming based Audience with the following definition, "Include audience who have at least 1 Product List Adds event then after 15 minutes do not have any Purchases event and occurs in last 1 hour(s)" But found that the profile will be qualified with this Audience right after a product is added to the cart without waiting for 15mins. Any advice please? Thanks,John

Introduction Personalized content is one of Journey Optimizer's strengths — but it is also one of the hardest things to test before you publish. A single email can personalize the subject line, branch on loyalty points and marital status in the body, and use fallback copy when attributes are missing — all in the same template. Simulate content variations gave you a dedicated screen to preview multiple variants and send proofs without the Adobe Experience Platform test profile workflow. That was a real step forward. But it still left the hardest part on your plate: figuring out which test variants you need, and building each one by hand. The Content Simulation Skill takes that job off your plate entirely. It reads your content, analyzes every conditional branch and personalization field, works out the minimal set of variants needed to cover each branch at least once, and uses AI to fill in realistic profile, context, and target attribute values that satisfy those branches. You preview t

Are Custom Actions async?

I have a question regarding AJO Forms and Experience Event datasets.When an AJO Form writes data to an XDM Experience Event dataset through a Form Preset, should the platform automatically generate the mandatory root fields _id and timestamp?If yes, is there any specific configuration required to enable this behavior?If not, what is the recommended approach for customers to populate these mandatory XDM fields, considering that the Form Designer does not appear to provide a mechanism to dynamically generate values for _id or timestamp?Currently, data ingestion into my streaming Experience Event dataset is failing with the error:"_id is missing"At the same time, I can see the Adobe OOTB web.formFilledOut event being generated successfully with both _id and timestamp populated.Could you please clarify whether this is expected behavior, a configuration issue, or a known limitation when using AJO Forms with custom Experience Event datasets?

Would you build this event based on ECID identity of Email identity? Execution field is taken from profile attributes and the email attribute might not be present in the event payload ….Any advise??

RequestWe would like the ability to easily add a mailto link within the AJO content editor, avoiding having to form the link structure manually. ReasoningThe users of the content editor are often not technical This is fairly standard functionality for a WYSIWYG editor It is present in your other email products WorkaroundWe know how to create one manually, e.g.mailto:emailme@example.com?subject=I%20would%20like%20more%20information%20on%20your%20product 

Hi Adobe Community,We're currently implementing a preference center/unsubscribe landing page using AJO campaigns with URL parameter encryption enabled via the Key Registry.**Current Setup:**- AJO email campaign uses the encrypt() helper in personalization editor- Email links include encrypted parameters: ?pid=v1.towEToq9cGLgo9x4...- Landing page is built using AJO Forms (not custom HTML)- Form is tied to an AEP profile-enabled dataset for capturing preferences**What We're Trying to Achieve:**When a user clicks the email link and lands on the form page:1. The encrypted pid (profile/identity) should be captured from the URL2. Assigned to a form hidden field automatically3. When the form is submitted, the pid should be mapped to a profile    identity namespace (Email or CRM ID)4. Form submission data should stitch to the existing profile in AEP    for preference updates**Our Questions:**1. **In AJO Forms Designer** - Can we configure a hidden field to    automatically capture and map URL

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. 

Working with AEM Content Fragments in Adobe Journey Optimizer?Then join us for the next Experience League Live on July 16 at 8:30 AM PT as we explore the latest enhancements that make it easier for content authors and journey practitioners to collaborate, manage content at scale, and reduce handoff friction.In this session, we'll cover how to:✅ Fetch Content Fragments from multiple AEM configurations and switch repositories across journeys and campaigns✅ Manage fragment lifecycle from a new dedicated listing page in AJO✅ Keep content fragment context throughout the message for easier content reuse✅ Take advantage of locale and variation support✅ Access AEM Content Fragments directly in AJO with Managed Services. Whether you're an AEM author managing content libraries or an AJO practitioner building personalized customer journeys, you'll leave with practical insights into the newest capabilities and how AEM and AJO work together in a production content workflow.My guests are : ​@tkhwai 

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

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}} ]

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

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

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? No path-tracing, no hand-built profiles, no digging through logs.This post walks through that end-to-end, using an example journey.  The Issue: Hand-Craf

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