在此頁面上：瞭解如何使用 停止動作 活動，從選取的傳入活動中移除設定檔，而不結束歷程。
使用 停止動作 活動，從一或多個選取的上游傳入活動（最多五個）中移除設定檔：應用程式內、內容卡、網頁或程式碼型體驗。 當設定檔達到此步驟時，它會停止符合所選體驗的資格，並繼續進行歷程中的進度。 其他傳入活動則不受影響。
不同於停止歷程會停止所有通過歷程的設定檔，停止動作只適用於到達此步驟的設定檔之選取的傳入活動。
活動的放置位置 placement
停止動作活動必須位於其目標之入站活動的下游，且位於相同歷程路徑上。 其他活動，例如 等待 或回應，可置於傳入活動與 停止動作 之間。
選擇放置位置時：
- 請避免在傳入活動後立即放置它，因為這樣可防止設定檔看到傳入體驗。
- 將它置於 End 之前是多餘的，因為當設定檔離開歷程時，會移除傳入活動。
護欄 guardrails
當您設定 停止動作 活動時，將會檢查選取的傳入活動和活動的位置。 有些條件會產生錯誤，有些則會產生警告。
以下設定會產生錯誤：
- 無入站活動，或超過五個入站活動。
- 相同傳入活動多次。
- 入站活動不是相同歷程路徑上 停止動作 的上游。
- 已刪除的傳入活動。 它會顯示為無法使用的活動。
以下設定會產生警告：
- 已在歷程中先前停止的傳入活動。
- 入站活動在啟動後立即停止，這會使設定檔無法看到體驗。
- 停止動作放在緊接在 End 之前，這是不必要的，因為設定檔離開歷程時，已移除傳入活動。
設定活動 configure
您的 停止動作 活動現已設定完成。 當設定檔達到此步驟時，它會從選取的傳入體驗中移除，並繼續在歷程中前進。
如果設定檔重新進入歷程，則體驗會在設定檔到達時再次啟用。
使用案例 use-cases
-
註冊後停止應用程式內提醒。 您的歷程會顯示應用程式內體驗，鼓勵設定檔註冊活動。 歷程偵測到設定檔已註冊後，請使用 停止動作 將該設定檔從上游應用程式內活動移除。 設定檔不再符合註冊提醒的條件，但會繼續完成其餘的歷程步驟，例如接收事件準備電子郵件。
-
轉換後停止購買促銷活動。 您的歷程讓設定檔可使用促銷網站或程式碼型體驗。 歷程偵測到購買後，使用 停止動作 從上游促銷活動中移除設定檔，讓他們不再符合這些體驗的資格。 設定檔可在相同歷程中繼續完成購買後的步驟，而任何未在 停止動作 中選取的傳入活動仍不受影響。
-
取代程式碼型體驗。 啟用程式碼型體驗A，新增 等待 活動，然後使用 停止動作 來停止體驗A，然後再啟用程式碼型體驗B。當設定檔透過歷程繼續時，此序列會取代第一個體驗。
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: Stop action removes a profile from selected upstream inbound experiences without ending the profile’s journey.
Intents:
- Remove a profile from selected inbound experiences while continuing the journey
- Configure Stop action downstream of inbound activities on the same path
- Distinguish Stop action from stopping a journey
- Replace a code-based experience while continuing the journey
- Resolve selection errors and avoid redundant Stop action activities
Glossary:
- Stop action: A journey activity that removes the profile reaching it from selected upstream inbound activities while the profile continues progressing in the journey. (product-specific)
- Inbound activities: The in-app, content card, web, or code-based experience activities that Stop action can target. (product-specific)
Guardrails:
- Stop action must be downstream of the selected inbound activities on the same journey path. Wait or Reaction can be placed between the inbound activity and Stop action.
- Select one to five upstream inbound activities (hard limit). Selecting none, more than five, or the same activity more than once generates an error.
- Selecting an activity that is not upstream on the same path or has been deleted generates an error. Deleted selections appear as Unavailable activity.
- Warnings identify an activity already stopped earlier, an activity stopped immediately after activation, or a redundant Stop action immediately before End.
- Avoid stopping an inbound activity immediately after activation, as this can prevent the profile from seeing the experience.
- Inbound activities are already removed when a profile exits the journey. Stop action immediately before End is redundant.
- Give inbound activities distinct labels because the Action dropdown shows only activity names, which can be identical.
- Other inbound activities are not affected.
Terminology:
- Canonical activity name: Stop action
- Target selection field: Action
- Additional target control: Stop another action
- Deleted selection label: Unavailable activity
- Do not confuse Stop action with stopping a journey: Stop action applies to selected inbound activities for the profile reaching it; stopping a journey halts all profiles progressing through it.
FAQ:
- Q: Does Stop action end the profile’s journey? The profile stops qualifying for the selected experiences and continues progressing in the journey.
- Q: Which inbound activities can Stop action target? In-app, content card, web, or code-based experience activities upstream of Stop action.
- Q: How many inbound activities can be selected? Up to five (hard limit).
- Q: Are other inbound activities affected? Other inbound activities are not affected.
- Q: Must Stop action immediately follow an inbound activity? Wait or Reaction can be placed between the inbound activity and Stop action on the same path. Avoid stopping an inbound activity immediately after activation, as this can prevent the profile from seeing the experience.
- Q: What happens when a profile re-enters the journey? The inbound experience activates again when the profile reaches that activity.