Deep Link Generator

Deep Link Generator: Build App Links Without Guessing the Syntax

A link that opens your app on the right screen is worth considerably more than one that dumps the user on the home tab. Someone tapping a promotion should land on the promotion, not on a menu where they have to find it again.

Getting there means constructing a URL with the correct scheme, path, and parameters — easy to describe and easy to typo. This deep link generator builds it correctly from four fields.

Two Link Types, and the Difference Matters

The first choice determines everything else.

Custom scheme (myapp://) opens your app directly. Fast and simple, but it only works if the app is installed. If it is not, the link fails — usually with an unhelpful error that looks like your app is broken.

Universal link / App Link (https://) is a normal web URL that opens the app when installed and falls back to the website when it is not. Slightly more work to set up, and almost always the right choice for anything a stranger might tap.

The practical rule: use a custom scheme inside your own app or in contexts where installation is certain, and a universal link everywhere public — emails, ads, social posts, QR codes.

Path and Parameters

Scheme or domain is your app's scheme or your verified domain.

Path is the destination inside the app — the product, the article, the specific screen.

Query params are entered as comma-separated key=value pairs, and this is where the useful detail lives: a product ID, a referral code, a campaign source, a promo identifier. This is how one link can open the right screen with the right content already loaded.

Copy the finished URL in one click.

What This Tool Does Not Do

Worth stating plainly, because it is the step people miss.

It generates the link URL. It does not configure your app to handle that link. Universal links require Associated Domains and a verification file on your server for iOS; Android App Links require intent filters and their own verification. Those are development tasks that happen in your project, not in a URL builder.

So the sequence is: configure the app to handle the links, then use this to build them quickly and consistently.

A Realistic Example: A Campaign Link

A marketing manager is emailing 8,000 customers about a specific product. The current link goes to the website, and app users get bounced to a browser version of a product they already have an app for.

She builds a universal link with the domain, the path to that product, and query parameters carrying the product ID and a campaign source.

App users land on the product screen inside the app. Everyone else lands on the same product page on the web. The campaign parameter tells her afterwards which of those groups converted better — and the answer changes how she structures the next campaign.

Test Both States Before Sending

The mistake that gets caught too late: testing only on a phone that has the app installed.

Test the link twice — once with the app installed, once without. The uninstalled case is where custom schemes fail visibly and where a misconfigured universal link reveals itself. Since most people receiving a marketing email do not have your app, that is the state most of them will experience.

Who Uses It

Mobile developers wiring up navigation. Marketers building app campaigns. Product teams creating shareable in-app links. QA testers reproducing specific screens. Turn the link into a scannable code with the QR Code Generator, or add campaign tracking with the UTM Link Builder. For the app-side configuration, our mobile app development service handles it — the 2026 mobile app development guide covers the wider picture.

Build Your Link Now

A link that lands users on the right screen converts better than one that makes them search for it. Enter your scheme, path, and parameters above and copy a correctly formed URL.