Nimriz

Routing rules and preview

Author per-link routing and experiments, use preview, and understand deep-link and rollout limits.

Routing rules and preview

This guide explains how to use the routing editor in both the create flow and the link detail page, plus what routing preview can and cannot tell you before traffic goes live.

Routing and deep links roll out gradually. Your workspace needs a supported plan, any required feature access for that workspace, and a domain that meets readiness rules (especially for deep links).

What routing rules can do

In v1, routing rules are:

  • per-link only
  • evaluated in order
  • first-match wins

The current editor supports:

  • country rules
  • device OS rules
  • device-type rules
  • UTC time windows
  • weighted A/B splits
  • deep-link actions on ready branded domains

In the dashboard, create-flow routing is organized into three capability tabs:

  • Geo & Device Targeting
  • Deep links
  • A/B Testing

Under those tabs, the dashboard still preserves the capability-first editing experience, but it now saves one ordered decision list underneath:

  • each item is an explicit Route or Experiment decision
  • match conditions come first
  • destination or experiment behavior comes second

If no enabled rule matches, the link keeps its canonical web destination.

How to order rules safely

Put the most specific rules first and broad rules last.

Examples:

  • country plus device conditions before broad country-only rules
  • campaign-specific mobile rules before generic mobile rules
  • catch-all rules with no conditions at the very end

If you put an enabled catch-all rule first, later rules may never run.

What routing preview shows

Routing preview runs the current draft through the same preview logic used in production, with:

  • host
  • path
  • country
  • device OS
  • device type
  • UTC timestamp

Preview is meant to answer: “Which destination would this request resolve to right now?” You can use it while the link is still a draft in the create flow, or later from the saved link detail page.

What routing preview does not pretend to know

Some redirect behavior still depends on runtime realities outside the dashboard:

  • whether a mobile app is actually installed
  • whether an existing visitor already has a sticky A/B cookie
  • later query-forwarding or query-merge behavior that is not part of the current product yet

For A/B rules, preview behaves like a first visit. It can show the chosen variant, but it does not replay a real sticky assignment cookie.

Preview also returns the canonical routing identity fields for troubleshooting and support:

  • decision_id
  • decision_kind
  • destination_type
  • experiment_key
  • experiment_run_key
  • variant_key

Deep-link eligibility

Deep-link actions only work on ready branded domains in v1. Nimriz Built-in or shared domains are intentionally excluded.

Deep links also stay disabled until deep links are enabled for your workspace. If the domain is ready but the workspace is still locked, Nimriz keeps traffic on web destinations and association files stay unavailable.

If the editor warns about deep-link readiness, check:

  • the domain is branded and not shared across accounts
  • DNS verification is complete
  • hostname and SSL are active
  • active iOS or Android app-link metadata exists

For more detail, go to the domain settings deep-link readiness card.

Why there are no domain templates yet

Routing remains per-link only for now by design. Domain-wide templates or defaults may come later so the redirect contract stays narrow and predictable while the editor and preview mature.

Related guides