Back to blog
Growth6 min

A/B testing links: our internal playbook for running experiments

How the getowl team tests link destinations, landing pages, and CTAs across different traffic segments. Includes the exact split ratios we use.

getowl Team·Growth & Product
March 24, 2026

At getowl, we A/B test everything — including our own links. Here's the exact playbook we use internally and recommend to our customers.

When to A/B Test Links

  • New landing page designs — Test before committing to a full rollout
  • CTA variations — Different button copy, colors, or placement
  • Pricing page variants — Test different pricing presentations
  • Headline testing — Which value proposition resonates most?
  • Signup flow — Short form vs. long form, social login vs. email

Our Split Ratio Framework

Phase 1: Discovery (Days 1-3)

  • 50/50 split between two variants
  • Minimum 500 clicks per variant for statistical significance
  • Monitor: click-through rate, bounce rate, time on page

Phase 2: Validation (Days 4-7)

  • Shift to 70/30 favoring the leading variant
  • Continue monitoring conversion metrics (not just clicks)
  • Look for consistency across devices and geos

Phase 3: Confirmation (Days 8-10)

  • Shift to 90/10 on the winner
  • The 10% ensures you catch any regression
  • If metrics hold, go to 100%

Phase 4: Rollout

  • Set to 100% on the winner
  • Document results and insights
  • Archive the test for future reference

How to Set Up in getowl

  1. Create a link with your primary destination
  2. Click Add A/B Variant
  3. Enter the variant URL and set the traffic percentage
  4. Save and share the link
  5. Monitor results in the link analytics dashboard

Common Mistakes

  1. Testing too many variants at once — Stick to 2-3 max
  2. Calling tests too early — Wait for statistical significance (500+ clicks per variant)
  3. Only measuring clicks — Conversions matter more than clicks
  4. Not documenting results — Keep a test log for institutional knowledge
ab-testinggrowthplaybookexperimentationconversion-optimization