Why Winback and Onboarding Experiments Should Never Share the Same Test
·Experiment design

Winback experiments and onboarding experiments should always run as separate tests because they target fundamentally different user populations with opposing mental states and conversion mechanics. A churned user evaluating whether to return has completely different decision criteria than a new user experiencing your product for the first time, making any combined measurement meaningless.
Combining these populations into a single experiment creates statistical noise that masks true treatment effects. Onboarding optimizes for first-time activation and initial value delivery, while winback focuses on re-engagement triggers and addressing previous friction points. The conversion timelines, baseline rates, and success metrics differ so dramatically that pooling them produces unreliable results that can't inform either strategy effectively.
Different user contexts require different hypotheses
New users arrive with curiosity and minimal product knowledge. They need clarity about core features, quick wins, and a clear path to their first meaningful outcome. Their decisions center on whether your app solves their immediate problem and whether the learning curve feels manageable. Onboarding experiments test messaging hierarchy, feature introduction sequences, and friction reduction in the initial setup flow.
Churned users return with baggage—previous disappointment, unmet expectations, or a problem that drove them away. They already understand your product but need a reason to believe things have changed or that they missed something valuable. Winback experiments test new feature announcements, pricing adjustments, personalized incentives, or messaging that directly addresses known churn reasons. These are fundamentally incompatible experimental contexts.
Conversion windows operate on completely different timescales
Onboarding conversion typically happens within the first session or first few days. You measure whether users complete setup steps, reach activation milestones, and convert to paid within a tight window—often 3 to 7 days for subscription apps. The user journey is compressed and sequential, with clear stage gates that indicate progress toward subscription.
Winback conversion extends across weeks or months. A churned user might see your campaign, ignore it, then convert weeks later when their original need resurfaces. The decision process is non-linear, influenced by external triggers unrelated to your messaging. Applying onboarding conversion windows to winback traffic produces false negatives, while extending windows for onboarding masks critical early-stage friction that kills conversion before users experience value.
Baseline conversion rates make combined tests statistically invalid
New user conversion rates typically range from 2% to 15% for trial starts, depending on your product and traffic quality. This baseline is your control against which you measure improvements. Any variant that moves this needle by even 10-20% relative represents a meaningful win worth validating and scaling.
Winback conversion rates often run 5-10x lower than onboarding rates because churned users have already rejected your product once. Mixing a 10% onboarding baseline with a 1% winback baseline into one test means the larger population dominates your results. A variant that doubles winback conversion from 1% to 2% gets buried under noise from the onboarding population, causing you to miss a genuinely successful treatment for your churned segment.
Treatment effects point in opposite directions
Effective onboarding reduces friction and defers complexity. You hide advanced features, streamline required inputs, and create a simplified path to one core outcome. The best onboarding variants often remove options and decision points, trading feature exposure for higher completion rates. Messages emphasize ease, speed, and immediate gratification.
Effective winback often adds information and acknowledges complexity. You need to surface what's new, demonstrate evolution, or explain how you've addressed previous limitations. Successful winback variants frequently include more detailed messaging, personalized feature callouts based on previous usage, or incentives that acknowledge past dissatisfaction. Testing messaging that works for one population actively harms performance in the other, creating false negatives for genuinely good ideas.
How to structure separate experiments correctly
Create distinct audience segments before launching any experiment. Tag users as new, active, or churned based on clear definitions—for example, churned means no session in 30+ days after previous subscription. Route each segment to appropriate experiment pools that never overlap. Your onboarding experiment only enrolls users in their first session; your winback experiment only enrolls previously active users returning after your churn threshold.
Platforms like Spinosis that assign sticky variants and allow traffic shifting make this segmentation straightforward through user ID matching and event attribution. You can run simultaneous experiments for each population, analyze them independently, and shift traffic to winning variants within each segment without cross-contamination. This structure lets you optimize both funnels aggressively while maintaining clean measurement and the ability to roll back treatments that underperform for their specific audience.
Questions
Can I test the same creative assets across both onboarding and winback audiences?
Yes, but only as separate experiments with different success metrics. The same image or headline might perform differently for new versus returning users, so you need isolated tests to measure each population's response. Run parallel experiments with identical variants but separate traffic pools, then analyze results independently. You may discover that messaging resonating with churned users confuses new users, or vice versa.
What if my sample size is too small to run separate experiments?
Prioritize the larger or more valuable population first. For most subscription apps, onboarding represents higher volume and greater lifetime impact, so optimize there initially. Once you've established a winning onboarding flow, shift focus to winback when you've accumulated enough churned users for statistical power. Running one good experiment sequentially beats running one bad experiment on mixed populations that produces unreliable results for both groups.
Should I use different conversion metrics for onboarding versus winback tests?
Absolutely. Onboarding experiments typically measure trial starts, feature activation, or day-7 retention as primary metrics. Winback experiments should track re-engagement actions like session starts, subscription reactivation, or 30-day retention among previously churned users. The time windows, baseline expectations, and business value differ enough that using identical metrics obscures what's actually working. Define success criteria that match each population's position in the user lifecycle.
Turn on auto-optimize for one test.
Create a project, install the SDK, connect RevenueCat. Traffic starts shifting on its own.