OpenText Core Content - Metadata - Optimizely Integration and Automation

Common Integration Use Cases Between OpenText Core Content - Metadata and Optimizely

• 1. Governed metadata sync for web content personalization

  Data flow: OpenText Core Content - Metadata ? Optimizely

  Push approved metadata fields such as content type, audience, region, product line, and campaign status from OpenText Core Content - Metadata into Optimizely to support segmentation and personalization rules. This ensures marketing teams use consistent, governed attributes when targeting content variations, reducing manual tagging errors and improving campaign accuracy.

• 2. Metadata-driven content eligibility for A/B testing

  Data flow: OpenText Core Content - Metadata ? Optimizely

  Use metadata validation rules in OpenText Core Content - Metadata to mark assets and pages as test-ready, approved, expired, or restricted. Optimizely can then automatically include only eligible content in experiments, preventing unapproved assets from being used in live tests and speeding up experimentation governance.

• 3. Experiment performance reporting by content metadata

  Data flow: Optimizely ? OpenText Core Content - Metadata

  Send experiment results such as variant ID, conversion rate, engagement score, and winning content back into OpenText Core Content - Metadata as reference metadata. Content owners can then analyze which asset categories, messages, or formats perform best across campaigns and use that insight to improve future content planning and governance.

• 4. Controlled vocabulary alignment for campaign and audience taxonomy

  Data flow: Bi-directional

  Synchronize controlled vocabularies between both platforms for terms such as product names, market segments, regions, and lifecycle stages. This creates a single taxonomy for content classification in OpenText Core Content - Metadata and audience targeting in Optimizely, improving searchability, reporting consistency, and cross-team alignment.

• 5. Automated content routing for personalization workflows

  Data flow: OpenText Core Content - Metadata ? Optimizely

  When content is tagged with specific metadata values, route it into the correct Optimizely personalization workflow. For example, assets tagged for enterprise customers, French language, or healthcare can be automatically surfaced to the right experience variants, reducing manual content selection and accelerating campaign deployment.

• 6. Metadata-based content reuse across experiments

  Data flow: OpenText Core Content - Metadata ? Optimizely

  Expose structured metadata to help Optimizely teams find and reuse approved content assets across multiple tests and experiences. This is especially useful for large organizations managing many product pages or regional sites, where consistent metadata makes it easier to locate the right image, copy block, or CTA for each experiment.

• 7. Compliance and audit support for digital experience changes

  Data flow: Bi-directional

  Use OpenText Core Content - Metadata to store approval status, ownership, retention, and compliance attributes for content used in Optimizely experiments. In return, Optimizely can provide usage and deployment details for audit trails. This helps regulated industries track which approved assets were used in which tests and when, supporting governance and review processes.