The System Notifications page allows you to automatically alert key team members about important system-level events. By subscribing one or more email addresses to specific events, you can stay informed about critical processes such as data updates, batch process completions, and campaign execution summaries without having to log in to check their status.
Prerequisites
- You must have an Admin role to view and manage System Notifications.
Navigating to System Notifications
- Click the Settings icon in the main navigation menu.
- Under the General Settings category, select System Notifications.
A Guide to the System Notifications Screen
The main page displays a list of all currently configured notifications, showing which Event triggers an email and which Contact Email(s) will receive it.
How to Add a New System Notification
- From the main page, click the blue + Add System Notification button.
-
The "New System Notification" screen will appear.
-
Click the Select Event dropdown to choose which system event will trigger the notification.
- In the Email Recipients text box, enter the email address of the person you want to notify. To add multiple recipients, you can press Enter or add a comma after each address.
- Click Save. The notification is now active.
How to Edit or Delete a System Notification
- From the main list, click the pencil icon (
✎) on the right-hand side of the notification you wish to modify. -
The "Edit System Notification" screen will appear.
- From here you can:
- Change the triggering Event using the dropdown.
- Add or remove email addresses in the Email Recipients box.
- To permanently remove the notification, click the Delete System Notification link in the top-right corner and confirm the action.
- Click Save to apply your changes.
Understanding Email Notifications
Each system notification is delivered by email to the recipients you subscribe to on this page. Notifications fall into two groups: event-based alerts, sent when a specific system event occurs (such as a data update or batch process completing), and scheduled summaries, sent automatically at a set time in your tenant's time zone. The section below covers one of the scheduled summaries.
Triggered Conditional Execution Daily Summary
The Triggered Conditional Execution Daily Summary is a scheduled email notification sent once a day, at 00:15 in your tenant's time zone. It summarizes everything that happened during the previous day for customers who met the trigger of triggered campaigns that are marked for conditional execution.
The summary is designed to help your team confirm that conditional execution is working as intended. Use it to:
- Check your timeout configuration — if a large share of customers appear under "Allowed after timeout," approval responses may be arriving too late, and you might consider extending the request timeout
- Verify your approval mechanism — if no customers were approved ("Allowed"), your approval integration may have an issue worth investigating
What the Summary Includes
Each email opens with the site name and the date it covers, followed by two configuration lines and a set of totals for the day. The totals count how many customers reached each stage of the conditional execution flow.
| Line | What it means |
|---|---|
| Active Triggered Campaigns with conditional execution | The number of conditional execution triggered campaigns that were active that day |
| Request timeout defined for this tenant | The response timeout, in seconds, configured for your tenant |
| Server unavailable | The number of customers Optimove tried to send the request for but could not reach the client's server |
| Requested | The number of customers Optimove sent the request for |
| Allowed | The number of customers Optimove received approval for |
| Denied | The number of customers Optimove received a denial for |
| Expired | The number of customers for which no response was received before the timeout |
| Allowed after timeout | A subset of Expired — customers for which an approval response arrived after the timeout |
| Denied after timeout | A subset of Expired — customers for which a denial response arrived after the timeout |
Example
A typical summary looks like this:
Summary of today's triggered campaigns with conditional execution for Optimove site [sitename].optimove.net for November 16, 2025.
- Active Triggered Campaigns with conditional execution: 34 campaigns
- Request timeout defined for this tenant: 10 seconds
Totals:
- Server unavailable: 0
- Requested: 5,331
- Allowed: 4,858
- Denied: 0
- Expired: 485
- Allowed after timeout: 51
- Denied after timeout: 0
For more on setting up and configuring conditional execution for triggered campaigns, see Using Conditional Campaign Execution.