Sharer-ID URL encoding for viral factor A/B testing
Encode the sharing user's ID into every shared URL so you can calculate viral factor as a cohort-to-cohort ratio and A/B test product changes to increase it.
Why this can grow a startup
Most teams treat sharing and referrals as fire-and-forget features. By encoding user IDs into every shared link and tracking which signups came from which sharers, you turn virality into a measurable, optimizable metric. A/B tests on share prompts, invite timing, and link presentation compound over time. The approach also reveals when a viral loop is saturating (generation-over-generation ratio declining), so you can switch channels before growth stalls.
Source-backed example
Andrew Chen (a16z, Nov 2025) documents the specific engineering pattern used by Instagram, Facebook, LinkedIn, and modern genAI apps like Sora — by storing sharer_id alongside every new signup row, teams calculated viral factor (e.g., 50 downstream signups from 100 sharers = 0.5) and ran A/B tests on invite flows, share buttons, and onboarding to push the ratio toward 1.0+. Chen notes that products with viral factor above 0.5 meaningfully amplify all other acquisition channels, and that tracking generation-over-generation decay is critical to avoid saturation.
Source details
Source: speedrun.substack.com
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
Source discovered: March 23, 2026
When to use it
Use this when Referrals is relevant to 0-100, 100-1K and you can run a bounded test with a free budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Referrals, using evidence from speedrun.substack.com as context—not as a promised result.
- Record a baseline for: Share of referred users who reach the activation milestone. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Connect activation, customer value, retention, and referral into one measurable loop.