Product Updates

🚢 Custom Experiment Decision Framework

We’ve expanded the Decision Framework feature beyond templates.

Now, you can directly configure and manage decision frameworks for each experiment. This gives teams a place to codify decision-making so that users can quickly move to action at the conclusion of an experiment.

To add a decision framework to your experiment select “Add Decision Framework” from the experiment menu.

Personal Console API Keys

You can now generate personal Console API keys in Statsig. These keys are automatically scoped to your role, ensuring the same access restrictions you already have. Each key is tied to its owner, making it easier to track usage and maintain clean audit logs.

Why it matters:

• Simplifies multi-user projects by giving every user their own key

• Provides clear ownership visibility for better security and compliance

• Admins can control the ability to generate personal keys in the organization settings

Dynamic Configs Archive and Unarchive API Endpoints

We've added two more endpoints to our Console API for Dynamic Configs. Now you can archive and unarchive a Dynamic Config in your project programmatically!

Access the endpoints here: https://docs.statsig.com/console-api/dynamic_configs

🧪 Sampling Across All Charts

You can now enable sampling in all major chart types to speed up queries on large datasets—while still getting directionally accurate results.

What You Can Do Now

• Use user-level sampling in Funnel, Distribution, Retention, and User Journey charts

• Use event-level sampling in Metric Drilldown

• Toggle sampling on or off in chart settings

• See when sampling is active, and disable it at any time for exact results

How It Works

Sampling is off by default. When toggled on, it only applies under high-volume conditions:

• Warehouse Native: Sampling applies if metric sources exceed 100K rows/day or row counts can’t be determined. For User Journeys, sampling is always applied when toggled on.

• Cloud: Sampling applies if the event volume in the query exceeds 100K. For Journeys, we look at total event volume across the company.

In Drilldown, event-level sampling is used for high-volume events unless the variance is too high, in which case we fall back to full data.

Impact on Your Analysis

Sampling helps you move faster through exploratory workflows. In early results, User Journey query times dropped by over 60% when sampling was applied.

It’s a small precision tradeoff for a much faster iteration loop.

🧪 Analyze Exposures in Metrics Explorer (Warehouse Native)

Experiment exposure events are now supported in Metrics Explorer on Warehouse Native. You can select them like any other event, filter or group by properties (variant, metadata), and tie rollout data directly to product metrics.

More details here: Exposures in Metrics Explorer

✅ Verified Cohorts and Dashboards

Admins can now mark specific cohorts and dashboards as verified. This signals that they are the trusted, official versions while also protecting them from accidental edits.

What You Can Do Now

• Mark cohorts and dashboards as verified to indicate they are the approved versions

• Prevent edits to verified entities unless you are an admin

• Clone verified cohorts and dashboards to create your own editable versions

How It Works

• Cohorts: Mark as verified when creating a new cohort or by editing an existing one

• Dashboards: Mark as verified from the settings cog in the top right of the dashboard page

Impact on Your Analysis

Teams can align on a single source of truth for key cohorts and dashboards while still allowing individuals to explore their own versions without risking changes to the verified originals.

This keeps shared analysis reliable and consistent.

Pre-Post Results on Feature Gates

This feature is currently available only on Statsig Cloud and is not yet supported on Warehouse Native.

Sometimes, you don’t have the luxury of launching a feature partially to your user population (e,g, X% of the users). Maybe you had to ship something immediately, rolled out a backend improvement to all users, or made a change you can’t ethically hold back from part of your audience. That’s where Pre-Post Results comes in.

With Pre-Post Results, you can:

• Compare metrics before and after a feature reaches 100% rollout

• See the directional impact on key outcomes, even without a control group

✨ How it works

Statsig automatically detects when a feature gate has been rolled out to all users (0 → 100% or started at 100% in the last 30 days). It then compares the same users’ behavior before and after rollout, showing you whether your feature moved the needle. To read more about our computational methodology, read Statsig Docs.

🥾Easier Bootstrapping in React Apps

Bootstrapping generates the values for a Statsig client SDK on a server that you manage - most commonly on your web server, so that you don’t have to make an extra network request for the SDK to be ready.

This means the Statsig SDK will be ready immediately, making your page more responsive and supporting metrics like your Core Web Vitals, and in turn your SEO.

Historically - Bootstrapping was tricky to setup in React, requiring a couple different server and client-side functions. We’ve now introduced the StatsigBootstrapProvider, which hides all of the necessary plumbing inside a server-side component so you can add a single component in your Layout.tsx to set everything up.

We're starting with support for Next.js apps, checkout the docs to get started!

📈 Velocity Dashboard

Introducing the Velocity Dashboard, your new source of truth for understanding how fast your team is shipping. Built to bring visibility and alignment, this dashboard helps you track experiments and gates shipped over time, making it easier to highlight progress, spot trends, and share impact across your organization.

Highlights

• Unified view of experiment and gate velocity across teams

• Filter & group by team, tag, or status to focus on what matters

• Long-term trends at a glance — perfect for quarterly reviews

• Export to PDF for reporting, decks, or sharing with stakeholders

Available Now

Click on Dashboards → Velocity Dashboard to get started, or from the homepage widget.

📌 Default Dashboard Filters

You can now pin filters directly to dashboards, making it easier to analyze different views of your data without rebuilding filters from scratch.

What You Can Do Now

• Pin commonly used filters (e.g. “Company Name”) to any dashboard

• Quickly swap values to see how different users, cohorts, or properties impact the same set of charts

• Use pinned filters as a starting point for scoped analysis

How It Works

From any dashboard, go to dashboard settings and configure "default filters". The pinned filter will appear at the top of the dashboard and apply across all charts. When you change the value (e.g. from Company A to Company B), the charts update automatically with no need to reconfigure each one.

Impact on Your Analysis

This makes it faster to compare trends across dimensions like company, region, or platform. Instead of duplicating dashboards or editing individual filters, you can reuse the same dashboard with dynamic, scoped filtering.

Great for teams who want to keep a consistent dashboard layout while comparing key segments.