Per-link routing rules
Author explicit route and experiment decisions on individual links instead of burying redirect logic inside brittle destination URLs.
Routing & deep links
Targeted routing and experimentation
Create per-link routing decisions for country, device, time windows, experiments, and mobile deep links with preview support.
What teams get
- Route by device OS, device type, country, or time window from a single short link.
- Run weighted sticky experiments without inventing a second redirect stack for A/B logic.
- Configure smart-mobile destinations on eligible verified branded domains with app, store, and web fallback behavior.
Availability
Available on supported plans
Routing, experiments, and deep links are included on supported plans. Deep links require eligible verified branded domains.
Weighted sticky experiments
Split traffic with stable variant assignment and reporting-ready experiment metadata so tests stay measurable after launch.
Eligible-domain deep links
Serve Universal Links or App Links only on branded domains that are verified, ready, and safe for association-file ownership.
Preview before shipping
Use the routing preview and simulator flows to understand what Nimriz will choose before traffic hits the live link.
A practical routing flow
One short link can serve different destinations based on the request context without becoming impossible to reason about later.
US iOS visitor
Use the smart-mobile path you configured: open the app when installed, otherwise the App Store or web fallback.
Android visitor
Follow the configured Android fallback path for that same link.
After-hours traffic
Route to a recap or waitlist destination using the same branded short URL.
Experiment posture
Weighted variants preserve sticky assignment and reporting context.
Important guardrails
- Routing decisions run after host and link resolution so branded-domain ownership still stays canonical.
- Deep links are intentionally constrained to eligible verified branded domains, not shared or Nimriz Built-in hosts.
- Preview and simulator flows matter because Nimriz cannot see whether an app ultimately opened on the device.
- Experiment reporting is explicit and lifecycle-aware—variants and outcomes stay visible in the product instead of hiding inside opaque redirects.