Weighted traffic splits
Assign any percentage distribution across variants - 50/50, 80/20, or a three-way split - validated at save time so weights always total 100%.
ExperimentationProfessional+
Weighted A/B experiments on short links
Split traffic across weighted variants, keep assignment sticky per visitor, and measure experiment performance without a separate A/B testing stack.
Weighted
Traffic splits
Sticky
Variant assignment
Lifecycle
Aware reporting
go.brand.com/launch
Spring launch landing test
Running · sticky assignment · 9 days in
Traffic split100% allocated
A60%
B40%
AOriginal pricing page60%
brand.com/landing-v1
Weight60%
Visitors11k
Conv. rate2.6%
BSocial proof layoutWinning
brand.com/landing-v2
Weight40%
Visitors7.4k
Conv. rate3.3%
18.4k
Total clicks
96%
Confidence
+27%
Uplift · B vs A
Without a dedicated link workflow
- Configuration, reporting, and follow-up work can spread across multiple tools.
- Teams rely on manual notes or separate dashboards to explain what happened.
- Changing campaign behavior often requires recreating or replacing links.
With A/B experimentation
- The capability stays attached to the same branded short-link record.
- Operational details are easier to review alongside analytics and related links.
- Teams can keep the public URL stable while improving how the link behaves behind it.
What you get
- Split traffic across up to N variants with custom percentage weights from a single short link.
- Variant assignment is sticky - the same visitor sees the same variant on repeat visits.
- Experiment metadata stays visible in reporting so you can measure outcomes without opaque redirects.
Availability
Weighted A/B split routing is included on Professional and Enterprise.
Experiments share the same routing entitlement model as other advanced link controls.
How it works
1
Define variants and set weights
Add two or more destination variants to any short link and assign traffic percentages. Weights are validated to total 100% before saving.
2
Visitors get sticky assignments
Each visitor is assigned a variant on first encounter. That assignment persists on repeat visits so your experiment results aren't muddied by split experiences on the same user.
3
Read results and end the experiment cleanly
Experiment metadata stays visible in dashboards throughout the test. When you end an experiment, traffic consolidates to your chosen winning variant - no stale splits lingering.
New link · Experiment
Experiment active100% allocated
A60%
B40%
Abrand.com/landing-v160%
Bbrand.com/landing-v240%
Add URLShares auto-balance to 100%
Everything included
Sticky variant assignment
The same visitor always sees the same variant. Sticky assignment uses a deterministic model so repeat visits do not muddy experiment data.
Reporting-aware lifecycle
Experiment state, variant labels, and traffic weights are part of the link record - not hidden inside opaque redirect behavior. End, pause, or promote a winner explicitly.
No second redirect stack
Experiments run inside the same redirect path as regular links - not a separate A/B layer bolted on top. Less moving infrastructure, fewer failure modes.
Clean experiment ending
When you end an experiment, choose the winning variant and all traffic consolidates cleanly. No stale percentage splits left running after the test is over.
Combine with targeting rules
Run an experiment only for a specific country or device OS - combine targeting rules and experiments on the same link for layered personalization.
A real experiment lifecycle
Start an experiment, let it run with sticky assignment, read results, then end it cleanly - all from the same branded short link.
Variant A (60%)
brand.com/landing-v1 - original pricing page.
Variant B (40%)
brand.com/landing-v2 - new social proof layout.
Sticky assignment
Repeat visitors always see the same variant they were assigned first.
End experiment
Promote Variant B as winner - 100% of traffic routes there going forward.
Experiment lifecycle
1
Launch the weighted test
Two destinations on one short link, 60/40 to start.
A 60%
B 40%
2
Read results, sticky per visitor
Repeat visitors keep their first variant, so the comparison stays clean.
Same visitor → same variantSocial proof layout leads · 96%
Promote the winner
End the test and consolidate. No stale splits left running.
B · brand.com/landing-v2 · 100%
Why this matters
- Experiment metadata stays visible in reporting so outcomes are attributable, not buried in opaque redirect behavior.
- Sticky assignment prevents split-experience contamination that inflates or deflates measured differences.
- Running experiments inside the main redirect path removes an entire layer of A/B infrastructure from your stack.
- Clean lifecycle management means teams can end experiments deliberately instead of leaving stale splits running indefinitely.
Ready to try it?
A/B experimentation is available on supported plans
Create an account to explore Nimriz, then use pricing to choose the plan and setup path that matches this workflow.