在此页面上：了解如何在Adobe Journey Optimizer中测试、发布和监视编排的营销活动，包括营销活动生命周期、执行日志和活动状态指示器。
在创建编排的活动并设计要在画布中执行的任务后，您可以发布该活动并监控其执行方式。 您还可以在测试模式下执行营销活动，以检查其执行情况和不同活动的结果。
Campaign生命周期概览 lifecycle
编排的营销活动可在定义的状态集中移动。 发布工作流程的关键阶段包括：
发布前测试营销活动 test
Journey Optimizer允许您在启动之前测试编排的营销活动。 创建营销策划后，其默认处于 草稿 状态。 提供了两个互补测试：
测试营销活动流程 test-flow
使用活动流测试手动执行工作流并验证其活动的编排方式。
要测试编排的营销活动，请打开该营销活动并选择开始。 活动按顺序执行，直到工作流到达渠道活动为止，在该渠道活动中，工作流将暂停，以便您可以通过 运行测试 来试运行。 如果没有渠道活动，则执行将持续到画布的结尾。
活动画布工具栏中的
对于触发的编排活动，系统会等待API调用启动该活动。 您需要发送信号以继续测试。 了解如何测试信号触发的营销活动。
在测试期间，您可以使用画布中的操作栏控制活动执行。 从那里，您可以：
- 随时 停止 执行。
- 再次 开始 执行。
- 重新启动执行以重置工作流并在单个操作中重新运行该工作流。 当您要在进行修改后快速重新测试营销活动流程时，这尤其有用。
- 恢复先前暂停的执行。
画布工具栏中的警报 / 警告图标会通知您问题，包括在执行之前可能主动出现的警告以及在执行期间或执行之后发生的错误。
您还可以使用直接显示在每个活动上的可视化状态指示器快速识别失败的活动。 有关详细的故障排除信息，请打开营销活动的日志，其中提供了有关错误及其上下文的深入信息。
活动流量测试具有您应该了解的重要执行约束：
-
工作流在渠道活动中暂停 — 工作流在到达渠道活动（如电子邮件、短信或推送）时暂停。 您可以使用 运行测试 单独执行该活动，但在执行渠道活动后，工作流不会继续后续活动。 这意味着在营销活动流量测试期间无法访问下游活动，例如其他渠道、条件或编排活动。
-
对测试策略的影响 — 无法在营销活动流测试中验证消息活动之后的逻辑，例如条件分支或多渠道工作流。 要对其进行测试，您必须发布活动并监视实时执行。
-
与实时执行的预期差异 — 在实时执行中，工作流按顺序继续运行所有活动，而不会在渠道活动中暂停。 在测试期间，这些暂停允许您验证每个步骤的消息内容和执行，但以不完整的工作流验证为代价。
测试渠道活动 run-test-channel
当营销活动流量测试到达渠道活动时，使用 运行测试 执行活动而不发送消息。 这将模拟发送，以便您可以在发布营销活动之前验证目标群体并确定排除项。
要测试渠道活动并查看其结果，请执行以下操作：
-
在画布中选择渠道活动，然后单击运行测试。
note NOTE 即使消息内容无效，运行测试按钮也可用。 检查画布工具栏中的警报 / 警告图标以了解与内容相关的错误，例如某个消息版本缺少内容。 修复报告的内容问题，然后再次运行测试。 -
成功执行测试后，选择 查看报告 按钮以打开其实时报告。
测试报告使用与实时报告相同的营销活动统计数据，但在测试期间不会发送消息。 了解有关营销活动实时报告的更多信息。
您还可以使用带有AEP测试用户档案和校样发送的模拟来预览和测试消息的内容。 在测试模式下启动营销活动，让工作流访问渠道活动以访问其测试用户档案；无需发布。 了解如何使用渠道活动和模拟内容。
发布营销活动 publish
在发布营销策划之前，请确认以下事项：
营销活动测试完成并准备就绪后，单击 发布 即可使其上线。
营销活动画布中的
可视化流程会重新启动，真实轮廓开始实时进入历程流转。
如果发布操作失败（例如，由于缺少消息内容），您将收到警报，必须在重试之前修复问题。 成功发布后，营销活动即开始执行（立即或按计划），从 草稿 状态移动到 实时 状态，并变为“只读”。
发布时间执行序列 publication-sequence
单击 发布 后，将在内部出现以下顺序：
- 计划程序激活 — 如果活动配置了计划，则计划程序将在定义的时间启动并触发执行。
- 保存受众活动首先运行 — 工作流中的任何保存受众活动在消息活动之前执行。 在受众门户中创建受众shell，并开始摄取符合条件的配置文件。
- 消息执行开始 — 渠道活动开始处理工作流中的第一个消息活动。
- 配置文件快照查找 — 配置文件数据是针对发布时拍摄的快照解析的，而不是针对实时配置文件解析的。 这可确保整个执行过程的一致性。
- 同意评估 — 对于匹配的用户档案，将直接从用户档案记录授予同意。 在发送时不会重新评估同意。 了解有关同意管理的更多信息
- 动态配置文件创建 — 在执行期间动态创建与现有记录不匹配的配置文件。
- 投放日志创建 — 投放事件记录在
ajo_message_feedback_event数据集中，该数据集是投放日志和发送后验证的主要来源。
要在执行后验证结果，请使用Journey Optimizer报表功能。 了解更多有关协调营销活动报告的信息
将营销活动恢复为草稿 back-to-draft
返回草稿功能允许您取消发布并还原编排的活动以在特定情况下草稿状态。 这是作为一种恢复机制，用于在发送任何消息之前修复问题，同时保持Campaign生命周期的完整性。
此选项在以下两种情况下可用：
-
等待执行的计划营销活动：如果计划在特定时间执行营销活动，但尚未达到该时间，则可以使用返回到草稿以在开始执行之前查看和修改营销活动。 但是，如果营销活动是定期的（例如每日计划的营销活动），并且已发生至少一次执行，则该选项不再可用。 在这种情况下，您应该改为复制营销活动。
-
存在执行错误的实时营销活动：如果营销活动在执行期间遇到错误并暂停，但尚未完成任何营销活动执行，则可以使用返回草稿修复错误并重新发布营销活动。
要将营销活动切换回草稿状态，请打开编排好的营销活动，然后单击营销活动画布工具栏中的 返回草稿 按钮。
将取消发布营销活动，并停止工作流。 营销活动返回到 草稿 状态。 您现在可以修复识别的问题，然后测试营销活动并在准备就绪后重新发布它。
确认消息发送 confirm-sending
默认情况下，对于非循环编排的活动，消息投放会暂停，直到您明确批准发送为止。 发布营销活动后，从渠道活动的属性窗格中确认发送请求。 在确认之前，渠道活动将保持挂起状态，并且不会发送消息。
发布之前，您可以从渠道活动属性窗格中禁用发送确认功能。 有关详细信息，请参阅确认消息发送。
监控营销活动执行情况 monitor
可视化流程监控 flow
在运行时（在测试或实时模式下），可视流量会显示用户档案如何实时在历程中移动。 此时会显示在任务之间过渡的轮廓数量。
通过过渡在活动之间传递的数据将暂存于临时工作表中。 可以为每个过渡显示此数据。 要检查在活动之间传递的数据，请执行以下操作：
-
选择过渡。
-
在属性窗格中，单击 预览架构 以查看工作表架构。 选择 预览结果 以查看传输的数据。
您现在可以检查在活动之间传递的数据，以验证营销活动流，并确认每个活动都在处理预期的用户档案。
活动执行指示器 activities
可视化状态指示器可帮助您了解每个活动的执行情况：
日志和任务 logs-tasks
监测日志和任务是分析编排的营销活动并确保其正常运行的关键步骤。 可从画布工具栏的测试模式和实时模式下的 日志 按钮访问日志和任务。
营销活动画布工具栏中的
日志和任务屏幕提供营销活动执行的完整历史记录，记录了所有用户操作和遇到的错误。
有两种类型的信息可用：
- 日志选项卡包含按时间顺序记录的所有操作和错误的历史记录。
- 任务选项卡详细列出了活动的逐步执行顺序。
在这两个选项卡中，您可以选择显示的列及其顺序，应用过滤器，并使用搜索字段快速查找所需信息。
设置警报 alerting
系统警报会提供关于编排活动中的问题的主动通知，因此您可以进行调查，并采取纠正措施，而无需持续检查监控视图。 您可以从管理 > 警报查看和管理可用警报。
有关可用警报以及如何订阅的信息，请参阅访问和订阅系统警报。
您还可以通过将 警报 活动添加到营销活动画布来创建自己的警报。 当营销活动执行到达活动时，将触发警报。 了解如何配置警报活动。
如果协调的营销活动返回错误代码，请参阅协调的营销活动错误。
后续步骤 next
开始编排的活动画布后，您可以使用Journey Optimizer报表功能获得见解，例如了解受众行为并衡量客户历程中每个步骤的表现。 了解更多有关协调营销活动报告的信息
是否有关于编排营销活动的问题？ 请查看编排的营销活动常见问题解答，以获取从业者最常见问题的解答。
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 explains how to test, publish, revert, confirm sending, and monitor Orchestrated campaigns in Adobe Journey Optimizer, including the campaign lifecycle, execution logs, activity status indicators, and alerts.
Intents:
- Test an Orchestrated campaign in Draft status before publishing.
- Test a channel activity with Run test, without sending the message.
- Publish a campaign and understand the internal publication-time execution sequence.
- Revert a published campaign back to draft status using Back to draft.
- Confirm message sending for non-recurring campaigns after publishing.
- Monitor campaign execution through the visual flow, activity status indicators, and logs and tasks.
- Set up system alerts or an Alert activity to be notified of issues.
Glossary:
- Draft: the default status when a campaign is created, in which the campaign is being built and tested and is not yet active (product-specific)
- Live: the status after a campaign has been published and is executing (product-specific)
- Completed: the status once campaign execution has finished (product-specific)
- Back to draft: a feature that unpublishes and reverts an orchestrated campaign to draft status in specific situations, designed as a recovery mechanism to fix issues before any messages are sent (product-specific)
- Confirm sending: the explicit approval step required, by default, before a non-recurring campaign’s channel activity sends messages after publishing (product-specific)
- Logs and tasks: the screen providing a complete history of campaign execution, recording all user actions and encountered errors, with separate Log and Tasks tabs (product-specific)
- Alert activity: a canvas activity that fires a custom alert when campaign execution reaches it (product-specific)
Guardrails:
- When testing a campaign in Draft status, all activities in the canvas are executed except Save audience activities and channel activities; there is no functional impact on your data or audience.
- In test mode, the workflow stops when it reaches a channel activity, so activities that follow a channel activity are not reached; test each channel activity with Run test. The logic that follows a message activity can only be validated by publishing the campaign and monitoring live execution.
- The test does not include the message rendering step; profiles can be excluded at send time on a rendering error even when the content is valid, and these exclusions might not appear in the test report.
- For triggered orchestrated campaigns, testing requires sending an API call signal to continue the test; the system waits for this call to start the campaign.
- The Publish button is disabled (greyed out) if there are unresolved errors; all errors must be fixed before publishing.
- On successful publishing, the campaign moves from Draft to Live status and becomes “Read only”.
- By default, for non-recurring orchestrated campaigns, message delivery is paused after publishing until the send is explicitly confirmed from the channel activity’s properties pane; until confirmed, the channel activity stays pending and no message is sent.
- Back to draft is available for scheduled campaigns awaiting execution only while the scheduled time has not yet been reached; if the campaign is recurring and at least one execution has already occurred, this option is no longer available.
- Back to draft is available for live campaigns with execution errors only when the campaign is paused due to the error and no campaign executions have been completed yet.
- During publication, Save Audience activities execute before message activities.
- During publication, profile data is resolved against a snapshot taken at publication time, not the real-time profile, to ensure consistency across the entire execution.
- During publication, consent is honored directly from the profile record for matching profiles and is not re-evaluated at send time.
- During publication, profiles that do not match an existing record are created on the fly during execution.
- Delivery events are recorded in the
ajo_message_feedback_eventdataset, the primary source for delivery logs and post-send validation. - The Logs button, giving access to Logs and tasks, is available in both test and live mode in the canvas toolbar.
Applicability:
- Applies to: Orchestrated campaigns.
- Testing restriction (Save audience and channel activities not executed during test) applies to: Orchestrated campaign test mode in Draft status.
- Confirm sending (paused delivery pending explicit approval) applies to: non-recurring orchestrated campaigns.
Terminology:
- Canonical name: Orchestrated campaign — status values: Draft, Live, Completed (see also Scheduled, Stopped, Archived on the linked statuses page).
- Do not confuse: “Draft” (campaign being built and tested, not yet active) ≠ “Live” (published and executing) ≠ “Completed” (execution has finished).
- Do not confuse: “Stop” (stop execution at any time during test) ≠ “Restart” (reset and re-run the workflow in a single action) ≠ “Resume” (continue execution if previously paused).
- Do not confuse: “Preview schema” (view the work table schema for a transition) ≠ “Preview results” (see the transported data for a transition).
FAQ:
- Q: What happens when I test an Orchestrated campaign in Draft status? — All activities in the canvas are executed except Save audience activities and channel activities, with no functional impact on your data or audience.
- Q: Why does the workflow stop during a test? — In test mode, the workflow stops when it reaches a channel activity and does not continue to the activities that follow it; use Run test on the channel activity to simulate its execution without sending the message.
- Q: Why does nothing happen after I click Run test? — The button remains available even if the message content contains an error; check the Alerts / Warning icon in the canvas toolbar for a content-related error, fix it, and run the test again.
- Q: What must be true before I can publish a campaign? — All errors must be fixed; if the Publish button is disabled, you must check the error messages in the logs.
- Q: Are messages sent immediately after publishing a non-recurring campaign? — No, by default message delivery is paused until you explicitly confirm the send from the channel activity’s properties pane.
- Q: When can I use Back to draft? — For scheduled campaigns awaiting execution before the scheduled time is reached (unless recurring with at least one execution already completed), or for live campaigns paused due to an execution error with no completed executions yet.
- Q: Where are delivery events recorded? — In the
ajo_message_feedback_eventdataset, the primary source for delivery logs and post-send validation. - Q: Where can I set up alerts for my Orchestrated campaign? — From Administration > Alerts for system alerts, or by adding an Alert activity to the campaign canvas for custom alerts fired when execution reaches it.
Best practices:
- Before clicking Publish, confirm the campaign ran successfully in test mode with no errors in the logs, that message content has been previewed using Simulate Content, that the schedule is configured if applicable, and that you have reviewed the sending confirmation behavior.
Related pages:
- For all campaign statuses (including Scheduled, Stopped, Archived) and available actions at each stage: Understanding campaign statuses (campaigns/manage-campaigns.md)
- For testing signal-triggered campaigns: Learn how to test signal-triggered campaigns (orchestrated/trigger-orchestrated-campaign.md)
- For working with channel activities and simulating message content: Learn how to work with channel activities and simulate content (orchestrated/activities/channels.md)
- For configuring a campaign schedule: schedule is configured (orchestrated/create-orchestrated-campaign.md)
- For details on the Save audience activity: Save audience (orchestrated/activities/save-audience.md)
- For the Audience Portal where audience shells are created: Audience Portal (audience/about-audiences.md)
- For consent management during publication: Learn more about consent management (action/consent.md)
- For querying the delivery events dataset:
ajo_message_feedback_event(data/datasets-query-examples.md) - For Orchestrated campaigns reporting: Learn more on Orchestrated campaigns reporting (orchestrated/reporting-campaigns.md)
- For accessing and subscribing to system alerts: Access and subscribe to system alerts (reports/alerts.md)
- For configuring the Alert activity: Learn how to configure the Alert activity (orchestrated/activities/alert.md)
- For a list of error codes: Orchestrated campaign errors (orchestrated/orchestrated-campaign-errors.md)
- For disabling sending confirmation before publishing: Confirm message sending (orchestrated/activities/channels.md)
- For common questions from practitioners: Orchestrated campaigns FAQ (orchestrated/orchestrated-campaigns-faq.md)
- For duplicating a recurring campaign that can no longer be reverted to draft: duplicate the campaign (campaigns/manage-campaigns.md)
Personas:
- marketer: Can test an Orchestrated campaign in Draft status by selecting Start, then control the test using Stop, Start, Restart, or Resume. Can publish the campaign by selecting Publish to move it from Draft to Live status. Can monitor execution through the visual flow, activity status indicators, and the Logs and tasks screen. The page states that the Publish button is disabled until all errors are fixed. Where: “Publish the campaign”.
Onboarding:
- Level: Intermediate
- First minimal step: Open the campaign and select Start to test it in Draft status.
- Success check: Each activity in the campaign is executed sequentially until the end of the canvas is reached or until the workflow reaches a channel activity, where it stops so that you can run a test of that activity.
- Previous: Create and schedule the Orchestrated campaign before testing and publishing it: Create and schedule Orchestrated campaigns with Journey Optimizer (orchestrated/create-orchestrated-campaign.md)
- Next: Get insights on audience behavior and measure step performance after starting the campaign: Reporting for Orchestrated campaigns with Adobe Journey Optimizer (orchestrated/reporting-campaigns.md); Find answers to common questions about Orchestrated campaigns: Orchestrated campaigns Frequently Asked Questions (orchestrated/orchestrated-campaigns-faq.md)