Free tool
Deep link generator
Fill in your app scheme and store pages. The preview below runs the same decision logic the redirector uses on a live click.
Add at least one app link or store page to see the preview.
Why one link is not enough
A raw app scheme like myapp://product/42 does nothing on a device without the app: the browser shows an error page, and the visitor leaves. A store link does the opposite — it sends people who already have the app back to a download page they do not need. A deep link is the arrangement that handles both, and the whole trick is what happens in the gap between the two.
The preview above runs the same decision table the redirector runs, so what you see here is what a visitor gets. The full behaviour, including deferred context after an install, is described on the mobile links page.
What the wait actually does
When both an app link and a store page are present, the visitor lands on a short interstitial that attempts the app scheme and starts a timer. If the app opens, the browser tab is backgrounded and the timer never fires. If nothing happens, the timer sends the visitor to the store. Under about 500 ms a slow phone has not finished switching context; over about 2,500 ms the page reads as broken.
In-app browsers inside Instagram, TikTok and Facebook handle scheme navigation inconsistently, which is why that case has its own setting. The deep link documentation covers the domain association files both platforms require.
Frequently asked questions
Should I use a custom scheme or a universal link?
Use a universal link (an https address your app claims) when you can, because it degrades gracefully: a device without the app simply opens the web page. Use a custom scheme when your app has no associated domain or when you need to reach a screen the web version does not have. This generator accepts both, and the preview treats them the same way.
Do I need the app association files?
For universal links, yes. iOS reads /.well-known/apple-app-site-association from your domain and Android reads /.well-known/assetlinks.json. Without them the operating system never hands the link to your app, no matter how the URL is written. LinkProfit serves both files from your branded domain once you enter your app identifiers.
What happens to the campaign context after an install?
By default it is lost: the store opens, the visitor installs, and the app launches with no idea which link brought them. Deferred delivery stores a short-lived device fingerprint at click time and hands the original context to the app on first launch, so a signup can still be attributed to the campaign that produced it.
Why is there a separate setting for tablets?
Because a tablet is a phone for some apps and a desktop browser for others. A media app usually wants the tablet to open the app; a business tool often prefers the full web version on a larger screen. The setting makes the choice explicit instead of guessing from screen width.
Ship mobile links under your own domain
Branded deep links, association files and deferred context on every plan.
No card required for the trial.