Commonly Used Features on Statsig for Enterprise Customers
How to use Statsig's FOMO feature to share project updates, experiment wins, and rollout activity with your team in a curated weekly digest format.
Single sign on (SSO)
⚠️ Security risk if not enabled
Without SSO enabled on Statsig, former employees retain access to your Statsig project unless you manually deactivate them. Enabling SSO ensures former employees lose access when you remove their account from your identity provider. Refer to the SSO overview.Require change review
⚠️ Production systems at risk if not enabled
Requiring a reviewer for Statsig changes reduces production mistakes, the same way code review does for source code. When enabled, changes that affect only pre-production environments don't require approval. You can grant admins or on-call staff the ability to self-approve changes. 

Tags for organization
Tags let you organize Statsig configuration items (gates, experiments, and metrics) so you can filter by team or objective. For example, tag growth-related experiments and metrics with "Growth" and filter to them when needed. Tags are especially useful for metrics: add the Growth tag to your scorecard metrics to pull in all Growth metrics at once instead of selecting them individually.
The Core tag is for company-critical metrics. Statsig includes these metrics in experiment scorecards by default so that experimenters always see the impact on critical metrics. 
Metric and user properties
Metric properties let you break out an event such as add-to-cart into product categories like sports, toys, appliances, and electronics. Log add-to-cart events and provide the product category in the event's value field. Refer to metric dimensions
User properties let you slice or filter metrics based on a user property. This is often something like Country, Device Type or a property like Free vs Paid. On Statsig Cloud, Statsig freezes these when a user is first exposed to a feature gate or experiment - in case your experiment ends up changing these properties (e.g. convert a Free user to Paid). If you're using Statsig Warehouse Native, you can set these properties anytime before analysis. 
Slack notifications
Statsig supports two classes of Slack Notifications: Project and Personal. Project Notifications post to a Slack channel you choose, 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).
Individuals can opt into Personal Notifications to receive notifications when tagged in discussions, invited to review a change, or when an experiment they follow changes. 
Discussions
Feature rollout and experimentation are collaborative. Teams often take screenshots, review metrics, and message teammates to ask questions, but this information is siloed and lost to others. In-context Discussions let teams discuss aspects of a feature rollout or experiment while keeping that context available to all team members. Common uses include discussing a surprising metric lift, asking questions about validation before ramping up a rollout, or keeping a running log of observations you can reference when the experiment is complete.

Users tab
The users tab is a diagnostics tool for developers troubleshooting or validating experiments. It answers questions such as "which experiment group was this user in?" or "when did the user first see this feature?". Refer to Users for more details.
Dynamic Config
Dynamic config replaces hard-coded values in your application with configuration parameters defined on the server. These parameters can include any property across client-side or server-side code, from button colors to ranking configurations. This lets you control application behavior dynamically in near real-time. Refer to Dynamic Config for more details.Holdouts
Holdouts are an advanced feature that supports experimentation program maturity. They let you measure the cumulative impact of feature releases and whether wins are sustained. Refer to the Holdouts blog post for more details.Was this helpful?