Split Testing in SessionSight runs server-driven variation tests with traffic weighting, goal tracking, and automatic winner detection, so you know what wins before you commit to it.
Every test you've run, still running, or waiting to ship
Split tests live next to feature flags and reuse the same value types: ID (route to a different component), TEXT (swap a headline), or JSON (reconfigure a whole section). Everything server-driven, so there's no client-side flicker.
Split Testing
Run server-driven variation tests to optimize conversions
Define variations once, let the server handle routing
Each variation gets a key, a human-readable name, a weight for traffic distribution, and a value that matches the test type. Boolean, number, text, JSON, or an ID for component-level experiments. All values land in the same SDK call as your feature flags.
Variations
Define the variations visitors will see.
Pick the outcomes you're optimizing for
Goals pulled from your goal library
Select any goal you've defined and it becomes a conversion metric for the test. One gets marked Primary; the rest become secondary metrics, measured in parallel so you know whether a win on signup came at the cost of revenue.
Goals
Select goals to track conversions for this test.
Ramp it up, ramp it down
Traffic Allocation controls what percentage of eligible visitors join the test. Start at 20% for a safe read, move to 100% when the numbers hold. Change it live without redeploying.
Traffic Allocation
Percentage of eligible visitors included in this test.
Stop debating the headline,
ship them both
Server-driven split tests let you run variations in production without redeploys or client-side flicker.
Start your first test