Skip to main content
An app dynamic link inspects the device on the way through and decides where to send it: into your native app when installed, to the app store or a custom URL when you configured that for visitors without the app, or to your website (usually destination_url on desktop and when no store/custom fallback applies). One URL works across iOS, Android and desktop, so the same link can go on a poster, in an email, and in a tweet. A store link sends existing users to a page telling them to install something they already have. A dynamic link opens the app they already installed, which is usually the whole point of sending them the link.

What it needs

1

A dedicated Dynamic Link domain

App Link verification is host-wide, so a shared shortlink domain cannot carry an association. Claim a Dashlink subdomain or add your own under Dynamic link domains. See Branded links.
2

App association files

Dashlink copies assetlinks.json and the AASA file from your destination website onto the Dynamic Link domain. The app still needs an Android autoVerify intent-filter and an iOS applinks: entitlement for that host. See App association.
3

Per-platform behaviour on the link

What to do on iOS, on Android, and when the app is not installed. See Creating.
4

Optional native SDK (required for deferred)

Routing works without an SDK. First open after a store install lands on the original content only if a Dashlink SDK is installed: Android, iOS, or a wrapper that calls those SDKs (React Native, Flutter, Unity, Unreal). See Receive.
Without a verified association on the Dynamic Link domain — and the matching intent-filter / Associated Domains entry in the app — the OS never intercepts the tap. Installed users then follow the browser path (Play Store or custom URL for https App Links).
App dynamic links are Shortlink records with extra routing, which has three practical consequences:
  • An API key granted the shortlinks module covers them; there is no separate grant
  • They appear in analytics alongside ordinary links
  • They can be tagged, added to campaigns, and bulk-managed the same way

Next

Creating

Per-platform behaviour and fallbacks.

App association

The files iOS and Android need.

Receive

Routing vs deferred, JSON resolve, and which SDK you need.

Android SDK

Gradle, App Links, Play Install Referrer, first-open join.

iOS SDK

SPM or CocoaPods, Universal Links, pasteboard first-open.

React Native

Host allowlist, Linking for live taps, deferred startup call.

Flutter

Host allowlist, app-links stream, deferred startup call.

Unity

Android and iOS player builds. Editor and desktop return no link.

Unreal Engine

Android and iOS packages. Editor and desktop return an empty link.