Nimriz
Smart targetingAvailable on supported plans

Target by country, device, and OS

Route visitors to different destinations based on their country, device type, or operating system - from a single short link, without fragmentation.

Start for freeView pricing
40+
Countries supported
3 dimensions
Country · Device · OS
Single link
No duplication needed
Targeting rules · go.brand.com/launch
Routing rules
4 active
1
Country = US→brand.com/us-launch
2
Country = DE→de.brand.com/launch
3
OS = iOS→apps.apple.com/app
4
OS = Android→play.google.com/app
↓
Default → brand.com/launch (all other visitors)
40+
Countries
3
Dimensions
1 link
No duplicates

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 Geo & device targeting

  • 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.

Use this page to evaluate the workflow, then follow the related docs or pricing path when you need implementation detail.

What you get
  • Route by visitor country to localized landing pages, regional storefronts, or language-specific destinations.
  • Detect device type (mobile, desktop, tablet) and OS (iOS, Android, Windows, macOS) for precise segment targeting.
  • All targeting runs on the same short link - no need to create separate links per audience segment.
Availability

Available on supported plans

Geo and device targeting are included on supported plans alongside routing and experiments.
Compare plans

How it works

1

Add a targeting rule to any link

Open any short link and configure a targeting rule. Choose the condition - country, device type, or OS - and the destination that should receive that segment.

2

Stack rules for multiple segments

Add multiple rules to the same link. Each rule is evaluated in order; the first match wins. Unmatched traffic falls through to the default destination.

3

Preview before going live

Use the routing preview to simulate what Nimriz will choose for any combination of country, device, and OS before the link receives real traffic.

Everything included

Country-based routing

Route US visitors to one destination and European visitors to another - or serve region-specific pricing pages, regulatory disclosures, and language variants.

Device type detection

Serve mobile visitors a lighter experience and desktop visitors a feature-rich one - or gate certain experiences to specific device categories.

OS-level targeting

Target iOS, Android, Windows, and macOS separately. Useful for directing visitors to platform-specific app stores, download pages, or native experiences.

Ordered rule evaluation

Rules are evaluated top-to-bottom; the first match wins. A default destination handles all unmatched traffic so no visitor ends up in a dead end.

Routing preview

Simulate what Nimriz will choose for any combination of country, device, and OS before the link goes live - no guessing, no broken segments after launch.

No link fragmentation

One branded short URL serves every segment. You distribute one link, collect one set of analytics, and update one record - audience segmentation is invisible to visitors.

One link, three different audiences

The same branded short link can route iOS users to the App Store, German visitors to a localized page, and everyone else to the main destination.

OS = iOS
Routed to apps.apple.com/your-app - install prompt for iPhone and iPad users.
OS = Android
Routed to play.google.com/your-app - the Play Store listing.
Country = DE
Routed to de.brand.com/launch - the German-language landing page.
All other visitors
Routed to brand.com/launch - the default destination.

Important guardrails

  • Targeting decisions run after host and link resolution so branded-domain ownership stays canonical.
  • Country detection is best-effort - use a fallback destination for any visitor the system cannot classify confidently.
  • Preview and simulator flows matter because server-side routing cannot see whether an app ultimately opened on device.
  • Targeting rules are ordered and explicit - there are no implicit groupings or fuzzy-match logic.

Related next steps

A/B experimentsDeep links & mobile routingTargeting availabilitySmart routing use case

Ready to try it?

Geo & device targeting 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.

All featuresView pricingStart for free