You can now create, edit, and analyze more dashboard charts through the Console API and the Statsig MCP.
Work with line, bar, pie, table, number, and geo-map charts alongside funnels
Use catalog metrics like WAU and formulas in your charts
Edit individual widgets without touching the rest of the dashboard
Rely on safeguards against accidental deletion and conflicting updates
Dashboards can now be built and maintained programmatically beyond funnels, so your scripts and agents can cover the charts your team actually uses, with protections against overwriting each other’s changes.
If you have the Statsig MCP set up, try a prompt like:
“Using the Statsig MCP, create a dashboard with a line chart of WAU.”
Learn more in the Dashboard API docs.
Admins can now connect Claude to Statsig once for the whole organization.
Let members use Statsig in Claude without individual OAuth prompts or personal API keys
Keep access tied to each member’s existing Statsig permissions, with admin controls for read-only or read and write access
Choose between Claude-issued identity and Okta / OIDC Cross App Access
Set it up in any Statsig organization. An organization admin configures and enables it
Rolling out the MCP across a company shouldn’t mean every person authorizing separately or managing a personal key. Now one admin setup covers the organization, and permissions still follow each member.
Follow the Enterprise-managed authorization setup guide.
Teams using Statsig Warehouse-Native can now see what is running in their warehouse and adjust schedules in one click.
Use the new Pipeline Activity page to see the jobs that have run in your warehouse and how long they ran
Open the details behind any job in one click, including the DAG and the SQL that will run
See every experiment and gate schedule on the data connection reload settings page, and edit any of them in one click
Two questions come up constantly, “What’s running in my warehouse?” and “Why is this experiment taking so long to refresh?” Now you can answer both yourself and tune schedules to reduce warehouse load.
Open Data → Pipeline Activity in the Statsig Console. To edit schedules, open your data connection’s reload settings.
Learn more in the Pipeline Activity docs.
Statsig Warehouse Native can creates far fewer tables for pre-computed user dimensions, with the same results.
Get 60 to 80% fewer PCUD-related tables for a standard 4-dimension setup, with larger savings as you add dimensions
Keep healthy dimensions computing when the source for one dimension is missing
Spend less on table creation and S3 / catalog management on Athena
Separate pipelines for each dimension meant table counts grew quickly. Now one combined path keeps your warehouse cleaner, and one failing dimension no longer blocks the rest.
Learn more in the Slicing by User Properties docs.
You can now schedule when a Cloud or Warehouse Native assign-and-analyze experiment stops.
Choose Stop New Assignments or Conclude & Defer Decision. At the scheduled time, Console runs the same action as clicking it by hand
Set a date and time up to a year out
Edit or cancel from the experiment header
Save a scheduled start and stop together as one request
Stopping an experiment at a specific moment used to mean someone had to be at the keyboard. Now you can set it and leave it.
To request early access, contact your Statsig account team.
A new Report tab turns experiment results into a shareable readout.
Generate an experiment report with AI analysis and key metric cards
Edit and reorder sections, and add your own context
Export the report as a PDF
Teams spend real time assembling numbers and writing the narrative after an experiment ends. Now you start from a generated draft and edit it.
To request early access, contact your Statsig account team.
Planning an experiment is now one connected workflow in Cloud and Warehouse Native.
Configure a population and metrics, run an analysis, and compare MDE, duration, and allocation tradeoffs
Review results in a Scenario Matrix, Week-by-Week view, and Advanced Statistics
Save settings, rerun or duplicate an analysis, and attach it to an experiment
Find past analyses on their own report pages, restore reports, and get completion notifications
Estimated duration is now the direct answer, so PMs and non-data-scientists can complete the calculator and trust what it tells them.
Go to Console → Experimentation → Power Analysis.
Dashboards can now focus on the experiments that are running right now.
Choose Add Filter → Experiment Status on any dashboard, including dashboards generated automatically from tags
Share the filtered view by URL, or save your selection as the dashboard’s default filter
Experiment widgets that don’t match the filter are dimmed in place, so your layout stays intact
Experiment overview dashboards get cluttered as tests start and finish. Now you can keep the view focused on running experiments without removing widgets by hand.
Open any dashboard, choose Add Filter, and select Experiment Status.
You can now verify a proposed gate or dynamic config change inside the review modal before you submit it for approval.
Toggle a preview with Visual and Diff views, and filter between Changes and All Rules
See compact comparisons that highlight the changed fields when requesting a review for rule changes
Find reviewers faster with a searchable selector for Teams and Individuals, with checkboxes and removable pills
Get a prompt in the review flow to turn on Slack notifications for reviews
Reviewers can only approve what they can clearly see. Now you can check exactly what you are proposing before you send it, which means fewer review rounds spent on mistakes you could have caught yourself.
Request a review on a gate or dynamic config rule change and open the preview in the review modal.
You can now see when a warehouse export fails and why, without guessing or contacting support.
Get a failure notification email when an export fails
See the error message in the UI so you understand why an export failed
Query export success and failure status programmatically with the new list-warehouse-export-status endpoint
Ask the Statsig MCP to help you understand an export failure
A failed export used to be easy to miss and hard to diagnose. Now you hear about failures right away and can see the cause, in the UI, over the API, or through your AI tooling.
Learn more in the Warehouse Exports docs and the export status API reference.
Keep an eye on your inbox for the latest Statsig product updates.