On this page: Learn how to configure the Alert flow control activity to notify subscribers when execution reaches a specific point in an Orchestrated campaign.
The Alert activity is a Flow control activity. Use it to notify subscribers when campaign execution reaches the activity on the canvas.
The activity has no independent trigger or condition configuration. Its position in the flow and the upstream orchestration logic determine when it fires. For conditional alerts, place it on the relevant branch of a Test activity.
Configure the Alert activity alert-configuration
-
Add an Alert activity to your Orchestrated campaign canvas.
-
Connect it to the transition where you want an alert to fire.
-
Select the activity and configure the following fields:
- Label: Enter a name to identify the activity on the canvas.
- Title (required): Enter a short, plain-text title for the alert.
- Message (required): Enter a plain-text message that describes what subscribers need to know.
The title and message are static. Dynamic tokens are not supported.
For information on subscribing to alerts in Journey Optimizer, see Subscribe to alerts.
Example: Low population alert low-population-example
Notify subscribers when a query returns fewer than 10,000 profiles:
-
Add a Build audience activity and use the rule builder to define your query.
-
Add a Test activity after it and define a condition that checks whether the population count is less than 10,000.
-
Place an Alert activity on the transition for that condition.
-
Enter a static title, such as
Low audience population, and a message, such asThe query returned fewer than 10,000 profiles.
The Alert activity fires when the Test condition matches and execution reaches the alert. The value of 10,000 is an example threshold that you configure in the Test activity, not a product limit.
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.