在此页面上：了解如何配置警报流控制活动，以便在执行到达精心安排的营销活动中的特定点时通知订阅者。
警报活动是 流量控制 活动。 使用它可在营销活动执行到达画布上的活动时通知订阅者。
活动没有独立的触发器或条件配置。 它在流中的位置和上游编排逻辑决定了它的触发时间。 对于条件警报，请将其放在测试活动的相关分支上。
配置警报活动 alert-configuration
-
将 Alert 活动添加到您的编排的活动画布。
-
将其连接到要触发警报的过渡。
-
选择活动并配置以下字段：
- 标签：输入一个名称以标识画布上的活动。
- 标题（必需）：输入警报的简短纯文本标题。
- 消息（必需）：输入纯文本消息，说明订阅者需要了解的信息。
标题和消息是静态的。 不支持动态令牌。
有关在Journey Optimizer中订阅警报的信息，请参阅订阅警报。
示例：低群体警报 low-population-example
当查询返回少于10,000个配置文件时通知订阅者：
-
添加构建受众活动并使用规则生成器定义您的查询。
-
在其后添加 Test 活动，并定义一个条件来检查群体计数是否小于10,000。
-
将 警报 活动置于该条件的过渡上。
-
输入静态标题（如
Low audience population）和消息（如The query returned fewer than 10,000 profiles.）
当测试条件匹配且执行到达警报时，将触发警报活动。 10,000值是您在测试活动中配置的示例阈值，而不是产品限制。
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: The Alert flow control activity notifies subscribers when Orchestrated campaign execution reaches the activity.
Intents
- Configure a static alert title and message.
- Define a label to identify the activity on the canvas.
- Use a Test branch to notify subscribers when a query returns fewer than 10,000 profiles.
Glossary
- Alert (product-specific): A Flow control activity that notifies subscribers when campaign execution reaches it.
- Label: The name that identifies the activity on the canvas.
- Title: The required short, static plain-text title for the alert.
- Message: The required static plain-text message that describes what subscribers need to know.
- Test (product-specific): The activity that evaluates the population count condition in the low population example.
Guardrails
- The Alert activity has no independent trigger or condition configuration. Its position in the flow and upstream orchestration logic determine when it fires.
- Title and Message are required fields.
- The title and message are static. Dynamic tokens are not supported.
- The value of 10,000 in the low population example is a threshold configured in the Test activity, not a product limit.
Terminology
- Do not confuse: The Test activity evaluates a condition. The Alert activity fires when execution reaches it.
FAQ
- What triggers an Alert activity? Campaign execution reaching the activity triggers the alert. Upstream orchestration logic determines when it is reached.
- Can the title or message contain dynamic tokens? No. Both fields use static plain text, and dynamic tokens are not supported.
- How can an alert depend on an audience condition? Place it on the relevant Test branch. The Test activity evaluates the condition, not the Alert activity.