Adobe Journey Optimizer

Microsoft joined Gmail and Yahoo in requiring DMARC for large senders (5,000 or more emails per day) in their consumer email services outlook.com, hotmail.com and live.com. Beginning May 5, 2025, Microsoft started rejecting emails that don’t meet the new bulk sender requirements. Why is this happening? Let’s understand In today's digital landscape, email remains a cornerstone of communication and marketing. However, with the rise of phishing attacks and email spoofing, ensuring the authenticity of email communications has become paramount. This is where DMARC (Domain-based Message Authentication, Reporting & Conformance) comes into play.   What is DMARC? DMARC is an email authentication protocol that builds upon two existing mechanisms: SPF (Sender Policy Framework) and DKIM (DomainKeys Identified Mail). It allows domain owners to specify how receiving mail servers should handle emails that fail authentication checks. By doing so, DMARC helps prevent un-authori

As the marketing practitioner for the e-commerce business, I have created a journey to engage with approximately 10 million users during the Diwali sale and offer period. I now need to test the journey before publishing, as even a small issue in your journey can cause major problems, from broken flows to a poor customer experience. In this blog, we’ll walk through the different testing techniques available in Adobe Journey Optimizer(AJO) and how they help you deliver with assurance.Journeys Test ModeAfter creating the journey, we need to see how it interacts with real profiles. That’s where AJO’s Journey Test Mode comes in handy — it lets you test your journey using the test profiles you’ve set up in AEP.Steps to activate a journey in test modeOpen the draft journey that you want to test.Click on the Test mode button from the header menu.While the transition takes place, we will see a status message that says Activating test mode.Once the transition is complete, we will

🚦🚦 Planning customer journeys isn’t just about creating a flow—it’s about seeing the big picture, identifying overlaps, and ensuring your journeys hit the mark. Adobe Journey Optimizer (AJO) empowers marketers, journey planners, and support teams with intuitive views designed to streamline journeys oversight. Let’s walk through how AJO’s Calendar View, Dashboard and Browse List each solve distinct challenges—paired with real-life use cases to inspire you to use them smartly. Calendar View – Plan Strategically with Visual Clarity 📍Use Case: Journey planner aligning journey timelines You’re launching a weeklong journey and want to avoid audience fatigue. Use Calendar View to: 📅See what’s live or scheduled across the current week ⏱️Identify overlaps that may overload specific segments 👁️Click on any journey block to see its audience and scheduling logic 📎Easily distinguish journeys running acro

In our setup we are currently receiving Analytics data through the dataflow. We want to count the product add events for the profile. Also count the product remove events.Both are separate events within the Analytics Data.Take a difference of Adds and Removals counts, to determine if the Cart is not empty.We want to qualify the customer to send out an email post 30 min wait period. Need help to identify such events and keeping a counter.Attaching a screen shot of the data. Please also be mindful that the Cart list activity may not be an activity the customer chooses to perform. Thank you much.

What Are Custom Actions? Custom actions in AJO are user-defined HTTP requests (typically REST APIs) that can be executed within a journey. They allow you to: Call external systems Send data to downstream services Trigger internal workflows Make real-time decisions based on API responses They are configured with authentication, headers, request/response schemas, and can include dynamic personalisation using AJO expressions.   Use Cases for Custom Actions Here are several categories and examples of how custom actions are being used across industries. 1. Integration with External Services Use Case: Triggering a WhatsApp or SMS via Third-Party API Send a message through a messaging service (like Twilio) directly from an AJO journey. POST https://api.twilio.com/... { "to": "{{ profile.phoneNumber }}", "message": "Hi {{ profile.firstName }}, your cart is waiting!" } Use Case: Notifying Logistics Systems Trigger fulfillment or shipping workflows when a user places an orde

Creating truly personalised customer journeys often requires more than simple conditions. You need the power to dynamically evaluate customer data, perform complex calculations, and create sophisticated logic that adapts to real-time customer behavior.   While Journey Optimiser's simple expression mode works well for basic conditions. The Advanced Expression Editor unlocks a world of possibilities for marketers who need to create intelligent, data-driven customer experiences. This guide will show you how to leverage advanced expressions to solve real marketing challenges and create more engaging customer journeys.   The Challenge: When Simple Conditions Aren't Enough Consider these common marketing scenarios: Scenario 1: Abandoned Cart Recovery You want to target customers who added items to their cart but didn't purchase, but only if they're high-value customers and it's been exactly 24 hours since abandonment. Scenario 2: Dynamic Loyalty Offers You need to send differ

