在此頁面上：瞭解如何設定警示流程控制活動，在執行到達協調行銷活動中的特定點時通知訂閱者。
警示活動是 流量控制 活動。 當行銷活動執行達到畫布上的活動時，使用它來通知訂閱者。
活動沒有獨立的觸發程式或條件設定。 其在流程中的位置和上游協調流程邏輯會決定其引發時間。 對於條件式警示，請將其放在測試活動的相關分支上。
設定警示活動 alert-configuration
-
新增 警示 活動至您的協調行銷活動畫布。
-
將其連線到您希望觸發警報的轉變。
-
選取活動並設定下列欄位：
- 標籤：輸入名稱以識別畫布上的活動。
- 標題 （必要）：輸入警示的簡短純文字標題。
- 訊息 （必要）：輸入純文字訊息，說明訂閱者需要知道的內容。
標題和訊息為靜態。 不支援動態權杖。
如需在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.