Feature Flags Quickstart

This is the feature-flag path through A vs B, start to finish. By the end you will have a flag in the dashboard, an SDK reading it from your own application, and a value you can change without deploying.

It takes about twenty minutes, and most of that is the install.

Two products, two paths

A vs B does web experiments (a snippet on your website) and feature flags (an SDK in your code). They share the same audiences, metrics, and statistics, but they start differently. If you want to A/B test a page on your website without touching your codebase, follow the web experiment path instead. Nothing stops you doing both: they are separate projects in the same organization.

What you need

  • An A vs B account and an organization. Both take a couple of minutes, and they are the same for either path.
  • An application you can add an npm package to. JavaScript or TypeScript for this guide, on the browser or on the server.
  • Somewhere to keep an environment variable. The SDK key goes there, not in a committed file.

Follow these in order

Each page picks up where the previous one stops.

What the dashboard tracks for you

Your project dashboard carries a short getting-started checklist covering these same steps. It ticks each one off from your own data, not from a box you check: "Connect an SDK" turns green when a real SDK checks in, and "Publish your changes" turns green when a real publish happens. It disappears when you finish, and you can hide it any time.

Was this helpful?