---
title: Integrate Optimizely Content Marketing Platform with CMS (SaaS)
slug: cms-saas/docs/integrate-cmp-with-cms-saas
createdAt: 2026-11-19T15:57:58.000Z
---

Integrate Optimizely Content Marketing Platform (CMP) with Optimizely Content Management System (SaaS) to plan, create, review, and publish web content as part of a CMP task. Marketing managers work in CMP to create CMS pages from structured content, track their progress, and publish them. CMS editors work on the same pages in CMS and use CMP assets without copying them between systems.

Use the integration to run web content through the same CMP campaign workflow as your other channels. Structured content and assets stay in CMP, so teams do not maintain copies of them in CMS.

The integration builds on external content in CMS (SaaS). For details on connected content, content type mappings, and property mappings, see [Integrate external content sources with CMS (SaaS)](https://docs.optimizely.com/cms-saas/docs/integrate-external-resources). Unlike other external content sources, you do not configure CMP through Optimizely Connect Platform (OCP). Instead, you connect CMP and CMS (SaaS) directly with an API key from CMS and an integration in CMP.

## How the integration works

The integration connects a CMP task with one or more CMS content items:

- **Create CMS content from CMP** – A CMP user creates a CMS page from a structured content item in a task, using a CMS blueprint. CMS creates the page at the selected location and adds it to the task.
- **Add existing CMS content to a CMP task** – A CMS user adds a page they are working on to a CMP task.
- **Use CMP assets in CMS** – A CMS user connects assets that belong to the CMP task to CMS content.
- **Preview, review, and publish from CMP** – The CMP task shows a live preview of each linked CMS content item. CMP users review and publish the content from the task.

Each product remains the source of truth for its own data:

- **CMP** – Tasks and workflows, Digital Asset Management (DAM) assets, and structured (omnichannel) content.
- **CMS** – Content items, compositions, and channel-specific properties.

## Before you begin

Complete the following before you connect CMP and CMS (SaaS):

- **Connect Optimizely DAM** – Connect your CMS (SaaS) instance to Optimizely DAM. The integration uses the same configuration as the DAM integration. See [Onboard DAM to CMS (SaaS)](https://docs.optimizely.com/cms-saas/docs/onboard-dam-to-cms-saas).
- **Get administrator access** – You need administrator access in CMS (SaaS) to create API keys and set access rights, and in CMP to add integrations.

## Enable the integration

The integration connects CMP and CMS (SaaS) in both directions:

- **CMS to CMP** – CMS calls the CMP API to list tasks and add content to them. CMS (SaaS) uses your existing DAM connection for this, so you do not need to configure it.
- **CMP to CMS** – CMP calls the CMS API to create and publish content. You create an API key in CMS (SaaS), give it access rights, and add it to an Optimizely CMS integration in CMP.

After you add the integration, your CMS (SaaS) instance displays as a channel in CMP, and CMS editors see **Add to task** in the CMS Visual Builder UI.

### Create an API key for CMP

1. Go to **Settings** > **API Keys** in CMS (SaaS).
2. Click **Create API Key**.
3. Enter a **Name**, for example, *cmp-integration*, and click **Create API Key**.
4. Copy the **Client ID** and **Secret** and save them in a secure location. You cannot view the secret again after you close the window.
5. Click **Done**.

For more information, see [Create API keys](https://docs.optimizely.com/cms-saas/docs/api-keys).

### Give the API key access rights

CMP uses the API key to browse the CMS content tree, list blueprints, create pages, and publish content. The key needs the following access rights:

- **Read** – Browse the content tree when a CMP user selects a location, and create content there.
- **Create** – Create pages.
- **Publish** – Publish the content in a task.
- **Administer** – Publish without reference validation. CMP skips reference validation when it publishes, and CMS allows that only with **Administer** access rights.

The key does not need **Change** or **Delete** access rights.

Set the access rights in the following places:

- **Start page** – Give the key all four access rights on the start page of each site that CMP creates content in or publishes to. Do not set them on the root, so the key only has access to the content CMP works with. Pages under the start page inherit the access rights. If a branch has its own access rights, add the key there too.
- **Pages that editors add from CMS** – Editors can add pages from anywhere in CMS to a task. CMP can publish a task only if the key has **Publish** and **Administer** access rights on every page in it.
- **Blueprints folder** – Give the key **Read** access rights on the **Blueprints** folder. The folder is under the root, not the start page, and does not inherit access rights. Without **Read** access rights, the **Blueprint** list in CMP is empty and CMP cannot create pages.

To set the access rights:

1. Go to **Settings** > **Set Access Rights** in CMS (SaaS).
2. Select the content, for example, your start page.
3. Click **Add User/Group** and search for the API key's **Client ID**. For example, *1f6c964310624abdhei47f64f3b9a62d*.
4. Select the access rights for the client ID.
5. Click **Save Access Rights**.

![screenshot of the API key's access rights for CMS and CMP integration](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/7vE__6JAMsBPfV0l3GERT_api-key-access-rights.png)

For more information, see [Set access rights](https://docs.optimizely.com/cms-saas/docs/access-rights).

### Add the Optimizely CMS integration in CMP

1. Go to **Settings** > **Integrations** in CMP.
2. Select the **Website, CMS & Feed** tab.
3. Click **Add** > **Optimizely CMS**.
4. Define the following. All fields are required.
   - **Display Name** – The name CMP users see for the channel under **Add to Channel**, for example, *Stride.com (Production)*.
   - **CMS Site URL** – The URL of your CMS (SaaS) instance, for example, `https://app-xxxxxxxx.cms.optimizely.com`.
   - **CMS Type** – Select **SaaS**.
   - **API Key (OAuth Client ID)** – The client ID of the API key you created in CMS (SaaS).
   - **API Secret (OAuth Client Secret)** – The secret of the API key.
5. Click **Save**.

## Prepare content types and blueprints

CMP users create CMS pages from structured content in a task. To set this up, a CMS administrator connects CMP structured content types to CMS and maps them to CMS content types. The administrator then creates blueprints for those content types.

### Prepare structured content types in CMP

A structured content type defines the fields that CMP users fill in for a piece of content in a task. CMP also calls structured content *omnichannel content*. Use an existing structured content type, or create one if you do not have a suitable type. Content types created in the CMP UI or with the CMP API work with the integration.

To create a structured content type, see [Create content types, components, and fields](https://docs.optimizely.com/content-marketing-platform/docs/edit-content-with-omnichannel-authoring#create-content-types-components-and-fields) in the CMP documentation. To create content types with the CMP API, see [Content type versions](https://docs.optimizely.com/content-marketing-platform/docs/content-type-versions).

### Connect CMP structured content types to CMS

CMS reads CMP structured content from Optimizely Graph. Before you map a CMP structured content type, connect it to CMS with **Connect from Graph**. You use the same process as for other external content sources. See [Connect external content sources using GraphQL](https://docs.optimizely.com/cms-saas/docs/connected-content-sources).

### Map CMP content types to CMS content types

Map each CMP structured content type to the CMS content type you want to create from it. Mappings are many-to-many, so you can map a CMP content type to more than one CMS content type, and the reverse. You use the same mapping process as other external content sources. See [Create content type mappings and map properties](https://docs.optimizely.com/cms-saas/docs/integrate-external-resources#part-3-create-content-type-mappings-and-map-proper).

### Create blueprints for mapped content types

CMP users create CMS pages from blueprints. When a CMP user selects a parent location in CMS, CMP shows only the blueprints that meet both of the following conditions:

- The blueprint's content type has a mapping for the selected structured content type.
- The blueprint's content type is allowed as a child of the selected location.

Create at least one blueprint for each mapped content type. See [Manage blueprints](https://docs.optimizely.com/cms-saas/docs/blueprints) and [Save as blueprint](https://docs.optimizely.com/cms-saas/docs/save-as-blueprint).

## Create CMS content from a CMP task

CMP users create CMS pages from the **Content** tab of a CMP task.

### Create a page

1. Open the task in CMP and go to the **Content** tab.
2. Select **More** > **Add to Channel** on the structured content item. The **Create CMS Page** window displays.
3. Define the following. All fields are required.
   - **CMS channel** – The CMS channel to create the page in, for example, **Stride.com (Production)**.
   - **Locale** – The language of the new page.
   - **Parent location in CMS** – Where to create the page in the CMS content tree. The selected location displays below the tree.
   - **Blueprint** – The blueprint to create the page from.
4. Click **Create page**.

::Image[]{src="https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/v1ej6nyLqPf6BBCghBQ4o_add-to-channel.png" size="100" isUploading="false" position="center" width="1642" height="1412" darkWidth="1642" darkHeight="1412" showCaption="false" indent="1"}

CMS creates the page as a draft from the blueprint, in the selected locale and parent location. CMS connects the page to the structured content and adds it to the task. The **Content** tab then shows a live preview of the page.

CMS does not copy the structured content into the page. It reads the values from Optimizely Graph, so when you update the structured content in CMP, the page displays the new values automatically.

## Add existing CMS content to a CMP task

CMS editors can add pages, shared blocks, and other assets they are working on to a CMP task.

1. Open the content in CMS (SaaS).
2. Select **More** > **Add to task**. The **Add to Task** window displays.
3. Search for the task by name, select it, and click **Add to Task**. Completed CMP tasks are not listed.

CMS displays **Part of task:** *task name* on the content, with a link to the task. The content also displays on the task's **Content** tab in CMP.

A content item can belong to only one active CMP task. After the task is completed or the content is published, you can add a new draft of the content to another task.

### Remove content from a task

1. Open the content in CMS (SaaS).
2. Select **More** > **Remove from task**.

The content stays in CMS, but it is no longer part of the CMP task.

## Use CMP assets in CMS content

When content belongs to a CMP task, CMS editors can connect assets from that task and from the CMP Library to CMS properties. For content that is not part of a task, **DAM (CMP)** shows only Library assets.

1. Open the page in CMS (SaaS) that belongs to the task and select the block or element to edit, for example, a **Hero** block.
2. Select **More** > **Connect Content**.
3. Select **DAM (CMP)** under **Locations**.
4. Select the asset and click **Connect Content**.

The connected properties display a link icon and are read-only in CMS, because their values come from CMP.

Files attached to a CMP task are work in progress and are not in the CMP Library yet. When CMP publishes the CMS content, it copies the task assets into the Library, and CMS updates its references to point to the Library assets. Editors do not see a change in CMS.

## Preview, review, and publish from CMP

The **Content** tab of a CMP task shows a live preview of each CMS content item in the task. The preview updates as editors change the content in CMS.

Content in a CMP task can be published only from the task. In CMS, **Publish** and **Schedule for Publish** are not available for that content. When the content is ready, CMS editors select **Ready to Publish**.

When CMS content is added to a task, CMP adds the matching CMS channel to the task's **Publishing** tab. The **Publishing** tab shows which content is selected for publishing, and to which channel.

To publish the content, click **Mark Task Complete** in CMP. CMP then asks CMS to publish the content, using the API key you added to the Optimizely CMS integration. Follow the publishing progress on the **Publishing** tab.

After CMP publishes it, the content behaves like any other published content in CMS, and editors can create new versions of it as usual. For CMS publishing in general, see [Control the publishing process](https://docs.optimizely.com/cms-saas/docs/control-the-publishing-process).

:::hint{type="info"}
**Note**
CMP cannot bypass the publishing rules in CMS. If an approval sequence applies to the content, CMS does not publish it until a CMS user approves it. CMS also publishes the content only if the API key has **Publish** access rights on it.
:::

## Limitations

The following features are not part of the integration:

- Creating translations of existing pages from CMP.
- Creating blocks from CMP. CMP users can create only pages.
- Scheduled publishing. CMS publishes the content as soon as the task is marked complete.
