Adobe Journey Optimizer

In Adobe Orchestrated Campaign (OCM) Allow Real-Time Customer Profile attributes to be queried directly within the Build Audience step. Why is this feature important to you Requiring an audience to be pre-created just to access standard profile attributes adds unnecessary steps to the workflow, increasing the time it takes to deploy campaigns and cluttering the platform with single-use audiences. How would you like the feature to work The Build Audience node should feature a direct integration with the RTCDP attribute library, allowing marketers to segment against profile data natively without relying on a pre-built Read Audience node. Current Behaviour Real-Time Customer Profile attributes cannot be queried directly within the Build Audience step; they are only accessible if an audience is pre-created and utilized via a Read Audience start node

In Adobe Orchestrated Campaign (OCM) Introduce a native activity to dynamically update profile attributes during campaign execution. Why is this feature important to you As users progress through an orchestration flow, their state changes (e.g., "engaged," "offer viewed"). We need the ability to write these state changes back to the profile mid-flight to ensure real-time accuracy across other integrated Adobe Experience Cloud solutions. How would you like the feature to work Provide an "Update Profile" action node within the OCM canvas that allows practitioners to write specific values or calculated attributes back to the XDM profile in real-time as the profile passes through the node. Current Behaviour There is no native activity available to update profile attributes dynamically during campaign execution  

In Adobe Orchestrated Campaign (OCM) Bring support for Custom Actions to message external third-party endpoints into the Orchestrated Campaign framework. Why is this feature important to you Modern tech stacks require seamless API connectivity to systems outside the Adobe ecosystem (e.g., Slack, Zendesk, legacy CRMs). The inability to trigger external custom actions fragments the customer journey and limits omnichannel orchestration. How would you like the feature to work Enable the same Custom Action framework available in AJO within the OCM canvas, allowing us to configure and trigger outbound webhooks and API calls as standard orchestration nodes. Current Behaviour Custom Actions for messaging external third-party endpoints are not currently supported within the OC framework 

 In Adobe Orchestrated Campaign (OCM), Provide a global campaign-level setting to define and restrict profile exit behavior across the orchestration engine. Why is this feature important to you In complex campaigns, business rules (like a sudden unsubscribe, a purchase event, or an exclusion segment qualification) dictate that a profile must immediately exit the campaign. Managing this node-by-node is error-prone and inefficient. How would you like the feature to work Include a "Global Exit Criteria" configuration panel at the campaign level, where architects can define universal rules that immediately remove a profile from the orchestration flow if met. Current Behaviour The orchestration engine lacks a global campaign-level setting to restrict profile exit behavior 

Improve the Adobe Orchestrated Campaign (OCM) orchestration canvas by allowing manual adjustment of connecting paths (up/down/left/right), similar to the AJO Journey canvas. Why is this feature important to you Enterprise orchestration workflows can become highly complex and visually dense. A rigid, linear canvas makes it incredibly difficult to map, read, and present workflows to stakeholders. Visual flexibility directly impacts practitioner efficiency. How would you like the feature to work Implement the drag-and-drop spline/routing logic currently used in Adobe Journey Optimizer, giving users the freedom to organize nodes and curve lines to optimize screen real estate. Current Behaviour Unlike the AJO Journey canvas, the connecting paths between orchestration nodes are linear and rigid, preventing manual adjustment (up/down/left/right) to optimize screen space or visual flow  

 In Adobe Orchestrated Campaign (OCM) Allow access to Real-Time Customer Profile attributes across all campaign starting nodes, not just Read Audience. Why is this feature important to you Flexibility in how campaigns are initiated is a core requirement for dynamic marketing. Restricting RTCDP access arbitrarily based on the entry node limits the architectural freedom to design trigger-based or event-driven orchestrations. How would you like the feature to work Real-Time Customer Profile attributes should be universally queryable and accessible regardless of whether the campaign begins with a Read Audience node or another entry mechanism. Current Behaviour Real Time Customer Profile attributes are only accessible when a campaign starts with a Read Audience

