Optimizely One Platform Overview
Why a unified platform matters
Section titled “Why a unified platform matters”Most digital teams juggle disconnected tools — one system for content, another for experiments, a third for customer data, and a fourth for analytics. Each tool has its own login, its own data model, and its own idea of who the customer is. The result is fragmented data, duplicated effort, and an inability to see how content, experimentation, and personalization work together.
Optimizely One brings these capabilities into a single platform. Products share a common identity layer (Opti ID), exchange data through standard integration points, and surface insights through unified analytics. This does not mean you must adopt everything at once — it means that when you add a product, it connects to what you already use without custom integration work.
The seven product areas
Section titled “The seven product areas”Optimizely One organizes its capabilities into seven product areas. Each addresses a distinct business need, and each can be adopted independently or together.
1. Content Management
Section titled “1. Content Management”Products: CMS SaaS, CMS PaaS
What it solves: Creating, managing, and delivering digital content across websites and applications.
Choose CMS SaaS when:
- You want a managed, cloud-native CMS with no infrastructure to maintain
- Your team prioritizes speed of deployment and automatic updates
- You are building headless or hybrid content architectures
Choose CMS PaaS when:
- You need deep .NET extensibility and custom business logic
- Your organization requires on-premises or private cloud hosting
- You have existing CMS PaaS investments to maintain
Key documentation:
2. Experimentation
Section titled “2. Experimentation”Products: Web Experimentation, Feature Experimentation
What it solves: Testing changes before committing to them — from visual UI tweaks to backend feature rollouts.
Choose Web Experimentation when:
- You want to test visual changes on an existing website without developer involvement
- Your experiments are primarily client-side (layout, copy, design)
- Marketing teams need to run tests independently
Choose Feature Experimentation when:
- You need server-side experiments and feature flags
- Your team practices progressive delivery (gradual rollouts)
- You want to test backend logic, pricing, or algorithms
Key documentation:
3. Personalization
Section titled “3. Personalization”Products: Optimizely Personalization
What it solves: Showing different content to different visitors based on who they are and what they have done.
Choose Personalization when:
- You want to target content to audience segments in real time
- You need to combine behavioral, demographic, and transactional data for targeting
- Your personalization strategy spans multiple channels
How it connects:
- Reads audience segments from ODP
- Delivers personalized content through CMS visitor groups
- Measures impact through Experimentation and Analytics
Key documentation:
4. Data Platform
Section titled “4. Data Platform”Products: ODP (Optimizely Data Platform), Analytics
What it solves: Unifying customer data from all touchpoints into a single profile and providing behavioral analytics.
Choose ODP when:
- You need a unified customer view across channels (web, email, in-store, mobile)
- You want real-time audience segments for personalization and targeting
- Your data strategy requires customer data unification beyond website analytics
Choose Analytics when:
- You want to understand how content and experiments perform
- You need product-aware analytics that connect CMS, Experimentation, and Personalization insights
- You want dashboards that correlate content changes with business outcomes
How it connects:
- ODP segments feed into Experimentation audience targeting
- ODP profiles power Personalization across CMS and other channels
- Analytics aggregates data from all products into unified dashboards
5. Commerce
Section titled “5. Commerce”Products: Commerce Connect, Commerce Classic (Configured Commerce)
What it solves: Running B2B and B2C commerce experiences integrated with content and personalization.
Choose Commerce Connect when:
- You want to integrate Optimizely content and experimentation with an existing commerce platform
- Your commerce backend is handled by a third-party system
- You need composable commerce architecture
Choose Commerce Classic when:
- You need a full-stack B2B commerce solution
- Your business requires complex catalog management, pricing rules, and order workflows
- You want commerce and CMS tightly integrated on one platform
6. Content Marketing Platform
Section titled “6. Content Marketing Platform”Products: CMP (Content Marketing Platform)
What it solves: Planning, creating, and collaborating on marketing content before it reaches CMS for publication.
Choose CMP when:
- Your marketing team needs structured campaign planning and calendars
- You want editorial workflow and approval processes for marketing content
- You need to coordinate content creation across distributed teams
- You want asset management integrated with content planning
How it connects:
- Content created in CMP publishes to CMS for delivery
- CMP content is indexed by Graph for headless access
- Campaign analytics feed back from Analytics
7. AI (Opal)
Section titled “7. AI (Opal)”Products: Opal
What it solves: AI-powered assistance across the platform — content generation, experiment suggestions, and data insights.
Choose Opal when:
- You want AI to help draft content, suggest experiments, and surface insights
- Your team wants to accelerate content creation without sacrificing quality
- You need AI that understands your specific products and data (not generic AI)
How it connects:
- Opal reads content from CMS to provide context-aware suggestions
- Opal analyzes experiment results to recommend next steps
- Opal requires Opti ID for authentication and context
Key documentation:
- Opti ID and Optimizely One — Opti ID is required for Opal
The identity layer: Opti ID
Section titled “The identity layer: Opti ID”Opti ID is not a product you “use” — it is the foundation that makes everything else work together. Every Optimizely product authenticates through Opti ID, which means:
- One login — Users sign in once and access every product in their organization
- Unified roles — Administrators manage permissions from a single admin console
- Shared context — Products know who the user is, enabling features like Opal that span products
- Enterprise SSO — Connect to your existing identity provider via SAML 2.0 or OIDC
Key documentation:
The content delivery layer: Graph
Section titled “The content delivery layer: Graph”Optimizely Graph provides a unified content API that spans multiple content sources. Content authored in CMS, CMP, or Commerce is indexed by Graph and available through a single GraphQL endpoint.
This means frontend teams can query content from any Optimizely source using one API, one set of credentials, and one query language.
Key documentation:
Product decision framework
Section titled “Product decision framework”Use this framework when deciding which products to adopt.
By team need
Section titled “By team need”| Need | Start with | Add later |
|---|---|---|
| We need a website | CMS (SaaS or PaaS) | Graph, Experimentation |
| We want to test changes | Web Experimentation | Feature Experimentation, Analytics |
| We want to personalize content | CMS + Personalization | ODP (for richer segments) |
| We need customer data unification | ODP | Personalization, Analytics |
| We run an online store | Commerce (Connect or Classic) | CMS, Experimentation |
| We plan marketing campaigns | CMP | CMS, Analytics |
| We want AI assistance | Opal + Opti ID | Any product (Opal spans all) |
Adoption sequence
Section titled “Adoption sequence”Most organizations follow a pattern like this:
- Start with one product — Usually CMS or Experimentation, depending on whether content or optimization is the priority
- Add Opti ID — Enable unified identity across your organization
- Add a complementary product — If you started with CMS, add Experimentation. If you started with Experimentation, add a content strategy.
- Add data — ODP and Analytics provide the data foundation for personalization and measurement
- Add AI — Opal becomes most valuable when it has content and data to work with
Ecosystem architecture
Section titled “Ecosystem architecture”+------------------------------------------------------------------+| Optimizely One || || +------------------+ +------------------+ +-------------+ || | CMS SaaS/PaaS | | Experimentation | | ODP | || | (Content) |--->| (Web + Feature) |<-->| (Data) | || +--------+---------+ +--------+---------+ +------+------+ || | | | || v v v || +--------+---------+ +--------+---------+ +------+------+ || | Graph | | Personalization | | Analytics | || | (Delivery API) | | (Targeting) | | (Insights) | || +------------------+ +------------------+ +-------------+ || || +------------------+ +------------------+ +-------------+ || | CMP | | Commerce | | Opal | || | (Marketing) | | (Transactions) | | (AI) | || +------------------+ +------------------+ +-------------+ || || +--------------------------------------------------------------+ || | Opti ID (Identity) | || +--------------------------------------------------------------+ |+------------------------------------------------------------------+Key data flows:
- CMS to Graph — Content is automatically indexed for headless delivery
- ODP to Personalization — Customer segments drive content targeting
- Experimentation to Analytics — Experiment results feed unified dashboards
- Opti ID to everything — Authentication and authorization for all products
- Opal across all — AI reads from CMS, Experimentation, and ODP to provide contextual assistance