KNOW WHAT YOUR STATSIG EXPERIMENTS ACTUALLY PROVED.
Connect Statsig to Menza and get straight answers on your feature gates, experiments, configs and metrics — which tests moved the numbers, which gates have gone stale, who a config actually reaches. Menza reads it live through the official Statsig API, and when you approve a change, it makes it for you.
- Reads analytics data
- Can take action on Statsig, once you approve
- Connects via the official API
What can Menza do with Statsig?
Tidy stale gates before they bite
Menza finds feature gates sitting at full rollout for months, proposes disabling the ones nothing depends on, and — once you approve — cleans them up, so your gate list stays honest.
Get a straight read on experiments
Ask which experiments actually moved your metrics and Menza reads results live, separating real lifts from noise, so ship decisions rest on numbers rather than optimism.
See who a config really reaches
Question any dynamic config or segment and Menza traces which users and events it touches, so you know exactly what changes before you change it.
See these answers on your own Statsig data.
Menza working with Statsig.
Menza doesn't just answer questions about Statsig — it proposes the fix and, once you approve, does the work. You stay in control; nothing changes until you say go.
Menzajust nowFourteen feature gates have been at full rollout for over 120 days and are still evaluated on every request. I'll disable the six gates with no active overrides and leave the other eight flagged for their owners.
Menza6m agoYour checkout experiment has run 38 days and the primary metric sits at +0.3% — well inside noise. I'll stop the experiment and ship the control config so traffic stops splitting.
Connect Statsig in a couple of clicks.
Is my Statsig data secure?
Your credentials are encrypted at rest and never exposed to the AI. Menza reads your data through the provider's official API using the access you grant, and you stay in control of what it can do — read-only by default, with any actions gated behind your approval.
Read our privacy policy- Encrypted in transit and at rest
- Scoped access — you choose what Menza can see
- Read-only by default; any action needs your approval
- Credentials are encrypted and never shown to the AI
- Revoke access at any time
Statsig questions, answered.
How does Menza connect to Statsig?
You connect with your Statsig console API key. It's encrypted at rest, used only to call the official Statsig API, and never shown to the AI. Once connected, Menza answers on your live gates, experiments and metrics — no CSV exports, no waiting.
What can Menza answer about my Statsig data?
Anything Statsig holds: feature gates, experiments, dynamic configs, segments, metrics and events. Ask which experiments concluded with a real effect, which gates are fully rolled out but still evaluated, or how a metric trended across the last three tests that touched it.
Is my Statsig data safe with Menza?
Your API key is encrypted and never exposed to the AI, and Menza only reaches what the key grants. Reads happen freely; any change — toggling a gate, stopping an experiment — is proposed first and waits for your explicit approval before Menza touches anything.
Can Menza tell me when an experiment has run long enough?
Yes. Ask about any live experiment and Menza reads its duration, exposure counts and metric movement, then tells you whether the result is still inside noise. If it's done, Menza can propose stopping it — the stop only happens once you approve.