Is Optimove down?

What's happening Meta (Facebook) is experiencing a service disruption. Because campaign delivery to this channels depends on Meta's APIs, some Optimove campaigns targeting Meta audiences are affected. How this may affect you - Campaigns sending to Meta may fail - Audience syncs to Meta Custom Audiences may stall or error out - Delivery reports and channel metrics for Meta may be delayed or incomplete Important: This is a Meta-side outage, not an Optimove platform issue. Campaigns on all other channels (email, SMS, push, web, and other integrations) are unaffected and running normally. What we're doing Monitoring Meta's status. We will confirm here when Meta service is restored and Meta-channel execution is back to normal.

Meta services have recovered and campaign delivery to Facebook has resumed.

We are currently experiencing errors leading to delays in Daily Batch. As a result, some campaigns may remain in a “Not Run” status. What We’re Doing: Our engineering team is actively investigating the root cause and working to restore normal execution as quickly as possible. Recovery Options: Manual Run: For high-priority campaigns, you can run them manually via the Run Now feature in Mission Control. Hover over the relevant campaign or use the three-dot menu to access the option. https://academy.optimove.com/hc/en-us/articles/8649444827549-Using-Run-Now-Capability Force Run: If your instance has Force Run enabled, campaigns will still be delivered as part of the batch process if this incident is resolved within the grace period. https://academy.optimove.com/hc/en-us/articles/10701094593565-Using-Force-Run. To enable Force Run, please reach out to your Customer Success Manager. Next Update: We will provide an update within 1–2 hours, or sooner if new information becomes available

This incident has been resolved.

We are currently experiencing errors leading to delays in campaign execution. As a result, some campaigns may remain in a “Not Run” status. This typically occurs when the Batch Data Update is delayed and campaign execution starts later than scheduled, causing some campaigns to miss their designated run time. What We’re Doing: Our engineering team is actively investigating the root cause and working to restore normal execution as quickly as possible. Recovery Options: Manual Run: For high-priority campaigns, you can run them manually via the Run Now feature in Mission Control. Hover over the relevant campaign or use the three-dot menu to access the option. https://academy.optimove.com/hc/en-us/articles/8649444827549-Using-Run-Now-Capability Force Run: If your instance has Force Run enabled, campaigns will still be delivered as part of the batch process if this incident is resolved within the grace period. https://academy.optimove.com/hc/en-us/articles/10701094593565-Using-Force-Run. To enable Force Run, please reach out to your Customer Success Manager. Next Update: We will provide an update within 1–2 hours, or sooner if new information becomes available

We are continuing to investigate this issue.

A fix has been implemented and we are monitoring the results.

We are continuing to monitor for any further issues.

This incident has been resolved.

We are currently experiencing errors leading to delays in the daily data update process for some instances. As a result, campaigns scheduled to run after the daily update may be delayed or may remain in a “Not Run” status. This issue affects only some instances using the impacted daily update workflow. Instances using other daily update workflows are not affected. This typically occurs when the daily data update process after the ETL phase is delayed or fails, preventing campaign execution from starting as scheduled and causing some campaigns to miss their designated run time. What We’re Doing: Our engineering team is actively investigating the root cause and working to restore normal execution as quickly as possible. Recovery Options: Manual Run: For high-priority campaigns, you can run them manually via the Run Now feature in Mission Control. Hover over the relevant campaign or use the three-dot menu to access the option: https://academy.optimove.com/hc/en-us/articles/8649444827549-Using-Run-Now-Capability Force Run: If your instance has Force Run enabled, campaigns will still be delivered as part of the batch process if this incident is resolved within the grace period: https://academy.optimove.com/hc/en-us/articles/10701094593565-Using-Force-Run To enable Force Run, please reach out to your Customer Success Manager. Next Update: We will provide an update within 1-2 hours, or sooner if new information becomes available.

A fix has been applied, and the affected daily data update process is now showing signs of recovery. We are currently re-initiating previously failed batch updates in a controlled manner to avoid creating additional load. Some customers may continue to experience delays while these updates are being processed. Next Steps: We are continuing to resume the affected batch update processes and monitor their successful completion. Next Update: We will provide another update within 1–2 hours, or sooner if normal operation is fully restored.

This incident has been resolved.

We identified and resolved a service degradation in our EU environment that impacted some customers. During the affected window, Web SDK events delivery into the Triggered Campaigns path was disrupted, which delayed or prevented triggered campaigns from firing for the impacted accounts. Server-side events, as well as standard Web SDK events, were unaffected throughout the incident. IMPACT - Affected: Triggered Campaigns powered by Web SDK events in the EU region. - Not affected: Server-side event ingestion, scheduled campaigns, Standard Wed SDK Events - Customers may observe a temporary dip in Triggered Campaign volume corresponding to the affected window. ROOT CAUSE The disruption was caused by an infrastructure change deployed in our EU environment on May 18-19, which inadvertently affected the path used to deliver Web SDK events into the platform. NEXT STEPS - We are conducting an internal post-incident review to prevent recurrence. - We are reinforcing our pre-deployment validation for infrastructure changes that affect event ingestion paths. - Events that did not reach the platform during the incident window cannot be retroactively replayed; data captured via server-side integrations during this period is intact. NEED HELP? If you believe your account experienced impact beyond what is described above, please contact us at [email protected] We sincerely apologize for the disruption and appreciate your patience.

This incident has been resolved.