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, 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.
Available Notification Types
The table below summarizes every notification available in the Select Event dropdown and which feature or integration it relates to. Detailed descriptions follow in the sections below.
Notification
Category
Who should subscribe
Batch Process Started
Batch & data
Operations teams monitoring pipeline timing
Batch Process – Data Update Completed
Batch & data
Teams who need to know when fresh data is loaded
Batch Process Completed
Batch & data
Anyone who needs end-of-day confirmation the pipeline ran cleanly
Batch Data Freshness for Today Completed
Batch & data
Teams using Campaign Execution 2.0 who need to know campaigns can run
Campaign Execution Daily Summary
Campaign execution
Campaign managers wanting a daily campaign health digest
Triggered Conditional Execution Status
Conditional execution
Teams using conditional execution on triggered campaigns
Low Conditional Approval Rate
Conditional execution
Teams using conditional execution who want approval rate alerts
Conditional Approval was missed
Conditional execution
Teams using conditional execution who want to catch integration failures
Data Ingestion Process – [process name] Failed
Data Ingestion
Data teams managing self-serve ingestion processes
Data Ingestion Process – [process name] Partially Failed
Data Ingestion
Data teams managing self-serve ingestion processes
Zero Copy List [list name] Failure
Zero Copy Lists
Teams using Zero Copy Lists from Snowflake or Databricks
OptiPromo – Insufficient Codes Alert
Promotions
Teams managing promo code promotions
OptiPromo – Audience Cap Threshold Reached
Promotions
Teams managing promotions with audience caps
OptiPromo – Budget Threshold Reached
Promotions
Teams managing promotions with budget limits
Shopify – Customer Data Request
Shopify
Anyone responsible for GDPR data requests
Shopify – Customer Redact Request
Shopify
Anyone responsible for GDPR data deletion requests
Shopify – Shop Redact Request
Shopify
Anyone responsible for merchant offboarding
Identified issues with event listeners
Platform health
Technical teams who manage webhook integrations
Note: Some notifications only appear in the dropdown if the related feature or integration is enabled for your site.
Click a notification in the sections below to expand its details.
Batch & Data Process Notifications
These notifications track Optimove's daily batch pipeline: the process that imports your customer data, updates the customer model, and prepares campaigns to run. They are available to all Optimove sites.
Batch Process Started
Sent at the beginning of the daily batch process, when Optimove starts importing new customer data and updating the customer model.
What the email tells you: The batch process has begun for your site and date. At this stage Optimove is preparing data; campaigns have not yet run.
Who should subscribe: Operations or data teams who need visibility into when the daily pipeline starts, for example to detect unexpected delays early.
Batch Process – Data Update Completed
Sent when the data import phase of the daily process completes successfully. This is a mid-pipeline milestone: campaign execution begins after this point, but your data is not yet considered fresh (see Batch Data Freshness for Today Completed for that signal).
What the email tells you: New customer data has been loaded into Optimove. The pipeline is now moving to the next phase.
Who should subscribe: Teams who want to know the earliest moment new customer data is available, or who need to confirm the data load ran before campaign execution begins.
Batch Process Completed
Sent when the entire daily process (data import, campaign execution, and analysis) has finished successfully.
What the email tells you: Mission Control and all Optimove reports are now up to date for the day.
Who should subscribe: This is the most commonly subscribed batch notification. It is the end-of-day confirmation that everything ran cleanly and reports are ready to view.
Batch Data Freshness for Today Completed
This notification lets you know that today's batch data is fresh and ready for your campaigns. It is sent once a day when the batch data update completes, and Optimove starts treating your batch data as fresh. From this point, your regular scheduled campaigns (those not marked Run Anyway) can run with today's batch data, according to their schedule.
If your batch data update was late, regular campaigns that are still within their allowed delay window will run now. Campaigns whose allowed delay has already passed move to Not Run.
The batch data refresh for Optimove site [site name] for [date] has completed successfully. The latest batch data is now available in Optimove. Any pre-scheduled campaign that relies on batch data will now be calculated and executed using the refreshed data for [date], according to its configured schedule and settings.
Visit Mission Control to monitor campaign execution.
The date is shown in your site's time zone. The email also includes a Visit Your Optimove Site link.
Which batch notification should I use?
Notification
What it tells you
Batch Process – Data Update Completed
Your batch data has been received and loaded. At this point it is not yet fresh, so regular campaigns cannot run with it.
Batch Data Freshness for Today Completed
Your batch data is fresh, so your regular scheduled campaigns can run with it.
Batch Process Completed
The entire pipeline (data, campaigns, and analysis) is fully done for the day.
Protip: If you want to know when your campaigns can start running with today's batch data, subscribe to Batch Data Freshness for Today Completed.
Campaign Execution Notifications
Campaign Execution Daily Summary
Sent once at the end of each day, after all campaign execution has finished. It provides a full picture of how today's campaigns performed across your site.
What the email tells you:
Number of campaigns executed successfully
Number of campaigns that failed or partially failed
Number of campaigns not executed because the Target Group was empty
A direct link to Mission Control to view campaign-level detail
Who should subscribe: Campaign managers or operations leads who want a single daily confirmation of campaign delivery health. If the failed count is above zero, the team can investigate in Mission Control before the next day's run.
Conditional Execution Notifications
These notifications relate to conditional execution, a Campaign Execution 2.0 feature where an external system approves or denies customers before a campaign runs. If your site does not use conditional execution, these notifications will not be relevant to you.
Triggered Conditional Execution Status
The Triggered Conditional Execution Status is a scheduled email sent once a day, at 00:15 in your site'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.
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 site
Server unavailable
The number of customers Optimove tried to send a request for but could not reach your server
Requested
The number of customers Optimove sent the approval 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
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
Low Conditional Approval Rate
Sent when the proportion of approved customers for a conditional campaign falls below 50% of the total eligible customers after the approval window closes.
For example, if 1,000 customers were eligible for a campaign but only 380 were approved by your external system before the deadline, the 38% approval rate triggers this alert.
What the email tells you:
Which campaign triggered the alert
The occurrence date and approval deadline
Total eligible customers, number approved, and the calculated approval rate
Who should subscribe: Teams responsible for the conditional execution integration. A low approval rate may indicate a delay in your external approval system, a configuration issue, or genuine business-driven denials worth reviewing.
Conditional Approval was missed
Sent when the conditional approval window closes and your external system sent zero approvals for a campaign, meaning no customers were approved before the deadline at all.
This is a more severe signal than Low Conditional Approval Rate. A missed approval typically indicates that the approval request was not received, the external system was unavailable, or an integration problem prevented any response from being sent.
What the email tells you:
Which campaign and occurrence was affected
The deadline that passed without any response
Who should subscribe: Technical teams and campaign managers who need to be alerted immediately when an approval integration fails completely, so they can investigate and act before the next run.
These notifications are sent when a Data Ingestion process (a self-serve upload of customer data) encounters a problem. The notification is sent to the email addresses you subscribe to this event in System Notifications, and the process name is shown in the email subject so you can identify which upload was affected.
Data Ingestion Process – [process name] Failed
Sent when a Data Ingestion process cannot complete. The process name in the notification is replaced with the actual name of the affected process.
Common causes include:
The source file was not found at the expected location
Optimove could not connect to the data source
Access to the data source was denied
The file could not be parsed due to an unexpected format
An unexpected platform error stopped the process
New attributes could not be created (for example, because the attribute limit has been reached)
Who should subscribe: Data or operations teams responsible for managing Data Ingestion processes. A failed process means no data was ingested for that run and action is required.
Data Ingestion Process – [process name] Partially Failed
Sent when a Data Ingestion process completes but some records could not be ingested. The email includes the list of customer IDs that failed, so you can identify and re-submit or investigate the affected rows.
Who should subscribe: Data teams who need visibility into partial upload failures, particularly where data completeness is important for downstream campaigns or segmentation.
Sent when a Zero Copy List sync fails. Zero Copy Lists allow Optimove to read customer lists directly from your data warehouse (such as Snowflake or Databricks) and use them as Target Groups in campaigns. The list name in the notification is replaced with the name of the list that failed to sync.
What the email tells you:
The name of the list that failed
The data connection that was being used
The Target Group(s) associated with that list
Who should subscribe: Data and campaign teams who rely on Zero Copy Lists. A sync failure means the Target Group may contain stale data, which could affect any campaigns using it. Optimove automatically clears the list content when a sync fails to prevent stale data from being used.
Note: This notification only fires on a failure. It does not fire if the sync ran successfully but returned zero results.
Promotions Notifications
These notifications alert you to thresholds being reached in your Promotions (formerly OptiPromo). Each alert is configured per promotion and fires once the defined threshold is crossed.
OptiPromo – Insufficient Codes Alert
Sent when the supply of unique promo codes available for a running promotion drops below the alert threshold set when the promotion was configured.
Who should subscribe: Teams managing promo code promotions. This alert gives you time to upload additional codes before the pool runs out and customers can no longer be issued a code.
OptiPromo – Audience Cap Threshold Reached
Sent when the number of customers who have received a promotion reaches the configured audience cap alert threshold. For example, if a promotion has an audience cap of 10,000 and the alert is set at 80%, this notification fires when 8,000 customers have received the promotion.
Who should subscribe: Teams managing promotions with audience limits, to plan whether the cap needs to be increased or the promotion wound down.
OptiPromo – Budget Threshold Reached
Sent when the total value of discounts issued by a promotion reaches the configured budget alert threshold. For example, if a promotion has a £50,000 budget and the alert is set at 80%, this notification fires when £40,000 has been issued.
Who should subscribe: Finance and marketing teams monitoring promotional spend, to ensure the budget is not exceeded without a conscious decision.
Shopify Notifications
These three notifications are sent in response to GDPR-related data requests that Shopify forwards to Optimove when you have the Optimove Shopify app installed. Shopify requires all apps to handle these mandatory webhook events; subscribing ensures your team is informed and can take appropriate action.
Shopify – Customer Data Request
Sent when a customer submits a data access request through Shopify, asking to see what data is held about them.
Who should subscribe: Whoever in your organization handles GDPR or data subject access requests. On receiving this notification, the relevant team should retrieve and provide the customer's Optimove data as required by applicable data protection law.
Shopify – Customer Redact Request
Sent when a customer requests deletion of their personal data through Shopify.
Who should subscribe: Whoever handles GDPR erasure requests. On receiving this notification, the relevant team should remove the customer's personal data from Optimove in line with your organization's data retention policy and applicable law.
Shopify – Shop Redact Request
Sent when a merchant uninstalls the Optimove Shopify app and requests that all their shop data be deleted from Optimove's systems.
Who should subscribe: Technical or operations teams responsible for merchant offboarding, to ensure that shop-level data is removed as required.
Platform Health Notification
Identified issues with event listeners
Sent when a registered webhook fails, that is, when a URL you have registered to receive a system event returns an error or cannot be reached during notification delivery.
This is the only notification that monitors your other notifications. It is designed to catch situations where a webhook endpoint goes down silently, so you can investigate and restore the integration before data is lost.
What the email tells you: Which listener URL failed and what error was returned.
Who should subscribe: Technical teams who manage webhook integrations. To avoid email floods if an endpoint is down for an extended period, this alert is capped to a maximum of one email per 10 minutes per site.
Note: This notification only fires for failed webhook listeners. It does not fire for failed email deliveries.