Commonly Used Features on Statsig for Enterprise Customers
Single Sign On (SSO)
⚠️ Security risk if not enabled
If you’ve not enabled SSO on Statsig, your ex-employees will be able to make changes in your Statsig project, unless you remember to deactivate them in Statsig. Using SSO makes sure they cannot access Statsig when you remove their user account from your systems (by forcing them to authenticate with your systems frequently). See moreRequire Change Review
⚠️ Production systems at risk if not enabled
Like with changes to your source code or production configuration, requiring a second pair of eyes to review changes in Statsig helps reduces mistakes in production. When enabled, changes impacting only pre-production environments do not require approval - allowing agility there. You can grant admins or oncalls the ability to self-approve changes if desired.
Tags for organization
Tags let you apply light-weight organization to your Statsig config (e.g. gates, experiments and metrics) to allow easy filtering by team (or organization objectives). E.g. You can tag growth related experiments and metrics with a tag called “Growth”, easily filtering down to just these when needed. This is particularly useful with metrics - since you can now just add the Growth tag to your scorecard metrics, and pull in all the key Growth metrics instead of individually picking them. The Core tag is meant to be used for company critical metrics. These are defaulted into experiment scorecards so experimenters are looking at impact on these metrics as part of their experiments.
Metric and User Properties
Metric properties let you break out an event such as add-to-cart into product categories such as sports, toys, appliances, electronics. To do this, you would simply log add-to-cart events and provide the product category in the event’s value field. See more
Slack Notifs
Statsig supports two classes of Slack Notifications - Project and Personal. Project Notifications will drop into a Slack channel you choose updates including Configuration changes (User1 rolled out Feature1 to 100% of Everyone), Health Check Alerts (Experiment1 is failing Sample Ratio Mismatch checks) and Statsig Health Status Reports (also posted to https://status.statsig.com).
Discussions
Feature rollout and experimentation are collaborative exercises where teams work together. Often this collaboration requires people taking screenshots, looking at metrics and DMing team mates to ask them questions. This information is siloed and lost to others. In-context Discussions allow teams to discuss aspects of the feature rollout or experiment while making this context available to other team members. Common reasons include discussing a surprising metric lift, asking questions on validation performed before ramping up a feature rollout or even keeping a running log of observations/escalations that can be referenced when the experiment is complete.
Users tab
The users tab is a powerful diagnostics tool for developers trying to troubleshoot or validate experiments. It can answer questions like “which experiment group was this user in?” or “when did the user first see this feature?”. See more.