Hi,I am trying to add some rule in Adobe Experience Platform that in a Query looks like:SELECT count(*) FROM profile_snapshot_export_xxx where <path>.LastChequeRedeemedDate <= dateadd(day,30, <path>.Most_Recent_Drop_Date_DM) -- 477 I set a rule like this in the audience:However, the Query count and Audience count are completely different (query gives me 477 and audience only 211)How should the rule be set in the audience, so it matches the count from the Query? Thanks. 

As the title says. I took a look at Journey Optimizer documentation (https://developer.adobe.com/journey-optimizer-apis/), looking for an endpoint that retrieves journeys, as well as Retrieve an Audience from Segmentation Service API in Experience Platform (https://developer.adobe.com/experience-platform-apis/references/segmentation/#operation/getAudience) retrieves audiences, but applied to journeys, however I did not find any endpoint that does something like that. Is there an endpoint to get information from journeys in Journey Optimizer?

Recently we have launched our first journey with Email channel in AJO so when I see CTR its not showing proper result. Can you help with the formula which you use to calculate CTR in AJO. Src shot shared for your reference.   

Hi All,We have an existing AJO email journey which runs in real time and send email to the end user/customers.  We have a new requirement to share this same email content to other department within the organization like agent / customer care team for a reference. we need to share each users email content to these teams like how end user seeing their email. Is there any way we can achieve this.?

🔹IntroductionModern marketing demands speed—but not at the cost of accuracy, brand integrity, or compliance. Whether you’re creating journeys, sending policy updates, or launching cross-channel campaigns, every message matters. That’s why having a structured way to review and approve assets before they go live is essential.Adobe Journey Optimizer (AJO) offers a powerful solution through Approval Workflows, ensuring that every customer experience is reviewed, approved, and auditable—not just for marketing, but across all AJO use cases.In this blog, we’ll walk through a real-world enterprise use case, explore how Approval Workflows solve governance challenges, and share practical steps and tips for making the most of this feature.❌The Challenge: Disjointed Reviews, Risk of Error, and Compliance DelaysA global insurance provider faced a recurring bottleneck: every marketing message and policy update had to be reviewed by Legal and Compliance before it could be activated. Th

Hi!  I would like to better understand how to differentiate between "push clicks" and "push opens" in the AJO Push Tracking dataset. I see that the pushTracking.applicationOpened event tracks when a user opens the application from a push notification. However, even when users interact and click within the app, I don't see any other event types captured in the dataset. Could you help clarify this?  Also what's the definition and difference between push open and push clicks? Thanks!

Hello,I’m encountering an issue with push notifications. For Android devices, push notifications are working as expected on the same day the profile is unified with the ECID and push token.However, for iOS devices, even after the profile is updated and unified with both the ECID and push token, the journey is excluding these profiles with the feedback message: pushNoTokenFoundInProfile.Interestingly, after waiting 24 hours and running the journey again for the same iOS profiles, the push notifications worked as expected.Has anyone experienced similar behavior where Android push works immediately after unification, but iOS does not, despite the profile showing the ECID and push token?Are there any iOS-specific considerations, processing delays, or unification timing issues that could explain this?Any tips or insights would be helpful? ThanksAJODev

“Confidence is the foundation of great customer experiences.”  Launching a journey in Adobe Journey Optimizer (AJO) is a critical step for marketers. But what if you could see exactly how profiles flow through your journey before actually going live—without risking real customer contact or profile updates? Enter: Dry Run Mode.  🧩 The Problem: Uncertainty Before Going Live  Crafting the perfect customer journey is both an art and a science. But here’s the challenge: marketers often face major blind spots during the pre-publication phase. These include: - How many profiles will qualify for the journey? - Which paths will they take? - What are the expected delivery counts? While Test Mode offers basic functionality, it doesn’t provide the full confidence needed to predict actual behavior once a journey is live.  🔍Use Case Snapshot  In this complex journey:  - We start with 200,000 profiles. - Several conditions filter p

  The Global Profile Filter is a powerful new feature in Adobe Journey Optimizer designed to provide marketers with greater control and flexibility over live customer journeys.What it is: Simply put, the Global Profile Filter allows you to define specific criteria based on profile attributes when the journey is paused and that will be applied to all profiles when that journey is resumed. This acts as an immediate, universal filter.This feature is particularly beneficial for scenarios where: Dynamic Exclusion is Needed: Your business rules or customer segments change after a journey has gone live, requiring immediate exclusion of certain profiles from an ongoing journey. Preventing Irrelevant Communications: You need to ensure that specific customer groups do not receive messages from a journey that are no longer applicable or could lead to confusion. Operational Agility: It provides a mechanism to quickly adapt live journeys to new policies or customer classifications without re

After the folder structure was introduced for landingpages, out mirror pages of email (read mail in browser) has stopped working, along with the unsubscribe links (that is pointing to a landingpage). We have moved out existing landing pages into new folders, and it seem like this creates some sort of error. Is this a know problem that existing landing pages might not work anymore it they are moved into a folder i the new folder feature. 

  How to Send Emails Only on Weekdays in Adobe Journey Optimizer Sending marketing emails at the right time is crucial for engagement and deliverability. Many organizations want to ensure that emails are sent only on weekdays (Monday to Friday), even if profiles enter a journey on weekends. In this post, we'll show you how to achieve this in Adobe Journey Optimizer (AJO) using Wait activities and custom formulas, based on a community-accepted solution.     The Challenge You want profiles to enter your AJO journey every day, but emails should only be sent Monday through Friday. If a profile enters on Saturday or Sunday, the email should be queued and sent on Monday at a specific time (e.g., 9 AM). The Solution: Using Wait Activities and Custom Formulas The recommended approach is to use a Condition to check the day of the week, and then use Wait activities with a custom formula to delay sending for weekend entries. Step-by-Step Guide Add a Condition ActivityRight after

Hi, we are actually working on the inApp messages for our implementation. We have ECID and an internal id both selected as identities.  The internal id is getting send through an event (into the identity map) and stored in the AEP profile into the identity map too.  The problem is that when we want to create an inApp campaign, using the internal id as identity instead of ECID, my profile gets excluded with an exclusion message based on missing namespace. For sending the internal id we only embed the identity map object into the xdm (it seem to be working as we can see the value getting stord into identityMap.identities.0.internal_id, but I think we should be applying the updateIdentities() API , for having it properly added to the profile as identity, is it correct?

Hi Team,I'm trying to dynamically set the locale in the formatCurrency() function in Adobe Journey Optimizer. Here's a simplified version of what I'm doing:{%= formatCurrency(10000, "en_AU") %}Instead of hardcoding "en_AU", I would like to pass a profile attribute (e.g., {{countryCode}} or profile.countryCode) that represents the locale dynamically.However, when I try to pass an attribute like this:{%= formatCurrency(10000, profile.countryCode) %}I receive an error.Could you please confirm if passing a dynamic attribute for the locale parameter is supported in AJO expressions? If so, what is the correct way to structure this? @satheeskannak @mohan_dugganab @ajodev @davidkangni @anuhya-y 

How you test these ones?

I have a journey created successfully in development environment, have packaged and imported into pre-Prod environment, however whilst Publishing the package, encountered below error. Have anyone experienced similar error? Any help is highly appreciated. 

For recurring journeys, the email delivery is sent to the seed addresses at every journey execution. But in the context of recurring journeys such as Audience Qualification or Unitary Events, how are seed addresses utilized? Specifically, if 1000 users meet the qualification criteria for an Audience Qualification journey on a given day, will the seed addresses receive 1000 emails?

We can see that when we create new Fragments to be used in email they is created in a Draft mode. And when testing the email with Proofing, we cant se any differences it a Fragment is in Draft mode or in Published mode. We are therefor wondering what is the difference. Is the Draft node just used when the Fragment is run through a Journey, and that Draft mode is excluded from rendering when the mail is sent from the Journey? Or is there other things we have missed regarding this topic? 

June '25 release notes Check out what's new and improved in the latest Adobe Journey Optimizer product release update: Release Notes New capabilities RCS Messaging: Rich Communication Services (RCS) messaging is now supported in the Journey Optimizer, enabling the following enhanced messaging capabilities subject to provider and carrier support: Branded and verified sender support: Send messages using verified business profiles with branding elements (logo, sender name, etc.). Message delivery insights: Receive detailed delivery reports including message status updates (e.g., sent, delivered, read). Link tracking: Embed and track URLs within RCS messages for engagement analytics. Fallback to SMS: Automatic fallback to SMS when the profile's device does not support RCS or is temporarily unreachable via RCS. Basic message composition: Send text-based RCS messages with optional media and rich elements, depending on provider support.  Form fields in code-based experience