In Adobe Orchestrated Campaign (OCM) Expand the character limit for survey and review links stored in relational tables beyond the current 250-character maximum. Why is this feature important to you Modern tracking links, surveys, and dynamically personalized URLs heavily utilize query parameters for attribution and context, often easily exceeding 250 characters. This limitation causes broken links and truncated data. How would you like the feature to work Increase the character allowance for URL string fields in relational tables to better align with standard web practices (e.g., 2048 characters). Current Behaviour Survey and review links can be max 250 characters in relational table

OCM audiences utilized within Adobe Journey Optimizer (AJO) Journeys should retain and carry forward their specific enrichment attributes. Why is this feature important to you The true value of an Orchestrated Campaign lies in the rich data compiled during its workflow. When this data drops off as the audience enters a Journey, we lose the context required for deep, individualized downstream messaging and decisioning. How would you like the feature to work When an OCM audience triggers an AJO Journey, the journey payload should automatically inherit all enrichment attributes calculated during the orchestration phase, making them available for personalization in the Journey canvas. Current Behaviour OCM audiences used in Journeys do not carry their enrichment attributes into the journey flow.

 In Adobe Orchestrated Campaign (OCM) Extend the availability of aggregate functions (e.g., SUM, COUNT, AVG) to the Build Audience step. Why is this feature important to you Marketers often need to build audiences based on aggregated behavioral metrics (e.g., "users who have made more than 3 purchases"). Forcing this logic down into the Enrichment phase creates unnecessary complexity when it should be a primary segmentation driver. How would you like the feature to work The UI for the Build Audience step should expose the same aggregate function capabilities currently reserved for Enrichment activities. Current Behaviour Aggregate functions are currently available in Enrichment activities but not within the Build Audience step

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

When building campaigns and journeys, teams often need on-brand visuals at the speed of iteration—without exporting work to disconnected design tools for every small change. Journey Optimizer’s AI Assistant for images, combined with Generative models under Brands, lets you choose how images are generated (default Adobe, partner, or custom Firefly models) and use prompts and settings directly in the content editor.This guide explains what generative models are in AJO, when to use them, where to configure them vs where authors use them, and pitfalls to avoid—so your team can roll this out safely and consistently.Official references: Create and manage generative models, Generate images with AI Assistant.  When to use this patternUse Generative models + AI image generation when:You need new or refreshed imagery for email, web, landing pages, or push inside Journey Optimizer’s content editor, not only static uploads.You want brand-aware generation: authors pick a Brand, tune the prompt, and

DescriptionWe are using AJO to automate email, with email HTML being sourced dynamically via AJO Integrations(Beta) and Custom Actions from an external email creation platform (e.g. Stensul, Wordpress). Current workflow:An external team builds emails in Stensul. AJO then calls the Stensul API via AJO Integration (Beta) to retrieve fully rendered HTML, which is injected into an AJO email template and then sent in a Journey. We have also tried this process pulling content from Wordpress and have had success.This workflow functions correctly from a delivery perspective; however, we have identified a limitation related to link tracking and analytics. Observed LimitationChannel Configuration URL parameters and click tracking are correctly appended to links when emails are authored natively within AJO. However, links contained within externally sourced HTML (via Integrations) or URLs returned from Custom Actions are not rewritten by AJO at send time. As a result, these links do not receive t

In all Sandboxes, prod and test, we sometimes need to clean up the environment. Meaning f ex deleting old Journeys, not used Journeys and Journeys used for testing. Today it is only possible to delete Journeys one by one. It would be better if there where a option where you could select several Journeys and batch delete them with one click. Deleting one by one seems unnecessary and time consuming.  

Capping Business rules in Admin section is only applied for the highest-priority identity namespace. We have few identities with our Hybrid data modal and would like an option to be align capping with the selected identity.

