As adoption of feature flags has spread, product teams have learned to release new features incrementally, exposing new functionality slowly to the user base with a careful eye towards ensuring the right customer experience. Measuring the impact of a new feature on the customer experience has traditionally been a manual process– information had to be gathered by the business, and data science teams sifted through the data to correlate results. Thankfully, feature flags have come into the picture, and they have made automating the process much easier.
Several automated tools have sprung up across the ecosystem to more rapidly measure the feature impact– New Relic, Datadog, Pendo, and FullStory, to name a few. As the number of customer touchpoints increases in the digital world, the number of unique tools needed to understand the entirety of the experience has ballooned.
Enter Segment, a single tool to capture data from every customer touch point. Segment sends the consolidated customer data to analytics, marketing, or data warehousing tools to personalize campaigns, analyze product usage, and more. If you’re one of the 15,000+ Segment customers, we don’t need to tell you they have a great product.
As featured in the video below, Segment has over 200 source and destination integrations, and we are happy to announce Segment can both send and receive data from Split. This integration takes full advantage of Segment’s functionality, providing a robust and flexible solution that meets the unique data formats and tracking methodologies of each product.
Split as a destination and a source for Segment
As the platform powering your product decisions, we recognize the importance of easily sending and receiving data from other tools in your data pipeline. With the Segment integration, you’ll spend less time managing data and more time improving your product experience.
Split can be both a data destination and a source for Segment. As a destination, Split supports the identify, group, track, page, and screen specs from Segment. As a source, data will flow from Split into Segment as a track type with the event name get_treatment.
Split as a destination
- Pull User IDs or Anonymous IDs from Segment into the Split console to pre-populate the Split web console for easier targeting and feature management.
- Capture user events tracked in Segment, then conduct statistical analysis using our experimentation engine. Define metrics within Split and apply to Segment’s user events to measure the impact of new features on customer experience.
Learn more about identifying customers in Split.
Learn more about Split events.
Split as a source
Split will send traffic impression data from your splits to Segment. Split records any actions your users perform, along with any properties that describe that action.
Locate and install the Segment integration
Locate the Segment integration on the “Integrations” tab under your Admin settings. Additional setup instructions are in our documentation.
If you’re new to Split, get a free trial to learn more about how you can use your data already in Segment for feature flags, feature management, and feature experimentation.
Stay up to date
Don’t miss out! Subscribe to our digest to get the latest about feature flags, continuous delivery, experimentation, and more.
At Split we believe in the power of metrics, and are always striving to improve the ways we help our users make more data-driven product decisions. In this previous post we talked about the importance of understanding the impact of a new feature release via key and guardrail metrics. With…
When we speak to our customers, one of the most common reasons they say they made the move towards feature flags was the need to make sure their releases didn’t cause more errors for their users. By leveraging feature flags to ramp the release of their features to just small…
Find faulty features before your customers do One of the most common reasons, our customers tell us, for moving towards feature flags is risk mitigation: the need to make sure releases don’t cause errors for users. Given how frequently organizations are now deploying features, the ability to limit the blast…