Deep links & mobile

Available on supported plans

Deep links and mobile app routing

Configure smart-mobile destinations on eligible verified branded domains — app open when installed, App Store or Play Store otherwise, web fallback always.

Start for free View pricing

iOS + Android

Platform support

3-tier

App · Store · Web fallback

Verified

Domain-only deep links

Deep link · go.brand.com/get-app

Mobile fallback chain

Verified domain

✓

iOS · App installed

Opens app at /dashboard

↗

iOS · No app

App Store listing

✓

Android · App installed

Opens app at /dashboard

↗

Android · No app

Play Store listing

→

All other traffic

brand.com/app (web)

Association files managed by Nimriz

apple-app-site-association

assetlinks.json

iOS + Android

Platforms

Fallback tiers

Verified

Domain

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 Deep links & mobile routing

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

Serve Universal Links (iOS) and App Links (Android) from eligible verified branded domains.
Automatic fallback chain: app when installed → App Store or Play Store → web destination.
Use the deep-link preview simulator to understand what Nimriz will serve before traffic hits the live link.

Availability

Available on supported plans

Deep links require eligible verified branded domains. Routing, targeting, and experiments are available on supported plans.

Compare plans →

How it works

Verify an eligible branded domain

Deep links are only available on verified branded domains that pass Nimriz eligibility checks. The DNS verification and association-file setup is guided in the dashboard.

Configure the three-tier fallback chain

Set your app identifier, App Store URL, Play Store URL, and web fallback. Nimriz serves the right tier based on what is installed and which platform the visitor is on.

Preview before shipping

Use the simulator to see what each platform and device combination will receive. Deep link behavior is notoriously hard to debug live — preview first.

Everything included

Universal Links and App Links

Serve iOS Universal Links and Android App Links — the modern deep-link standards that open apps directly without redirecting through a browser-based interstitial.

Three-tier fallback

App open when installed, App Store or Play Store when not, web destination as the final fallback — so no visitor ever reaches a dead end.

Eligible-domain enforcement

Deep links are intentionally constrained to eligible verified branded domains. Shared Nimriz domains and unverified hosts are not eligible — by design.

Preview and simulator

Deep-link behavior is hard to test live. Nimriz provides a routing preview and simulator so you understand what each platform will receive before shipping.

Time-window routing

Combine deep links with time-window rules — serve the app deep link during business hours and a different destination after hours on the same branded URL.

Association-file ownership

Nimriz manages the apple-app-site-association and assetlinks.json files for eligible verified branded domains so you do not have to host them yourself.

A practical mobile routing flow

One short link can open your app on a device that has it installed, send new users to the relevant store, and handle web as the final fallback.

iOS — app installed

Universal Link opens the in-app destination directly.

iOS — no app

Redirected to the App Store listing for that app.

Android — app installed

App Link opens the in-app destination directly.

All other traffic

Web fallback destination — the campaign page or product page.

Important guardrails

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.
Routing decisions run after host and link resolution so branded-domain ownership remains canonical.
Association-file management is handled by Nimriz for eligible domains — review eligibility requirements in docs.

Related next steps

Geo & device targeting →A/B experiments →Deep links and plans →Developer docs →

Ready to try it?

Deep links & mobile routing — available on Nimriz today

All features View pricing Start for free