在此頁面上：瞭解如何測試、發佈和監視Adobe Journey Optimizer中的協調行銷活動，包括行銷活動生命週期、執行記錄檔和活動狀態指標。
一旦您建立了協調的行銷活動並設計了要在畫布中執行的任務，您就可以發佈它並監視其執行方式。 您也可以在測試模式下執行行銷活動，以檢查其執行和不同活動的結果。
行銷活動生命週期總覽 lifecycle
協調的行銷活動會經過一組已定義的狀態。 發佈工作流程的關鍵階段包括：
發佈前測試您的行銷活動 test
Journey Optimizer可讓您在開始使用前測試協調的行銷活動。 建立行銷活動時，預設會進入 草稿 狀態。 在此狀態下，您可以手動執行行銷活動以測試流量。
若要測試協調的行銷活動，請開啟行銷活動並選取開始。 行銷活動中的每個活動都會依序執行，直到達到畫布結尾為止。
行銷活動畫布工具列中的
針對觸發的協調行銷活動，系統會等待API呼叫啟動行銷活動。 您必須傳送訊號才能繼續測試。 瞭解如何測試訊號觸發的行銷活動。
在測試期間，您可以使用畫布中的動作列來控制行銷活動的執行。 從那裡，您可以：
- 隨時 停止 執行。
- 再次 開始 執行。
- 重新啟動執行以重設工作流程，並在單一動作中重新執行。 如果您想要在修改後快速重新測試行銷活動流程，這會特別有用。
- 如果先前已暫停執行，則繼續執行。
畫布工具列中的警示 / 警告圖示會通知您發生的問題，包括執行之前可能主動出現的警告，以及在執行期間或執行之後發生的錯誤。
行銷活動畫布工具列中的
您也可以使用直接顯示在每個活動上的視覺狀態指標，快速識別失敗的活動。 如需詳細的疑難排解，請開啟行銷活動的記錄，其中提供有關錯誤及其內容的深入資訊。
如果您已在畫布中新增頻道活動，則可預覽和測試訊息內容。 瞭解如何使用頻道活動並模擬內容。
發佈此行銷活動 publish
在您的行銷活動經過測試且準備就緒後，按一下「發佈」，讓行銷活動上線。
行銷活動畫布中的
視覺流量會重新啟動，而真實設定檔會開始即時流過歷程。
如果發佈動作失敗（例如，由於缺少訊息內容），您會收到警報，必須在重試之前修正問題。 成功發佈後，行銷活動就會開始執行（立即或依排程）、從 草稿 移至 即時 狀態，並變成「唯讀」。
發佈時間執行順序 publication-sequence
當您按一下 發佈 時，會在內部發生下列順序：
- 排程器啟動 — 如果行銷活動已設定排程，排程器會在定義的時間啟動並觸發執行。
- 儲存對象活動會先執行 — 工作流程中的任何儲存對象活動都會在訊息活動之前執行。 對象殼層是在對象入口網站中建立的，且合格的設定檔會開始擷取。
- 訊息執行開始 — 通道活動開始處理工作流程中的第一個訊息活動。
- 設定檔快照集查詢 — 設定檔資料會針對在發行集時拍攝的快照集進行解析，而非即時設定檔。 這可確保整個執行的一致性。
- 同意評估 — 對於相符的設定檔，會直接從設定檔記錄接受同意。 傳送時不會重新評估同意。 進一步瞭解同意管理
- 即時設定檔建立 — 在執行期間會即時建立與現有記錄不符的設定檔。
- 傳遞記錄建立 — 傳遞事件記錄在
ajo_message_feedback_event資料集中，這是傳遞記錄和傳送後驗證的主要來源。
若要在執行後驗證結果，請使用Journey Optimizer報告功能。 進一步瞭解協調的行銷活動報告
將行銷活動恢復為草稿 back-to-draft
返回草稿功能可讓您取消發佈，並在特定情況下將協調的行銷活動還原為草稿狀態。 這是為了當作復原機制而設計，可在傳送任何訊息之前修正問題，同時維持促銷活動生命週期的完整性。
此選項適用於兩種情況：
-
排程行銷活動等待執行：當行銷活動排程在特定時間執行且尚未到達該時間時，您可以使用回到草稿來檢閱和修改行銷活動，然後再開始執行。 但是，如果行銷活動為週期性行銷活動（例如每日排程的行銷活動），且已發生至少一次執行，則此選項不再可用。 在這種情況下，您應該改為複製行銷活動。
-
發生執行錯誤的即時行銷活動：當行銷活動在執行期間遇到錯誤且已暫停，而且尚未完成任何行銷活動執行時，您可以使用回到草稿來修正錯誤並重新發佈行銷活動。
若要將行銷活動切換回草稿狀態，請開啟協調的行銷活動，然後按一下行銷活動畫布工具列中的 返回草稿 按鈕。
行銷活動會取消發佈，而工作流程會停止。 行銷活動會傳回 草稿 狀態。 您現在可以修正已識別的問題，然後測試行銷活動並在準備就緒時再次發佈。
確認訊息傳送 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.
- 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.
- 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: 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.
- 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)