Architecting AI in Optimizely CMS: When to Use Opal vs Custom Integration

AI is rapidly becoming a core capability in modern digital experience platforms. As developers working with Optimizely CMS 12 (.NET Core), the real question is no longer:

“Can we integrate AI?”

But rather:

“What is the right architectural approach for AI inside Optimizely?”

In this article, I’ll share practical implementation patterns, lessons learned, and how to decide between custom AI integration and leveraging Opal.

Why AI Integration Matters in CMS Implementations

Across multiple implementations, I’ve observed recurring challenges:

• Manual metadata tagging

• Inconsistent summaries and SEO descriptions

• Static personalization logic

• Slow campaign iteration cycles

• Limited experimentation insights

AI, when architected correctly, can significantly enhance these areas - without disrupting core CMS performance.

Option 1: Custom AI Integration in Optimizely CMS 12

For organizations requiring flexibility and control, integrating external AI services (e.g., Azure OpenAI or private ML models) remains a powerful option.

Recommended Architecture

Editor → CMS → AI Service Layer → External AI Provider

Step 1: Introduce an Abstraction Layer

public interface IAIContentService
{
    Task<string> GenerateSummaryAsync(string content);
    Task<List<string>> GenerateTagsAsync(string content);
}

This ensures your CMS remains provider-agnostic.

Step 2: Register via Dependency Injection

services.AddHttpClient<IAIContentService, AIContentService>();

Keep AI logic outside controllers and content models. Treat it as infrastructure.

Step 3: Hook into CMS Events

Example: Auto-tag content during publishing.

_contentEvents.PublishingContent += async (sender, args) =>
{
    if (args.Content is ArticlePage page)
    {
        var tags = await _aiService.GenerateTagsAsync(page.MainBody.ToHtmlString());
        page.Tags = tags;
    }
};

Important Considerations

Performance

• Never execute AI calls during page rendering.

• Use background jobs or publish-time triggers.

• Cache generated outputs.

Security

• Store API keys in secure vaults.

• Avoid exposing AI endpoints client-side.

Prompt Governance

Treat prompts like code:

• Version them

• Document them

• Test them

Option 2: Leveraging Opal

Opal introduces AI natively within the Optimizely ecosystem.

Rather than building infrastructure from scratch, Opal enables:

• AI-assisted content creation

• Campaign generation

• Intelligent experimentation insights

• Workflow-level automation

From a developer perspective, Opal reduces:

• Integration complexity

• Maintenance overhead

• Governance concerns

It shifts AI from being API-driven to being workflow-native.

Architectural Decision: Opal vs Custom AI

In enterprise implementations, the decision should be strategic.