9 June 2026

OOTB Events

Updated Registration Initiated and Registration Failed event references

The Registration Initiated and Registration Failed event reference articles have been updated to align with the latest event definitions — covering the event key, parameters table, and JSON example for both events.

Impact: Implementations sending Registration events should verify their payloads match the updated schema.

For the full event schema, see the Registration Initiated and Registration Failed references.

Five Self-Exclusion events now live

The following Self-Exclusion OOTB events are now live and documented in the Developer Hub:

• Self-Exclusion: Initiated — fired when a customer initiates a self-exclusion request
• Self-Exclusion: Activated — fired when the self-exclusion period becomes active
• Self-Exclusion: Updated — fired when an existing self-exclusion is modified
• Self-Exclusion: Violation Attempt — fired when a customer attempts to engage during an active exclusion period
• Self-Exclusion: Lifted — fired when a self-exclusion period ends and the customer is reinstated

Impact: Implementations that need to track responsible gambling workflows should integrate these events. Review the event schemas and align your payloads accordingly.

Customer Data API

Upsert Customer endpoint marked as legacy — use Batch Add Customers

The Upsert Customer (PUT /customers/upsertcustomer) endpoint has been marked as a legacy API. The article now directs developers to the Insert or Update Customers endpoint, which supports batch operations and is the recommended approach for all new implementations.

Impact: No breaking change — the legacy endpoint remains functional. New integrations should use the batch endpoint.

For the current recommended approach, see the Insert or Update Customers reference.

Fixed Total_Payment field definition in Prepare Your Data for Ecommerce

The definition of the Total_Payment field in the Orders_Summary table on the Prepare Your Data for Optimove — Ecommerce page has been corrected.

Impact: Documentation only — no changes to data schema required.

SDK & Integration

Updated Flutter SDK version to 3.3.3

The optimove_sdk_flutter dependency version referenced in the Optimobile Getting Started integration guide has been updated from an outdated version to the current release:

dependencies:
  optimove_sdk_flutter: 3.3.3

Impact: Developers setting up a new Flutter integration should use version 3.3.3. Existing integrations should check their pubspec.yaml against the latest release.

Renamed "Track & Trigger" to "real-time" throughout Web SDK Integration guide

All references to "Track & Trigger" and the abbreviation "T&T" in the Web SDK Integration guide and its child articles have been updated to use current terminology — "real-time" or "real-time capabilities" depending on context.

Impact: Documentation only — no functional changes.

Data Sharing

Fixed broken Snowflake links in Data Sharing Methods

Three broken links pointing to the Snowflake documentation in the Data Sharing Methods article have been fixed. The affected links were: Reader Accounts Overview, Snowflake Data Sharing Concepts, and Snowflake Credit System Concepts.

Impact: Documentation only — no functional changes.

OptiPromo

Updated Promo System Safeguards and Best Practices article

Two updates were made to the Promo System Safeguards and Best Practices article:

1. The article title has been updated to "Promo System Safeguards and Best Practices".
2. A sentence in the Manual Promo Backup section has been corrected: "campaign execution" has been changed to "promotion allocation", and "system" has been changed to "Optimove".

Impact: Documentation only — no functional changes.