We are facing a editorial challenge when users are creating emails in the email designer. This is regarding the use of email fragments. We have created many different fragments as design elements/modules, and in all of this fragments we are using variables to control how the fragment should look like. F ex we use variables to choose between pre defines background colors, we use variables to set the alignment of the content (can vary from mobile to desktop), we have different styling of CTAs etc. Today this settings needs to be done before the fragment is broken, and the content can be edited. The challenge is after the fragment is broken we cant change the variable settings from the interface.But there is a work around, and this is not user friendly. From the code editor we can access the fragment code, and by finding the right place in the code we can manually change the chosen value of the variable. And this is reflected in the template when we save the change.It would be very helpfu

In our daily work we are facing a challenge when it comes to maintaince of email templates build from fragments. We are using different pre-defined templates that is built from fragments. And the fragments again contains just dummy images and lorum ipsum texts. The users changes the content in the fragments when they create there Journeys with there emails. The issue we are facing is when a content designer wants to change the template that is in use in an running Journey – there will be a problem. The content designer could have ordered a total new template, with a new look that he wants to use (a new framwork) or simply just want to change to another existing template (could be seasonal variations in the design). When you use the “change design” feature in the email, and changes to another template – you use all your created content in that email you are changing design too. It should have been possible to keep your content when you change the underlaying template.Maybe it could be s

Description:We use a specific naming structure for our Journeys and our message names.  We want to be able to Query this Name when creating an audience, instead of having to use Journey ID or Message ID.   Why is this feature important to you:As I empower more teams to work on campaigns as standalone teams, including test variations with split tests, I need to have overarching criteria that will allow me to all audiences who have received a type/class of mailing without having to create a manual list of Journey ID or message IDs   How would you like the feature to work:For instance, if all emails with an Offer use "-OFFER-" in the message name, then I want to be able to create and audience with anyone who has received a message with "-OFFER-" in last X months and not have to recall all the journey IDs.  Similarly, if a customer has been in any journey that begins with "XYZ-" in last X day I want may want to exclude them. I don't want to have to s

In Queries > Templates, there is currently no way to organise query templates beyond a flat list with a search bar. As the number of templates grows, this creates several usability challenges: No ability to create folders or group queries by use case, brand, or purpose Users must remember the exact query name to find it The search is case-sensitive, so queries cannot be found unless the name is typed exactly This often results in duplicate or sample queries being recreated multiple times, leading to clutter and inefficiency For teams working extensively with queries (especially in enterprise environments), this significantly impacts productivity and governance.

We have a requirement to apply different capping thresholds to different placements,For a given customer A show offer B, X times in Placement C or Y times in Placement Dwhere X <> YFor example,For customer Andrew, show LOAN offer, 3 times over 7 days in Header placement or 2 times over 14 days Footer placement My idea would be to include an optional placement qualifier (“Placement name”) when selecting “Apply capping to each placement” as shown above. Capping would then apply to “Placement name” only and not all placements. Note that placement capping is “Offer Decisioning” functionality, which would need to be re-introduced into experience decisioning.  

When we try to send emails from AJO we get this alert. Saying that the opt-out link is missing in the body.But his is not entirely true. The link is there, but is placed inside a fragment. To us it seems like AJO is not able to see this link when it is inside a fragment, and then returns a alert. We have placed the link inside a footer fragment, that is not broken before sending the email. We are also using if/or logic controlled by variables to show the right language for that link. This also might be a reason for AJO is not able to recognize the link. But it is there, and it is working. Could the code checker that looks for this opt-out link also try to look for this code inside fragments?

We often run into all kind of problems with the email designer during a AJO upgrade/release. Created content disappears, variable settings used in fragments changes/disappears, Image sizes changes etc etc. All this things come back from the users as bug reports. When investigating the issues, we often need to conclude that the error/experienced behavior most come from hickup in the code during the code upgrade. Suddenly all is back to normal again, the day after, without changing anything. Out theory is that a AJO upgrade/code change possible has some impacted on the use of the email designer during the code upgrade. Maybe it is hard or difficult to store things at the same time the source code is been updated. At least we experience that it might be a challenge here.   We would therefor like to have the option to “lock” the email editor and other components that creates things in AJO during an update . The lock could explain that this feature is temporary locked caused by an code upgr