在此页面上：在历程和营销活动上线前发现重叠之处，这样您就可以避免一次用过多的通信轰炸客户。
随着营销人员在Journey Optimizer中增加促销活动和历程的数量，营销人员越来越难以了解他们是否通过过多的营销交互来轰击其客户。 因此，当存在重叠的营销活动和历程时，轻松进行识别至关重要，以确保它们在营销沟通方面达到适当的平衡，同时降低客户疲劳的风险。
要监控潜在重叠的关键领域包括：
- 时间轴（开始和结束日期）：同时运行的历程是否太多？
- 受众：我的历程受众中还有多少百分比是其他历程的一部分？
- 渠道：是否计划在同一个时间范围内进行其他通信？如果是，有多少通信？
- 上限规则集：我将对哪些类型的历程设置上限，并且这些历程中存在重叠？
- 渠道配置：是否有其他历程或营销活动正在使用同一历程或营销活动中使用的任何渠道配置可能会阻止向最终用户显示历程或营销活动？
➡️ 通过观看视频了解此功能
Journey Optimizer如何检测冲突 detection
以下是Journey Optimizer如何识别历程和营销活动潜在冲突的摘要：
- 冲突标识范围：仅对实时或计划的营销活动和历程显示冲突。
- 单一历程：如果所选历程为单一历程，将显示以同一事件开始的其他历程，因为此事件将触发所有此类历程。
- 受众资格和读取受众/商业事件历程：如果所选历程是受众资格或读取受众/商业事件历程，则将显示具有有效受众的相同类型的所有其他历程，因为受众之间可能存在重叠。
- 营销活动：由于所有营销活动均以受众为目标，并且没有事件的概念，因此所有营销活动都可能与区段触发的历程（从读取受众活动开始）冲突。
- 实时/计划的营销活动：实时和计划的营销活动可能由于潜在的受众重叠而相互冲突。 对于任何给定的营销活动，所有实时或计划的营销活动都会在冲突查看器中列出。
查看给定历程或营销活动中的已识别冲突 view
在创作历程或营销策划时，Journey Optimizer允许您检查何时可能与其他历程或营销策划重叠。 为此，请执行以下步骤：
-
在创作历程或营销策划时，单击历程或营销策划属性中的 查看潜在冲突 按钮。
note NOTE 一旦分配了以下任何设置，查看潜在冲突按钮即可供您选择：开始/结束日期、受众、渠道、渠道配置和规则集。 确保在分配这些设置后选择保存，因为保存更改之前，按钮不可选。 -
将打开 潜在冲突 窗口，允许您可视化与当前历程/营销活动重叠的所有元素。
您可以通过选择重叠历程或营销策划的名称，直接从屏幕中打开它。
note NOTE 由于实施了缓存，新发布的历程和营销活动可能需要3-7分钟才能显示在冲突查看者中。
为进一步优化潜在重叠的搜索，您可以根据相关的字段筛选营销活动和历程列表。 为此，请在库存视图中选择过滤器图标。 了解如何使用筛选器
解决冲突 resolve
以下是识别潜在冲突后减少这些冲突的一些提示：
- 调整 开始/结束日期 以避免营销活动或历程重叠。
- 优化 受众定位 以最大限度地减少历程之间的重叠。
- 实施 频率限制 以防止客户接收过多的通信。
- 减少 活动历程 的数量，以更有效地管理客户体验。
- 设置入站操作的 优先级 以确保向客户显示最重要的操作。
利用这些功能，您可以确保营销工作保持一致，并在沟通策略中保持适当的平衡。
操作方法视频 video
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 Journey Optimizer detects potential conflicts between overlapping live or scheduled journeys and campaigns, how to view them, and how to resolve them.
Intents:
- Identify overlapping journeys and campaigns before they go live
- Open the Potential conflicts window with the View Potential Conflicts button
- Monitor overlap across timeline, audience, channel, capping rule set, and channel configuration
- Filter the conflict list to refine the search for overlaps
- Apply resolution tactics such as adjusting dates, refining audiences, adding frequency caps, reducing active journeys, or setting priorities
Glossary:
- Conflict detection tool: Tool that identifies potential overlaps in journeys and campaigns, such as timelines, audience overlap, and channel configurations (product-specific)
- View Potential Conflicts: Button in the journey or campaign properties that opens the potential conflicts window (product-specific)
- Unitary journey: A journey type for which other journeys that start with the same event are displayed as potential conflicts (product-specific)
- Capping Rule Set: An overlap area that identifies which journey types are capped and whether there is overlap within those (product-specific)
- Channel Configuration: An overlap area that identifies other journeys or campaigns using the same channel configuration (product-specific)
Guardrails:
- Conflicts are shown only for live or scheduled campaigns and journeys.
- The View Potential Conflicts button becomes available only after you assign at least one of Start / end date, Audience, Channel, Channel configuration, or Rule set, and it stays unselectable until changes are saved.
- Newly published journeys and campaigns may take up to 3-7 minutes to appear in the conflict viewer, due to caching.
- For a unitary journey, other journeys that start with the same event are displayed, as that event triggers all such journeys.
- For an Audience qualification or a Read Audience/Business Event journey, all other journeys of the same type with a valid audience are displayed.
- All campaigns potentially conflict with segment-triggered journeys (those starting with a Read audience activity), and live or scheduled campaigns may conflict with one another due to audience overlap.
Terminology:
- Canonical name: conflict detection — Acronym: n/a — variants: conflict detection tool, potential conflicts, View Potential Conflicts
- Synonyms: none
- Do not confuse: “conflict detection” (spots overlapping journeys and campaigns) ≠ “priority scores” (decides which communication takes precedence) ≠ “rule sets” (limit how often and how many messages are sent)
FAQ:
- Q: Which journeys and campaigns appear in the conflict viewer? — Only live or scheduled journeys and campaigns.
- Q: Why is the View Potential Conflicts button unavailable? — It becomes available only after you assign at least one of start/end date, audience, channel, channel configuration, or rule set, and after you save.
- Q: Why does a newly published item not show as a conflict yet? — Newly published journeys and campaigns can take up to 3-7 minutes to appear, due to caching.
- Q: How can I reduce identified conflicts? — Adjust start/end dates, refine audience targeting, implement frequency caps, reduce the number of active journeys, or set priorities on inbound actions.
- Q: Do campaigns conflict with journeys? — Campaigns can conflict with segment-triggered journeys that start with a Read audience activity, and live or scheduled campaigns can conflict with one another due to audience overlap.