Adobe Journey Optimizer

Use case: We would like to target customers on below qualified dates and be suppressed if they don’t meet qualified date. So, looking for the solutions to manage dynamic qualified date in the journey if possible. 2 days before 1st Friday of each month e.g. Apr 1, 2026 1st Friday of each month e.g. Apr 3, 2026 1 month after 1st Friday (on 1st Friday only) e.g. May 1, 2026 2 months after 1st Friday (on 1st Friday only) e.g. Jun 5, 2026 3 months after 1st Friday (on 1st Friday only) e.g. Jul 3, 2026

In Adobe Orchestrated Campaign (OCM) Provide functional significance to the "Enable for Segmentation" toggle present on relational schemas. Why is this feature important to you UI elements that have no backend functionality create confusion for data architects and marketers during implementation, leading to unpredictable behaviors and wasted configuration effort. How would you like the feature to work If the toggle is present, it should actively allow the fields within that relational schema to be leveraged in the standard AEP segment builder. If this is not technically viable, the toggle should be removed from the UI to prevent confusion. Current Behaviour The “Enable for Segmentation” toggle on relational schemas has no current significance

Enable Adobe Journey Optimizer (AJO) Journeys to natively query and consume data residing in relational tables. Why is this feature important to you Siloing relational data strictly to Orchestrated Campaigns creates a disjointed architecture. Real-time journeys often need contextual data (like store inventory or loyalty tier lookups) that is best suited for relational storage. How would you like the feature to work Allow AJO journey conditions and personalization syntax to securely reference and pull data from relational schemas linked to the primary profile. Current Behaviour Relational tables are designed for OC only and cannot be directly consumed by AJO Journeys

In Adobe Orchestrated Campaign (OCM) Introduce a native, automated feature to clone XDM profiles into relational stores without dual-ingestion or Query Service workarounds. Why is this feature important to you Architectural simplicity reduces technical debt and maintenance costs. Forcing data engineers to ingest data twice or build scheduled Query Service scripts just to populate relational tables is an inefficient use of platform resources. How would you like the feature to work Provide a UI-driven toggle or standard data prep mapping function that allows specific XDM profile attributes to automatically sync or "clone" into designated relational schemas upon ingestion. Current Behaviour There is no free auto clone feature for xdm profiles into relational stores; data must be ingested twice or derived via Query Service

In Adobe Orchestrated Campaign (OCM) Enhance the test profile creation wizard to include functional hooks for updating or populating relational tables via CSV upload. Why is this feature important to you Robust QA requires highly specific, multi-dimensional test data. The inability to inject test data directly into relational tables hinders our ability to thoroughly validate complex orchestration workflows that rely on those data structures. How would you like the feature to work The test profile wizard should support a CSV template upload that maps test identifiers not only to XDM profile attributes but directly to custom fields within linked relational schemas. Current Behaviour The test profile creation wizard lacks placeholders or functional hooks to update or populate corresponding test data within relational tables via CSV upload  

 In Adobe Orchestrated Campaign (OCM) Update the standard AEP Profile UI to display relational store attributes and cross-table relationships. Why is this feature important to you A true 360-degree customer view is the primary promise of the Adobe Experience Platform. If relational data used heavily in orchestration is hidden from the Profile UI, practitioners cannot easily validate data ingestion or troubleshoot personalization logic.  How would you like the feature to work The Profile UI should include a dedicated tab or widget that surfaces the underlying relational data and schema links associated with that specific profile's primary identifier. Current Behaviour Relational store attributes and cross-table relationships are not reflected in the standard Profile UI, preventing a unified “360 view” of a specific profile’s relational records

