在此页面上：将优先级得分分配给历程、营销活动和入站操作，以便您能够在用户档案符合多个通信条件时控制哪个通信优先。
Journey Optimizer允许您为历程 操作 活动中的历程、营销活动或入站渠道操作分配优先级分数。
当存在强加的限制（如频率上限）时，优先级对于确定历程、营销活动或操作的优先级至关重要。
如果客户符合许多历程、营销策划或沟通的条件，而您希望选择他们应该输入和接收的内容，则应使用此字段。
为历程和营销活动分配优先级分数 priority-journey-campaign
➡️ 通过观看视频了解此功能
分配优先级得分对于入站通信（如Web、移动设备和应用程序内）至关重要。 如果您有多个使用相同渠道配置的营销活动（例如，网页顶部的横幅），则可能会出现问题，因为可以尽可能只显示来自一个营销活动的内容。 优先级分数是您插入首选项的位置，当收件人可能有资格参与多个营销活动时，应显示哪个营销活动。
要为历程或营销活动分配优先级得分，请在历程或营销活动属性中的 优先级得分 字段中输入一个数值（从0到100）。 数字越大，优先级越高。
如果您创作此营销活动，并且希望确保显示此营销活动内容，则可以为其指定100分。
为入站频道操作分配优先级分数 priority-action
Journey Optimizer还允许您在操作活动中为入站渠道操作分配优先级分数。
这样，当有多个历程操作或营销活动使用相同的渠道配置时，您就可以优先执行集客操作。
在 冲突管理 部分中，默认情况下选中 使用历程优先级 选项，这意味着操作的优先级分数继承自历程的整体优先级分数。
要为 操作 活动中定义的集客操作分配优先级得分，请取消选择 使用历程优先级 选项，然后在 优先级 字段中输入一个数值（从0到100）。 数字越大，优先级越高。
操作方法视频 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 to assign a priority score (0-100) to a journey, campaign, or inbound channel action so the most important communication takes precedence when a profile qualifies for more than one under a constraint such as a frequency cap.
Intents:
- Assign a priority score to a journey or campaign in its properties
- Assign a priority score to an inbound channel action in the Action activity
- Ensure a specific communication is shown by giving it the highest score
- Override the inherited journey priority for an action by unselecting Use journey priority
Glossary:
- Priority score: A numeric value from 0-100 assigned to a journey, campaign, or action; the higher the number, the higher the priority (product-specific)
- Use journey priority: Option, selected by default, that inherits the action’s priority from the overall journey priority score (product-specific)
- Conflict management: Section of the Action activity where the action priority is set (product-specific)
- Inbound channel action: A web, in-app, or code-based action within the Action activity that can take a priority score (product-specific)
Guardrails:
- Enter a numeric value from 0-100 in the Priority score field; the higher the number, the higher the priority.
- In campaigns, priority score is available for the web, in-app, and code-based inbound channels only.
- In the Action activity, priority score is available for the web, in-app, and code-based inbound channels only.
- If two journeys or campaigns have the same priority score, the system does not have a tie-breaking mechanism; ensure priority scores are unique to avoid conflicts.
- In the Action activity, Use journey priority is selected by default, so the action inherits the journey’s priority score until you unselect it.
Terminology:
- Canonical name: priority score — Acronym: n/a — variants: priority, Priority score
- Synonyms: none
- Do not confuse: “priority score” (a static 0-100 value setting precedence) ≠ “ranking formula” (a dynamic expression that ranks journeys)
- Do not confuse: journey or campaign “Priority score” ≠ action “Priority” (which by default inherits the journey score via Use journey priority)
FAQ:
- Q: What range can a priority score take? — A numeric value from 0-100, where the higher the number, the higher the priority.
- Q: How do I make sure a specific campaign is shown? — Give it a score of 100.
- Q: What happens if two items share the same priority score? — The system has no tie-breaking mechanism, so ensure priority scores are unique.
- Q: On which channels is priority score available? — The web, in-app, and code-based inbound channels only.
- Q: How does an action get its priority? — By default it inherits the journey priority via Use journey priority; unselect that option to set a separate value from 0-100.