On this page: Explore Coworker capabilities in Adobe Journey Optimizer for creating journeys, generating channel content, analyzing performance and journey inventory hygiene, tracing profiles through a journey, and simulating journey behavior.
Coworker brings natural-language tools into Adobe Journey Optimizer to help you create and configure journeys, generate channel-specific content, analyze performance, trace profiles through a journey, and simulate journey behavior.
Learn more:
- Coworker skills for Journey Optimizer — overview of Coworker skills across Journeys, Loyalty, Content Management, and Decisioning in Journey Optimizer.
- Coworker documentation — overview of Coworker’s Campaigns, Chat, and Projects capabilities.
- Coworker Chat UI guide — how to access and navigate Coworker Chat.
Journey tools journey-tools
Journey Create journey-create
Journey Create enables Journey Optimizer users to build and configure marketing journeys using a natural language interface. With Journey Create, practitioners can quickly create journeys by describing their requirements in conversational prompts. The skill walks users through the different options for creating a journey, allowing marketers to focus on strategy rather than technical configuration.
Key use cases
Journey Create offers capabilities that can be leveraged to accelerate marketing execution:
With this skill, natural language requirements are translated into structured journey configurations.
Prompting best practices
To maximize the effectiveness of Journey Create, follow these best practices:
- Be Specific: Provide clear details about your journey goals, target audience, and desired actions. Include information about channels, timing, and conditions.
- Specify Timing: Clearly indicate wait periods between actions and when the journey should start.
- Define Conditions: When using conditional logic, explain the criteria for each branch path.
- Include Channels: Specify which communication channels you want to use (push, email, mobile message).
- Mention Scheduling: For scheduled journeys, provide the desired start date and time.
- Custom Actions: If you are using custom actions in your workflow you need to specify that you are using a custom action along with the exact name of the custom action. Example:
When a user enters my store location send a welcome message using custom action ExternalPush. Wait 2 days and then send a follow up message using custom action ExternalEmail with a survey on their visit. - Validate Expressions: Make sure to check and validate any expressions that Journey Skills create to ensure that the correct fields and values are used.
Out of scope skills
The following functionalities are currently not supported:
- Advanced journey analytics
- Cross-journey orchestration
- A/B testing configuration
- InAudience expression generation
- Dataset lookup nodes
- Wave sending settings
- Schedule recurrence options
- Namespace selection for audiences
- Custom Action field mapping
- Complex data transformations
Setup best practices
- Define Clear Objectives: Before creating journeys, establish clear goals (improving retention, driving conversions, increasing engagement).
- Prepare Audiences: Ensure your target audiences are already created and properly segmented.
- Plan Message Content: Have your messaging strategy defined before journey creation.
- Consider Customer Experience: Design journey flows that respect customer preferences and avoid over-communication.
Channel Content Create channel-content-create
Channel Content Create enables Journey Optimizer users to generate, edit, and manage channel-specific content for journeys using AI-powered content generation.
Key use cases
Prompting best practices
- Be Specific: Provide clear details about the content type, tone, target audience, and key messaging.
- Specify Channel: Clearly indicate which channel you are creating content for (email, push, mobile message).
- Define Tone: Specify the desired tone (friendly, formal, casual, urgent).
- Iterate and Refine: Use the regenerate action to refine content until it meets your requirements.
Journey Analyze journey-analyze
Journey Skills enable Journey Optimizer users to analyze and optimize journeys using a natural language interface. With Journey Skills, practitioners can quickly identify and resolve schedule and/or audience conflicts, detect points of user abandonment in a journey, scan for broken configurations and silent failures, and provide actionable recommendations to improve journey health. It empowers practitioners to make data-driven decisions, improve customer engagement, and streamline journey orchestration.
Key use cases
Journey Analyze offers a range of functionalities that can be leveraged to optimize marketing efforts:
Prompting best practices
To maximize the effectiveness of Journey Analyze, follow these best practices:
- Be Specific: Use clear and concise prompts to get targeted insights. For example, instead of asking “What are my journeys?”, specify “List all journeys created in the last month.”
- Combine Insights: Integrate insights from Audience and Data Insights capabilities for a holistic view of journey performance.
- Iterative Refinement: Use fallout and overlap analysis to iteratively refine journey design and scheduling.
Setup best practices
- Define Clear Objectives: Before analyzing journeys, establish clear goals (e.g., improving retention, increasing conversions).
- Monitor Regularly: Schedule regular reviews of journey performance to identify trends and anomalies.
- Optimize Segmentation: Ensure audience segmentation is balanced to avoid fatigue and maximize engagement.
Journey Execution Timeline journey-execution-timeline
Journey Execution Timeline enables Journey Optimizer users to get the end-to-end timeline of a Read Audience (batch or scheduled export) journey batch, using a natural language interface. The skill shows how long a batch took, when the audience export, the journey execution, and the delivery started and ended, and the profile-level P95 and P99 for entry, exit, or execution time. Before answering, the skill validates the journey against the journey model. If the journey is not a Read Audience journey, the skill stops instead of approximating a result.
Key use cases
Limitations
- Journey Execution Timeline supports Read Audience journeys only. For any other journey type, the skill stops and does not approximate a result.
- Audience export latency is measured from the creation of the export job to the first profile entry. It does not cover the processing stages that occur after the export job is created.
- Recipient-side or device-side notification receipt and display timing is not reliably available from standard Journey Optimizer datasets, so the skill reports that metric as unavailable instead of estimating it.
- The skill is read-only and cannot change journey configuration.
The following analyses are handled by the Journey Analyze skills:
- Journey Fallout Analysis: per-node timing, per-node P95 and P99, and drop-off.
- Analyze Journey Anomalies: volume and count anomalies.
- Journey Custom Action Error Analysis: custom action errors and latency.
- Journey Audience Overlap Analysis and Journey Schedule Overlap Analysis: audience and schedule conflicts.
Trace Journey Profile trace-journey-profile
Trace Journey Profile is a read-only skill that returns profile-level execution data for a published journey, based on journey step events. Use it to see how profiles moved through a journey, which profiles errored and why, or the path of a single profile from node to node.
The errored-profile lookup and the single-profile trace return profile-level data.
Limitations
- Trace Journey Profile works on published journeys only. It does not support journeys that were never published (draft-only) or B2B journeys.
- It is read-only. It does not export lists or edit journeys.
- For fallout analysis, volume anomalies, or custom action error trends, use Journey Analyze.
Journey Simulation journey-simulation
Journey Simulation skill brings AI-driven Quick Simulation into the chat interface, letting users validate a journey’s logic conversationally. Through Coworker, users can generate simulated test data, run and manage a simulation, and review the results.
Key use cases
Limitations
This feature currently only supports the Quick Simulation flow, and does not fully replace the Journey Optimizer manual simulation experience. Use Quick Simulation for a fast, automated sanity check of a journey’s logic. For granular control over simulated users and scenarios, use the manual simulation experience in Journey Optimizer.
As part of this Quick Simulation experience, users cannot:
- Choose an existing saved simulated user for a run.
- Edit a simulated user before rerunning a simulation.
- Create, browse, update, or delete persistent simulated users through chat.
- Target a specific path or custom test case.
This section contains structured knowledge intended to support interpretation, retrieval, and question answering related to this topic.
For complete understanding, this information should be combined with the documentation on this page. Neither source is intended to stand alone; the page describes the feature, while this section provides additional context that helps disambiguate terminology, intent, applicability, and constraints.
- TL;DR: This page documents five Adobe CX Enterprise Coworker skills for Adobe Journey Optimizer journeys — Journey Create, Channel Content Create, Journey Analyze, Trace Journey Profile, and Journey Simulation — plus the Compare journey versions tool, with their use cases, scope, prompting guidance, and limitations.
Intents
- Build and configure journeys from natural language prompts or uploaded images using Journey Create.
- Generate, edit, and refine channel-specific content for journeys using Channel Content Create.
- Run a Quick Simulation to exercise journey paths, then review step-by-step traversal and branch outcomes using Journey Simulation.
- Analyze journey fallout, audience overlap, schedule conflicts, custom action errors, anomalies, performance, and journey inventory hygiene using Journey Analyze.
- Trace profiles through a published journey (node and branch counts, errored profiles, single-profile traces) using Trace Journey Profile.
- Compare journey versions with Journey Version Comparison and review a structured diff of nodes, connections, and journey-level properties.
- Learn each skill’s permissions, scope, and limitations.
Glossary
- Journey Create (product-specific): CX Coworker skill that builds and configures marketing journeys through natural language prompts.
- Channel Content Create (product-specific): CX Coworker skill that generates, edits, and manages channel-specific content (email, push, SMS) for journeys using AI-powered content generation.
- Journey Analyze (product-specific): CX Coworker skill that analyzes and optimizes journeys, covering fallout analysis, audience overlap analysis, schedule overlap analysis, operational insights, custom action error analysis, anomaly detection, business performance analysis, and journey hygiene analysis.
- Trace Journey Profile (product-specific): CX Coworker skill that returns read-only, profile-level execution data for a published journey, based on journey step events.
- Journey Simulation (product-specific): CX Coworker skill that uses Quick Simulation in chat to generate simulated test data, run or manage a simulation, and review results.
- Quick Simulation: The simulation flow available in Coworker for a fast, automated sanity check of journey logic.
- Journey Fallout Analysis: identifies where and why customers drop off during a journey.
- Journey Audience Overlap Analysis: analyzes audience overlap across multiple journeys to prevent fatigue from over-targeting.
- Journey Schedule Overlap Analysis: detects timing conflicts between scheduled journeys targeting the same audience.
- Analyze Journey Anomalies: detects unexpected spikes, drops, or flatlines in a journey’s entry, exit, or send counts compared to historical baselines, confirms whether a flagged change is a genuine anomaly, and runs read-only diagnostics to identify a likely root cause.
- Business Performance Analysis: evaluates journey performance, highlights trends and bottlenecks, and recommends concrete optimizations to improve engagement and conversion.
- Journey Hygiene Analysis: identifies journeys with missing or generic names; stale draft journeys more than 30 days old that have never been published and have not been modified; stale live journeys more than 90 days old; oversized journeys with 50 or more nodes; long-existing closed journeys more than 90 days old; and similar action and event names. It provides recommendations to clean up and stabilize the journey inventory. A sample prompt is “Audit my journeys configuration.”
- Node and branch counts: Trace Journey Profile query that shows how many profiles entered a node, how many stopped there, and how they split across branches, as counts and percentages.
- Errored-profile lookup: Trace Journey Profile query that shows which profiles errored over a period such as the last 7 days, at which node, and why.
- Single-profile trace: Trace Journey Profile query that shows a profile’s node-by-node path with timestamps, the attribute value evaluated at each condition node, and the exit point and reason.
- Journey Version Comparison: Coworker tool that compares two journey versions and returns a structured diff of added, removed, modified, and moved nodes, changed connections, journey-level property changes, and roll-up counts.
Guardrails
- Journey Create requires the following permissions to be fully used: Manage Journeys, View Journey Events, Data Sources and Actions, View Segments, and Manage Segments.
- Channel Content Create is available for all customers in Limited Availability; contact your Adobe representative to gain access.
- Journey Analyze is available for all customers who have access to Coworker; full use requires the View Journeys, Manage Journeys, View Segments, and Manage Segments permissions.
- Trace Journey Profile is read-only and works on published journeys only. It does not support journeys that were never published (draft-only), B2B journeys, list export, or journey edits, and it does not cover fallout analysis, volume anomalies, custom action error trends, or Read Audience batch timelines; use Journey Analyze for fallout, anomalies, and custom action errors.
- Journey Simulation currently supports only the Quick Simulation flow and does not fully replace the manual simulation experience. Users cannot use chat to choose an existing saved simulated user or edit one before rerunning, create, browse, update, or delete persistent simulated users, or target a specific path or custom test case.
Terminology
- Synonyms: “Journey Analyze” = “Journey Skills” — the page introduces the Journey Analyze section using the term “Journey Skills” to refer to the same capability.
- Do not confuse: “Journey Create” (builds new journeys) is not the same skill as “Journey Analyze” (analyzes and optimizes existing journeys), “Trace Journey Profile” (traces profiles through a published journey), or “Channel Content Create” (generates channel content for journeys) — each is a distinct Coworker skill on this page.
- Do not confuse: “Trace Journey Profile” is its own skill, not a use case of “Journey Analyze”. Fallout analysis, anomalies, and custom action errors belong to Journey Analyze.
- Do not confuse: Quick Simulation is a fast, automated sanity check; it does not replace the manual simulation experience for granular control over simulated users and scenarios.
FAQ
- What permissions do I need to fully use Journey Create? Manage Journeys, View Journey Events, Data Sources and Actions, View Segments, and Manage Segments.
- Is Channel Content Create generally available? It is available for all customers in Limited Availability; contact your Adobe representative to gain access.
- What does Journey Analyze detect? Journey fallout, audience overlap, schedule conflicts, custom action errors, anomalies in a journey’s entry, exit, or send counts, business performance trends and optimization opportunities, and journey inventory hygiene issues such as missing or generic names, stale or oversized journeys, and similar action and event names.
- What does Trace Journey Profile do? It is a read-only skill that answers three types of queries on a published journey: node and branch counts (how many profiles entered a node, how many stopped there, and how they split across branches), errored-profile lookup (which profiles errored, at which node, and why), and single-profile trace (a profile’s node-by-node path with timestamps, the attribute value evaluated at each condition node, and the exit point and reason).
- What does Journey Version Comparison show? A structured diff between two journey versions, including node changes with field-level details, changed connections, journey-level property changes, and roll-up counts.
- Does Quick Simulation replace manual simulation? No. It provides a fast, automated sanity check; use the manual simulation experience for granular control over simulated users and scenarios.
- Does Journey Create support cross-journey orchestration? No. Journey Create does not support cross-journey orchestration.