Back to docs
Site Configuration

A/B Testing with Flint

Plug in Statsig, LaunchDarkly, or Eppo. Your feature flags control what Flint serves.

How it works

Flint integrates with popular experimentation platforms to enable A/B testing on your pages. The setup follows three steps:

Step 1: Add the platform SDK script to your Flint site

Click the Settings button in the top navigation, then go to Site Settings > Custom Code and paste your platform's JavaScript snippet into the Head field. See the platform-specific guides below for the exact snippet.

Step 2: Prompt the Flint agent to instrument your experiment

Here's an example prompt for testing hero copy with Statsig:

text
Create a variant of the / page called /variant-hero with Statsig A/B testing for the hero section.

Requirements:
1. The /variant-hero should change header text from "Your company's always-on website agent" to "Landing pages that build themselves"

2. Use window.statsig.getExperiment('hero_copy_test') to read the active variant on page load and apply the correct headline. Statsig is already loaded via script tag.

3. Add these classes to the hero elements:
Headline: class="hero-headline"
Subheadline: class="hero-subheadline"
CTA Button: class="cta-button"

Step 3: Configure and start your experiment in your testing platform

Add your parameters, set up variants, and flip the experiment live. Your platform will begin splitting traffic and collecting results.

Custom Code panel in Flint Site Settings

Test at two levels

You can run experiments at different granularities:

  • Individual components on a single page - Test different headlines, images, CTAs, or any other component
  • Full page variants - Test completely different page designs against each other

This flexibility lets you run quick copy tests or major redesign experiments.

Ad platform

Use the experimentation module on Google Ads, more info found on Google's Ad Experiment page.

Google Ads experimentation module interface

Platform-specific setup guides

For step-by-step instructions on connecting a specific platform to your Flint site, see the individual guides:

  • A/B Testing with VWO - Point-and-click visual editor, ideal for non-technical teams. Includes heatmaps and session recordings.
  • A/B Testing with Optimizely - Enterprise-grade experimentation with AI-powered test recommendations and data warehouse integration.
  • A/B Testing with Statsig - Developer-friendly platform with a generous free tier, built-in session replay, and product analytics.

Other platforms that follow the same pattern (add their SDK snippet to the Head field, then prompt the Flint agent to instrument your pages) include LaunchDarkly, Eppo, AB Tasty, and Adobe Target.

Coming soon

Native A/B testing built into Flint - continuous and autonomous.

This will allow you to run experiments without any external platform integration, with Flint automatically optimizing your pages based on conversion data.