在此页面上：了解如何使用 停止操作 活动从选定的入站活动中删除用户档案，而不结束历程。
使用 停止操作 活动从一个或多个选定的上游入站活动（最多五个）中删除配置文件：应用程序内体验、内容卡片体验、Web体验或基于代码的体验。 当用户档案达到此步骤时，它将停止符合所选体验的资格并继续完成历程。 其他入站活动不受影响。
与停止历程不同，停止历程会停止所有通过历程的用户档案，停止操作仅适用于到达此步骤的用户档案的选定入站活动。
活动的放置位置 placement
停止操作活动必须位于其定向的集客活动的下游，且位于同一历程路径上。 其他活动，如 等待 或反应，可以置于入站活动和 停止操作 之间。
当选择放置位置时：
- 应避免将其放在集客活动之后立即，因为这样可能会阻止用户档案看到集客体验。
- 将其放置在 End 之前是多余的，因为当配置文件退出历程时，集客活动已被删除。
护栏 guardrails
配置 停止操作 活动时，将检查所选集客活动和活动的位置。 某些情况会生成错误，而其他情况则会生成警告。
以下配置生成错误：
- 无集客活动，或集客活动超过5个。
- 多次执行同一集客活动。
- 入站活动，它不是同一历程路径上 停止操作 的上游。
- 已删除的集客活动。 它显示为不可用的活动。
以下配置会生成警告：
- 历程中较早时已停止的入站活动。
- 集客活动在激活后立即停止，这可能会阻止用户档案看到体验。
- 停止操作放在紧靠前面 结束 的位置，这是不必要的，因为当配置文件退出历程时，集客活动已被删除。
配置活动 configure
您的 停止操作 活动现已配置完成。 当用户档案达到此步骤时，将从选定的集客体验中删除该用户档案，并继续在历程中前进。
如果配置文件重新进入历程，则体验会在配置文件到达时再次激活。
用例 use-cases
-
注册后停止应用内提醒。 您的历程显示应用程序内体验，鼓励用户档案注册活动。 历程检测到配置文件已注册后，使用 停止操作 从上游应用程序内活动中删除该配置文件。 用户档案不再符合注册提醒的条件，而是继续完成其余的历程步骤，如接收事件准备电子邮件。
-
转换后停止购买促销活动。 您的旅程可为用户档案提供促销Web体验或基于代码的体验。 历程检测到购买后，使用 停止操作 从上游促销活动中删除用户档案，以便他们不再符合这些体验的条件。 配置文件可以在同一历程中继续完成购买后步骤，而 停止操作 中未选定的任何入站活动仍不受影响。
-
替换基于代码的体验。 激活基于代码的体验A，添加 等待 活动，然后使用 停止操作 在激活基于代码的体验B之前停止体验A。当个人资料继续遍历历程时，此序列替换第一个体验。
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.