External Content Integration

In Optimizely CMS 13, external content integration is reimagined through a "Graph-first" architectural lens. Unlike previous versions where bringing in third-party data often required complex, custom-built Content Providers that directly queried external APIs, CMS 13 leverages Optimizely Graph as the central hub for all unified content discovery and delivery.

The Concept of Unified Content Discovery

In the past, "external content" meant data that lived outside the tblContent database table. In CMS 13, the distinction between "local" and "external" content becomes secondary to where the content is indexed.

External content integration in CMS 13 terms means the process of synchronizing third-party data—such as product catalogs, digital assets from a DAM, or articles from a legacy system—into the Optimizely Graph index. Once indexed, this data is surfaced within the CMS user interface using the same tools editors use for native pages and blocks.

The Content Provider Integration Pattern

CMS 13 introduces a new integration pattern that allows developers to connect external content sources specifically via Optimizely Graph.

• Ingestion: Data is pushed from the external source into Optimizely Graph.
• Surfacing: Developers configure the CMS to recognize specific schemas within Graph as content items.
• Usage: Content editors can search for, select, and reuse these external items when composing experiences in the Visual Builder or Content Manager.

Graph-First vs. Legacy Approaches

The legacy approach to external content often suffered from performance bottlenecks because the CMS had to fetch live data from external APIs during the rendering pipeline. The CMS 13 approach solves this via Index Unification.

Conclusion

External content integration in CMS 13 is about using Optimizely Graph as the connective tissue to blend native and external data into a consistent, low-friction editor interface.