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%.
Experimentation
Available on supported plans
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
Experiment · go.brand.com/launch
Spring launch A/B test
Running · Sticky assignment enabled
Live
Variant A2,881 clicks
brand.com/landing-v1
60%
Variant B1,931 clicks
brand.com/landing-v2
40%
Assignment model
Deterministic — same visitor always sees same variant
End experiment → promote winner to 100%
4,812
Total clicks
2
Variants
60/40
Split
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
Available on supported plans
Experiments are available on supported plans alongside routing and targeting.
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.
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.
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 — available on Nimriz today
Sign up and start using this feature alongside branded links, analytics, and the full Nimriz platform.