Welcome to the Adobe Journey Optimizer Community! Connect with peers to ask questions, share best practices, explore release updates, and contribute ideas that shape the future of Adobe Journey Optimizer.
Récent
In Adobe Orchestrated Campaign (OCM) Enrichment nodes should be able to pull fields directly from the core XDM profile, not just from linked relational entities. Why is this feature important to you The Real-Time Customer Profile is the heart of the Adobe Experience Platform. If orchestration cannot easily leverage native XDM profile attributes during the enrichment phase, it severely limits personalization capabilities and forces redundant data mapping into relational stores. How would you like the feature to work Within an Enrichment activity, users should have full access to select and pull attributes natively from the unified XDM profile alongside relational entity data. Current Behaviour Enrichment is anchored to the targeting dimension but can pull fields from any properly linked relational entity and NOT from XDM profile
Enhance the reliability and error messaging of the preview functionality between orchestration nodes. Why is this feature important to you Data validation during the build phase is essential for trusting the orchestration engine. Vague errors prevent practitioners from effectively debugging schema or data flow issues, forcing reliance on trial-and-error testing. How would you like the feature to work The node preview should reliably render data samples. If an error occurs, the UI should provide specific, actionable diagnostic messages (e.g., highlighting exactly which schema field or table mapping failed) rather than generic fallbacks. Current Behaviour The preview functionality between nodes frequently fails with non-descriptive “something went wrong” or “table has changed” errors, hindering data validation
Provide the ability to edit or delete Profile Target Dimensions within the Adobe Orchestrated Campaign Module (OCM) UI after their initial configuration. Why is this feature important to you Business requirements and data models evolve over time. When Target Dimensions are locked, architects are forced into rigid technical debt, requiring cumbersome workarounds if the underlying identity schema or targeting strategy changes. How would you like the feature to work Administrators should have the ability to safely modify or deprecate existing Profile Target Dimensions within the UI, provided they are not actively running in live campaigns. Current Behaviour Profile Target Dimensions are foundational, immutable objects; once configured, they cannot be edited or deleted within the UI
There is a need for a centralized repository or UI view within Orchestrated Campaigns to easily inspect existing filter definitions. Why is this feature important to you Governance and validation are critical for enterprise deployments. Without a way to preview filter logic safely, practitioners risk accidentally altering campaign audiences during routine audits or troubleshooting. How would you like the feature to work Introduce a read-only "View Filters" modal or a dedicated tab in the OCM UI that allows users to inspect the detailed logic of an existing filter without having to enter an edit mode that risks overwriting it. Current Behaviour There is no centralized repository or UI view to inspect existing filter definitions without initiating an “overwrite filters” action within the Build Audience node
If you have ever pasted a carefully crafted date-time expression into a Journey wait node and been greeted by a vague parser error about the plus sign, you are not alone. Journey Optimizer’s expression language is strict about how arithmetic is written, and one missing pair of parentheses is enough to block your journey.In this short guide, we walk through a real pattern: computing a wait-until time from profile data and “days from today,” then show why the expression fails and the minimal syntactic change that makes it valid. What you are trying to doA common pattern is to combine currentTimeInMillis() with a millisecond offset derived from a profile reminder date, today’s date at midnight, and a fixed offset (for example, fourteen days in milliseconds). Conceptually that is straightforward arithmetic inside toDateTime / toDateTimeOnly. The expression that triggers the errorBelow is an example of the kind of nested expression teams often build for wait logic. It is semantically reason
Hi, I want to join delivery and tracking logs for push. For email I know we can use “messageProfileId” but I can’t see that column in Push tracking logs. Do you know if there’s an specific column (or maybe a concatenation of ids) to join both Delivery and Tracking for push? My goal is to see the opens or clicks for a profile who received the push. Thanks.
Does these also works for event journeys?
I can find these from APIs may be, but I dont see any dataset which has this information.
Hi Adobe Community, Greetings! For AJO use case where streaming segment is one of the core dependencies, I wanted to check if we can potentially configure a trigger event journey that does not depend on streaming audience qualification? Due to our current architecture with AEP, we're unable to get streaming segments to work in our instance, because our current connect type is based on a batch type of connector. So, even though we have set the ingestion cadence to 15 mins and profiles + events update in the profile store <15 mins but still the streaming audience do not qualify in real/near-real time as the current connection type doesn’t supports it. All other factors necessary for streaming segment to qualify is satisfied, except the connection type. Creating a new connection would significantly delay our use case deployment. Hence we were exploring creating journeys that would trigger based on events. As am not aware about AJO (am an AEP dev), Just wanted to get expert opinion
I have enabled the “add an alternative path in case of timeout or error” option for an email action in an event-based journey.When I triggered an event, one profile entered the email action. Due to an error (the email address was missing in the event payload), the profile moved to the alternate path (timeout/error path).However, I’m confused about the statistics shown on the End node:Entered: 2 Error: 1Since only one profile went through the email action, shouldn’t the Entered count in the End node be 1?Also, since the alternative path is enabled, the email action itself does not show any error count, and instead, the profile continues via the alternate path. The End node then shows Error: 1.Can you please confirm if my understanding is correct?
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!
In AJO, if a message is queued during quiet hours and contains a dynamic attribute (e.g, price) that changes during that time: Will the message use the value from when the event was triggered or the latest value at the time of delivery after quiet hours? Our requirement is in the night time, price of products change ($10 to $9) so we have to ensure that the profiles paused in quiet hours are getting sent the email with correct price ($10) -- approach for this. Will using “Discard” option in Business Rules in this requirement work?.
I’m working on a transactional journey in Adobe Journey Optimizer that is triggered by an event tied to a Prospect Event Schema.At the same time the event is ingested, the same individuals are also being written to the Prospect Profile schema. I’ve validated this by comparing timestamps and primary IDs across both the Event and Profile datasets—data is being populated correctly in both places.To account for any latency, I’ve added a 15-minute Wait activity immediately after the event trigger to allow for profile ingestion and stitching.Data Structure Context Event Schema Does not contain consent values (true/false) Contains SourceID, which maps to commPreferenceType in the profile Profile Schema Contains commPreferences Includes both: commPreferenceType granted (consent flag) IssueAlthough the journey is triggered by the event, I am attempting to evaluate Profile data within a Condition (Optimize activity) to determine eligibility for email communicat
Hi Community Members@AmitVishwakarma @Asheesh_Pandey @kautuk_sahni @akshay_kashyap @bjoern__koth Any suggestions would be appreciated thank you Is it possible to expose the ranking formula score in Code-Based Experience so it can be accessed by third‑party systems requesting offers via the Edge Decisioning APII understand that this is a runtime activity where in the system will calculate the offer priority and provide the score https://developer.adobe.com/data-collection-apis/docs/endpoints/collect/https://experienceleague.adobe.com/en/docs/journey-optimizer/using/decisioning/experience-decisioning/experience-decisioning-rankings/ranking-formulas Code based Experience Logic!--scriptorstartfragment-->We are able to retrieve the offers that are eligible for this decision policy.The ranking formula is available under subPropositions(base64 encoded values).However, we want to understand whether it is possible to send the ranking score as part of the response.If so, which attribute
Looking for some best practices on how to manage/contain all of our audiences. As more and more campaigns come through, our audience list gets larger and larger with some not being deactivated after the campaign is finished, duplicates, etc. Some questions about capabilities are below. Thanks for your help! Is it possible to look at inactive/deactivated audiences? For audit purposes, we would like to keep a list of audiences we are deactivating to show they aren’t in use anymore. Obviously we can use the UI tool and filter, but this might quickly become not enough. Looking into using a query/API but unsure if possible. Is there a way to see audiences that are being used in a live journey currently? With out large list of audiences, some might have been used in multiple journeys and before deactivating them, we would like to check if they are actively being used. I thought there was a safeguard in place that when you deactivate an audience, it would not let you if it was being used, b
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
I am trying to solve a particular use case whereby I use a custom wait activity to determine how long to wait before a customer is sent communications. This custom wait activity needs to based on the customer’s Australian time zone. Importantly we do not have time zone preference details enabled in AEP/AJO because we do not have this source data. We might in the future. Therefore I am trying to determine if we can use the advanced expression editor to write the necessary logic within the journey to determine the customer’s wait time. GOAL: if time of event is X-time or later local time pass through the condition and send email/SMS, else wait Z-mins until it is X-time customer local time before continuing onto the next journey node. I want this to automatically calculate/adjust for daylight savings instead of manually updating wait times whenever daylight savings changes. For example if the goal is to send comms at 12pm noon, this means if the customer is in WA (Western Australia [Pert
If I am establishing a business rule in EST timezone, and if the journey is running continuously for a year - will Adobe automatically accomodate for DST changes or will the daylight-saving timing change need to be done by the developers manually? Please confirm the same.
Hi Team, Can anyone please let me know who creates/owns the mail boxes for From and Error email addresses in AJO Channel surface config when the subdomain for this channel surface is CNAME delegated instead of full delegation ? @SatheeskannaK
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
Hello Everyone, I'm working on a use case, where I'm receiving 2 streaming events for same profile at exact same time. The journey is setup using unitary events. Both events getting ingested into dataset. But in Profile's event tab, I see only one event. For a profile, journey re-entrance is set to 1 second, so that for some cases if the profile with same identifier comes after a second it should get processed. Looks like journey is getting triggered for only one(first) event, since both events are hitting AJO at same time, though there is difference(of 9 second) in timestamp between 2 events.Payload1:{ "emailAddress": "<user address>", "ProfileID":"9876543212PSR", "Code":"PP003", "channel": "Email", "communicationName":"Project Started", "_id": "1123457QWER0", "eventType": "ajocommunication", "timestamp": "2026-04-02T11:59:48.384Z", "address" :"NULL", "projectName" : "Ebill", "status": "NULL", "date": "NULL", "action": "NULL", "trackingCode": "ABCD123
Hi! I am seeing an unexpected delay with a Weekly Quiet Hours rule (Queue message).Configuration:Window: 10:00 PM to 8:00 AM (Recurring daily). Timezone: Buenos Aires (GMT-3). Frequency Capping: None.The Issue:A profile reached a Push node on Tuesday at 4:20 AM. Expected: Sent Tuesday at 8:00 AM. Actual: Sent Wednesday at 8:00 AM (27-hour delay).Questions:Does AJO treat an overnight window (where End Time < Start Time) as a single block that concludes on Day+1? Because the profile arrived at 4:20 AM on Tuesday, did the system assign it to the "Tuesday Rule" (ending Wednesday 8 AM) instead of the "Monday Rule" (ending Tuesday 8 AM)? Is this behavior documented? What are your reccomendations? Thanks!
I’m looking to create highly personalised data driven Kinetic emails. Would anyone be able to help me with this or provide any additional information as to what is supported in AJO?
Vous avez déjà un compte d'utilisateur ? Connexion
Pas encore de compte ? Créer un compte
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
