2026 Optimizely Connect Platform release notes
4 min
Plan Type
The OCP database is not included in the free version of OCP. The free version syncs data in real-time without using the OCP database, letting you access public apps and data syncs.
Contact your Customer Success Manager if you have any questions.
Follow this article to receive email notifications when new Optimizely Connect Platform (OCP) content is added for 2026.
June
- (Beta) Released CMS UI extensions, which let developers add interactive panels to the Optimizely Content Management System (CMS) content editor and back them with functions running on the Optimizely Connect Platform (OCP). This lets teams extend the editing experience without configuring separate frontend infrastructure. See CMS UI Extensions for more information
- Released data sync health metrics, which give you real-time visibility into each data sync's performance so you can pinpoint where items drop off across pipeline stages and resolve sync issues faster. The detail page shows a health status badge, Items received and Items delivered totals, drop-off by stage, and a granular performance breakdown over a date range you choose. See Sync manager overview for information.
May
- Added autocomplete dynamic values to ocp autocomplete in OCP CLI v2, which suggests context-aware values for command arguments and flags retrieved from your account, and a --refresh-cache flag to manually refresh the cache.
- Added scaffold commands through a new `ocp add command group` (ocp add function, ocp add job, ocp add source, and ocp add destination) for adding components to an existing app. Additionally, added a --no-prompt mode for ocp app init and ocp app register, allowing both commands to run in CI pipelines and other unattended contexts.
April
- Published an end-to-end guide to build a reference OCP app that syncs product data from an external source into OCP. The reference app is based on a real-world Shopify integration and uses a simplified, externally ready version of the source code, making it easier for developers to understand how to implement historical imports, real-time webhook updates, and product deletion handling without internal dependencies. View the full source code on GitHub.
- The local testing tool is now generally available. This release also adds Opal tools and ODP API callsOpal tools and ODP API calls compatibility, enabling end-to-end local testing across your Optimizely stack.
March
- Released the Optimizely Connect Platform (OCP) command-line interface (CLI) v2, with multiple package manager support, ocp update, ocp autocomplete, flexible parameter syntax, and standalone installation. If you have the beta version installed, run ocp update stable to install the stable release. For setup and migration from v1 to v2, see OCP CLI v2 migration guide.
- Enhanced support for nested fields under Source Fields and Destination Fields when configuring Field Mappings for data syncs between Content Marketing Platform (CMP) and Optimizely Graph. Building on the existing nested object and array support in OCP, you can now map nested source and destination fields with greater precision when syncing data between CMP and Graph.
- Added a data deletion option for data syncs between Content Marketing Platform (CMP) and Optimizely Graph created through OCP. When configuring the sync, select None to retain the data, Soft to keep the record with an expired timestamp, or Hard to permanently remove the data from Optimizely Graph.
- Published an end-to-end guide to build a reference OCP app that lets developers build OCP apps with Optimizely Opal tools. The reference app is based on the publicly available Google Analytics 4 Opal tool and uses a simplified, externally ready version of the source code, making it easier for developers to understand the implementation pattern without internal dependencies. View the full source code on GitHub.
January
- Simplified the process of adding a custom data sync source to an Optimizely Connect Platform (OCP) app. Previously, configuring a custom source required defining source-specific function, lifecycle, and jobs entries directly within each source in the app manifest. Custom sources now follow a streamlined three-step setup by declaring the sources in app.yml, declaring the schema, and emitting data using sources.emit().