In Adobe Orchestrated Campaign (OCM) Enhance saved audiences to support incremental evaluation (entries and exits) rather than requiring full static snapshot re-evaluations. Why is this feature important to you Processing efficiency is critical when dealing with millions of profiles. Forcing a full re-evaluation is computationally expensive and delays the timely execution of campaigns that only need to trigger on net-new audience entries or exits. How would you like the feature to work Provide an option for saved audiences to evaluate continuously or incrementally, accurately flagging profiles that have recently qualified for or fallen out of the audience parameters. Current Behaviour Saved audiences function as static snapshots requiring full re-evaluation; they lack method to identify incremental entries, exits

In Adobe Orchestrated Campaign (OCM) Update the orchestration canvas UI to display unique profile counts rather than total records. Why is this feature important to you Architects and marketers rely on canvas counts for immediate sanity checks and sizing estimates. Displaying total records instead of unique profiles artificially inflates the perceived audience size, leading to misaligned expectations for campaign reach. How would you like the feature to work The numbers displayed above nodes and paths on the canvas should represent deduplicated, unique XDM profiles flowing through the orchestration step. Current Behaviour Counts displayed on the orchestration canvas represent total records rather than unique profiles

In Adobe Orchestrated Campaign (OCM) Enable the orchestration engine to dynamically re-evaluate consent and opt-in status mid-execution rather than relying on a static snapshot. Why is this feature important to you Compliance with privacy regulations (GDPR, CCPA) requires strict adherence to real-time consent. If a user opts out while a multi-day orchestrated campaign is running, they must be immediately suppressed from downstream deliveries. How would you like the feature to work The engine should natively ping the profile's consent attributes immediately prior to any delivery or action node, ensuring messaging is suppressed if the opt-in status has changed since the campaign started. Current Behaviour Consent opt in status is a static snapshot taken at the start and does not update mid execution

Provide native support and integration for Offer Decisioning capabilities within Orchestrated Campaigns. Why is this feature important to you Next-best-action and dynamic offer management are core to delivering personalized experiences at scale. Orchestration tools must be able to resolve and deliver centralized offers to ensure consistent messaging across channels. How would you like the feature to work Provide an "Offer Decisioning" node or native integration within messaging nodes in OCM, allowing the engine to fetch and append the highest-ranked offer for a profile dynamically during execution. Current Behaviour Native integration with Offer Decisioning capabilities is not currently supported

Integrate Send Time Optimization (STO) capabilities natively within Orchestrated Campaign execution. Why is this feature important to you Maximizing engagement requires reaching customers when they are most likely to interact. AI-driven STO is a standard expectation for modern marketing automation; lacking it degrades the performance of orchestrated communications compared to standard AJO journeys. How would you like the feature to work Include an STO toggle or configuration setting on messaging/delivery nodes within the orchestration canvas to optimize the dispatch time based on AI profile scoring. Current Behaviour Send Time Optimization (STO) is currently absent in orchestrated execution

Ensure orchestrated campaigns generate standard journey step events datasets for comprehensive execution reporting. Why is this feature important to you Robust analytics and observability are non-negotiable for enterprise deployments. Without step-event datasets, feeding orchestration performance data into Customer Journey Analytics (CJA) becomes incredibly difficult, leaving stakeholders blind to node-level drop-offs and operational metrics. How would you like the feature to work The orchestration engine should automatically log standard step events (entry, exit, error, transition) into an AEP dataset, identical to how AJO logs journey step events. Current Behaviour Orchestrated campaigns do not generate standard journey step events dataset

In Adobe Orchestrated Campaign (OCM) Enable direct access to Federated Audience Composition (FAC) attributes within the Build Audience step. Why is this feature important to you Federated data is crucial for enterprises maximizing external data warehouses. Forcing practitioners to publish to the Audience Portal and ingest via Read Audience breaks the seamless experience FAC is meant to provide, adding latency and administrative overhead. How would you like the feature to work FAC attributes should be natively accessible and selectable directly within the Build Audience node's configuration UI. Current Behaviour Federated Audience Composition (FAC) attributes are inaccessible in the Build Audience step unless the audience is first published to the Audience Portal and ingested via a Read Audience node

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