Statsig can now be configured as a Destination within Segment to automatically ingest any of your Segment events. This allows you to bootstrap your Statsig environment easily, as all of the events you’ve been logging to Segment will start showing up in your Statsig experiments with no additional work.
In your Segment console, click Add New Destination and search and add the Statsig Destination.
From here, follow the steps and configure your Destination with your preferences and providing your Statsig Server Secret. After that, go to your Statsig console and enable the Segment integration.
Once you’ve completed these steps, your Segment data will start arriving in Statsig! For more instructions follow the steps in our documentation.
For any current and future experiments run on Statsig, Statsig be able to provide comparisons for how your Segment events are affected by the test and control groups. This enables you to get a complete view of how the features you’re building and testing are affecting your ecosystem based on the metrics you’ve already logged.
Your events will arrive in Statsig in real-time, allowing you to dive in and gather insights from your metrics by exploring historical trends or observing correlations between features you shipped and changes in event volumes.
Find which features and experiments are causing the greatest positive or negative lifts in your Segment metrics with Ultrasound and identify which features to double-down on and which should be reconsidered.
Sign up and start using Statsig here and start getting more value from your Segment events!
Experimenting with query-level optimizations at Statsig: How we reduced latency by testing temp tables vs. CTEs in Metrics Explorer. Read More ⇾
Find out how we scaled our data platform to handle hundreds of petabytes of data per day, and our specific solutions to the obstacles we've faced while scaling. Read More ⇾
The debate between Bayesian and frequentist statistics sounds like a fundamental clash, but it's more about how we talk about uncertainty than the actual decisions we make. Read More ⇾
Building a scalable experimentation platform means balancing cost, performance, and flexibility. Here’s how we designed an elastic, efficient, and powerful system. Read More ⇾
Here's how we optimized store cloning, cut processing time from 500ms to 2ms, and engineered FastCloneMap for blazing-fast entity updates. Read More ⇾
It's one thing to have a really great and functional product. It's another thing to have a product that feels good to use. Read More ⇾