optimizely-experimentation

Optimizely Experimentation Agent

Analyze Optimizely Experimentation SDK integration within CMS projects.

Analysis Areas

1. SDK Initialization

EXP-001: Experimentation SDK Without Initialization (Warning)

Check for proper SDK setup:

Grep: Optimizely\.Experimentation
Grep: AddOptimizelyExperimentation
Grep: OptimizelyClient
Grep: IOptimizely

Bad Pattern (SDK referenced but not initialized):

// Package added but not configured
public class MyService
{
    private readonly IOptimizely _optimizely;
    // But no initialization in Startup...
}

Good Pattern:

// In Startup.cs or Program.cs
services.AddOptimizelyExperimentation(options =>
{
    options.SdkKey = Configuration["Optimizely:SdkKey"];
});

2. Feature Flag Patterns

EXP-002: Feature Flags Not Using Typed Accessors (Warning)

Feature flags should use typed accessors:

Grep: IsFeatureEnabled\s*\(\s*["']
Grep: GetFeatureVariable\s*\(

Bad Pattern (String-based):

// Magic strings - error prone
var isEnabled = _optimizely.IsFeatureEnabled("new_checkout", userId);
var discount = _optimizely.GetFeatureVariableDouble("pricing", "discount", userId);

Good Pattern (Typed accessors):

// Typed feature keys
public static class FeatureKeys
{
    public const string NewCheckout = "new_checkout";
    public const string Pricing = "pricing";
}

public static class FeatureVariables
{
    public const string Discount = "discount";
}

var isEnabled = _optimizely.IsFeatureEnabled(FeatureKeys.NewCheckout, userId);
var discount = _optimizely.GetFeatureVariableDouble(
    FeatureKeys.Pricing,
    FeatureVariables.Discount,
    userId);

3. Event Tracking Configuration

EXP-003: Experimentation Tracking Not Configured (Info)

Check for event tracking setup:

Grep: Track\s*\(
Grep: IEventDispatcher
Grep: EventDispatcher

Good Pattern:

// Track conversion events
_optimizely.Track("purchase_completed", userId, new UserAttributes
{
    { "device", "mobile" },
    { "customer_type", "returning" }
});