Get started with omnichannel content

Omnichannel content (OCC) lets you create and distribute content across the channels in their respective ecosystem.

OCC has the following conceptual types.

When OCC integrates with Optimizely Content Marketing Platform (CMP), CMP OCC has additional conceptual types, described in the following sections.

An instance refers to how data is separated logically from one another. One organization, company, or legal entity can have multiple instances, each serving a specific purpose. These instances can be used for different reasons, such as isolating environments or separating various business units. Customers can determine how they use each instance when set up without restrictions on their intended purpose.

In the context of OCC, content types defined in an instance are unique and encapsulated within that instance only.

A content type defines how a piece of content should be structured or what it should include. Each content type has a name and consists of field definitions and metadata.

Content refers to an instance of a content type, analogous to what instance is to an object in the object-oriented paradigm. Understanding content within a digital asset manager (DAM) library can sometimes be confusing. Typically, content in a DAM refers to a group of assets that form a final deliverable product. However, OCC content encompasses both perspectives: it can refer to content within the context of DAM and partial content or fragments that act as assets within a DAM.

For example, a Blog content type has a author field (along with other fields) that references an Author content type. Author also has reference fields called home_address and work_address each of which references Address. Every instance of Blog and Author can be considered as content in the context of OCC and DAM. However, authors working with the same agent can share a working address so that commercial addresses can live as DAM assets referred to by many authors, such that a work_address instance of address would be OCC content, but not DAM content. It instead would be a DAM asset.

A task is where you create assets by processing them through a workflow and collaborating with contributors and stakeholders. In CMP, a task is where work happens. It is also where you schedule assets for distribution through publishing.

Drafts and versions refer to revisions of assets, but their contexts are different.

Content preview refers to an HTML-based representation of a piece of content to mimic what the content looks like at delivery. CMP does not dictate what a preview is. As part of the webhookswebhooks and APIsAPIs, only a URL is expected to returnreturn an HTML that you can render as a preview within a task and library. A preview associated with the final draft of an asset is carried along with it as a preview for the asset's version in the library to work as a thumbnail. See Work with previews.

CMP can associate a pixel with a piece of content. When you leverage CMP's Analytics JavaScript, you can collect content analytics, measure conversion, and measure ROI. CMP has designed a system content type for this that looks like:



This content type gets special treatment from the editor. The user interface automatically adds the pixel as a reference, but you can delete it. If you (optionally) install the Analytics JavaScript and use the pixel from the content on the delivered page, customers can get content analytics in CMP.

Publishing assets and contents refers to CMP distributing them to downstream channels. See Push and pull OCC strategies. Some social channels are directly integrated with CMP and the respective APIs, but for Optimizely Content Management System (CMS) and other downstream channels, WebhooksWebhooks are used.

Publishing is the most common form to Push content from CMP to a downstream channel.