Skip to main content

Getting Started

Statsig is the world’s most advanced experimentation platform. It enables your entire company to run experiments collaboratively and quickly, with minimal engineering effort.

There are two ways to seamlessly integrate Statsig into your product development:

  • Statsig Cloud: Set up Statsig SDK, configure events logging. Everything else is handled by us.
    • You get feature gates and 1 million metered events for free, as well as many analytics tools such as Dashboard, Metrics Explorer, and Insights. Here is a link to our pricing details.
  • Warehouse Native: If you have data instruments already, or a strong privacy requirement, you may want to consider Warehouse Native (WHN). With WHN, you can host Statsig’s Stats Engine within your own Data Warehouse, using your own pre-existing data sets to calculate metric lifts. You can define feature assignment either by providing us feature exposures (you randomize), or through our SDK (we randomize).
    • Today’s this option is only available for Enterprise contracts. Check this link for more details or Schedule a demo with our sales if you are interested in this option.
    • With WHN, we still recommend using Statsig SDK for feature gates, and randomization, and take advantage of its reliable infrastructure, and seamless integration with the Statsig Console.

This page gives you an organized overview of how to set up the SDK. SDK can help you log events, and assignments, which will light up feature gate, experiments, and analytics within half an hour.

Overview: What is Statsig, and what is needed to set it up?

Statsig provides three tightly-integrated core capabilities:

  1. Experimentation: Run AB tests with minimal engineering efforts (two lines of code), and make decisions as a team with a powerful and intuitive Console.
  2. Feature Gating: Decouple code deployment and feature deployment, giving you full control of your users’ experiences, including the ability to rollout or rollback features in a single click.
  3. User Analytics: Dashboards, charts, funnels, retention; from logged events to all sorts of business metrics.

Statsig helps you generate two core outputs — metrics and exposures — metrics summarizes user behaviors that are meaningful to your business; exposure tells us, and allows us to control, what features each user is exposed to.

Logging Events is the foundation for metrics, and Feature assignment is the foundation for exposuress. Statsig has best-in-class SDKs built with experimentation as a first-class citizen, that once turned on, can create logging events and feature assignments to power all Statsig features. The SDK is strongly recommended for as it’s reliable, resilient, and have many experimentation best practices built in.

You can use Statsig without its SDK. For example, metrics can come from raw events table, metric definitions, or a precomputed metrics table; assignments can come from 3rd party tool, or in-house assignment tool. Statsig is modulated to work with other tools you are currently using.

Now, let’s walk through how to use Statsig SDK to turn on events logging.

Three Steps to Turn on Statsig Cloud

Step 1. Integrate with our SDK

We also provide an HTTP API. Our API is a great choice if an SDK isn't available for your environment yet, as you can use it in any type of application:

Step 2. Set Up Your First Feature Gate

Check this page for a full walkthrough


Step 3. Start Logging Events

Check this page for a full walkthrough



Now, events are logged and passed to Statsig Cloud via the SDK. They will start being computed as metrics in your Metrics Catalog:


Which you can add to a Dashboard:


Or even start trying to optimize via Experiments:


Need more help?

Statsig strives to provide the best support possible. You can

Walkthrough Guides

Your First Feature

Let's build a new feature with Feature Gates, targeting and rollout.

Your First A/B Test

Running an A/B experiment should not be difficult. Let's set one up in minutes.

Logging Events

Useful product metrics are computed from discrete events that you log. Let's get started on logging events.

Your first Holdout

Sometimes it helps to measure cumulative impact of a set of features. Let's set up a Holdout to do that.

Making Code Dynamic

You don't always have to ship new code for customizing your experience, or even shipping new features. Let's learn about dynamic configs.

Statsig in Your Warehouse

You can calculate experiment results on existing data in your warehouse. Let's explore Statsig Warehouse Native.


Feature Gates

Control access to new functionality and automatically measure how it’s performing with an A/B test before you ship

Dynamic Configs

Dynamically configure user experience with configuration parameters instead of hard-coded constants


Define a reusable set of rules to target a group of users


Run sophisticated experiments with multiple variants (A/B/n tests) or mutual exclusion


Automatically optimize for a single metric by testing a number of variants


View metrics automatically derived from all gate checks and events logged with Statsig


View users exposed to all gate checks and events logged with Statsig


View how your experiments impact your metrics


View all experiments that have impacted a metric


Measure the cumulative impact of all features shipped over a period of time

Filing bugs

You can file bug reports or feature requests via github issues in our Statsig Feedback repository