Products
Solutions
Resources
Even though the end of summer is flying by, we still shipped a lot of new features in August. I want to check in on both what we shipped and why we shipped it.
Our main goal in August was to continue to make Statsig work better for you, however you want to use it. The three big themes within that goal were scaling cross-platform control, building out more AI capabilities, and tackling customer ease-of-use requests.
Scaling cross-platform control
Whether you use Statsig via the console, the API, the CLI, or with integrated tools, we want to make sure you can trust your experiment results and release metrics. “Have it your way” isn’t just the slogan for my third-favorite burger joint.
PagerDuty integration lets Statsig Topline Alerts page PagerDuty directly to detect problems faster
API: Pull daily experiment checks for better visibility and delete single feature gate user overrides without having to mutate the full list locally
SCIM Role Aliases can now match custom IdP naming conventions without having to rename anything in your IdP
Warehouse-native: Cost attribution tags on Statsig queries help you better evaluate compute costs, and Athena projects now get full pipeline visibility out of the box
AI mode
We believe that AI implemented correctly can help teams ship faster, and building out Statsig’s AI capabilities is a top priority. With MCP use steadily increasing, it’s clear you think this is a priority too.
August saw five new fields added to MCP experiment configuration. If you want to create or update an experiment from your coding agent, you can now modify secondaryIDType, identifierMappingMode, enabledNonProdEnvironments, links, and secondaryMetrics, no console required.
Ease of use: You asked, we built it
You’re the experts at using Statsig, and you know (often better than us) what would make it easier to use. That’s why we prioritize improvements from your requests.
This month, we focused on requests for Experiment and Feature Gate creation modals.
Layers are now a top-level targeting option for experiments, making it easier to keep tests mutually exclusive and prevent cross-contamination
Targeting multiselect is expanded to better manage as many targeting values as you need
Display names can be shared across gates, experiments, and configs, so you don’t run into “ID already in use” as often
As always, if you have other requests, let us know!
The next episode
It’s been a packed summer expanding the foundational pillars of our platform and building out feature requests.
Looking forward, we’ve got even more to come. We have a couple of big releases in the next two months, and we're making continued progress toward a combined, AI-powered behavioral and validation stack with Amplitude and Statsig.
We’re excited to show you what’s up soon.