Home/Internals/A/B Testing

GrowthBook A/B Testing

Feature flagging and experiment management using GrowthBook for gradual rollouts, A/B tests, and targeted feature releases.

Internal Infrastructure GrowthBook integration is used for Clew's own product development telemetry and experiment tracking. It is not a user-facing feature — this documentation is for contributors and integrators.

Overview

GrowthBook provides feature flagging and A/B testing within Clew. It enables controlled rollouts of new features, experiment tracking, and targeted feature releases based on user segments. The SDK is initialized at startup and evaluates flags locally with caching for minimal latency.

Architecture

  • Feature Flags — Boolean, string, number, and JSON flag types evaluated locally
  • Experiments — Multi-variant A/B tests with statistical tracking and automatic analysis
  • Forced Variations — Override flag values for testing and debugging
  • Sticky Bucketing — Consistent user experience across sessions based on stable identifiers
  • Local Caching — Feature definitions cached after initial fetch for offline resilience

Usage in Code

// Check if a feature is enabled (cached evaluation)
const isEnabled = getFeatureValue_CACHED_MAY_BE_STALE(
  'tengu_plum_vx3',  // Feature key
  false              // Default value
);
// Use the feature value
if (isEnabled) {
  // New behavior path
} else {
  // Control behavior path
}

Configuration

VariablePurpose
GROWTHBOOK_API_HOSTGrowthBook API endpoint (self-hosted or cloud)
GROWTHBOOK_CLIENT_KEYClient-side SDK key for feature flag access
GROWTHBOOK_FORCE_VARIATIONForce a specific variation for testing

How It Works

  1. On startup, Clew initializes the GrowthBook SDK with the configured API host and client key
  2. Feature definitions are fetched from the GrowthBook server and cached locally
  3. Throughout the session, code checks feature flags using the cached evaluation function
  4. Flag values are re-evaluated periodically or on explicit refresh
  5. Experiment results are tracked and sent back to GrowthBook for statistical analysis
  6. Forced variations can override normal bucket assignment for testing

Best Practices

  • Always provide a sensible default value (usually false for features not yet released)
  • Use descriptive, unique feature keys
  • Cache-aware design: do not rely on flag values being real-time; they are evaluated at session start
  • Clean up stale flags after experiments conclude