A universal install link is one URL that sends every visitor to the right place. iOS users land on the App Store. Android users land on Google Play. Desktop visitors get a web page. Everyone else gets a sensible fallback.
The alternative — posting two store links side by side — is so common that it looks normal. It isn't. It quietly costs installs at every single touchpoint.
What the link actually does
When someone clicks, the server inspects the request and decides where to send them. Three signals matter:
Platform. The User-Agent header identifies iOS, Android, or desktop. This is the primary routing decision and it is right the overwhelming majority of the time.
Browser context. Whether the request came from a normal browser or an in-app browser inside Instagram, TikTok, LinkedIn, or similar. This matters more than most people expect — see below.
Fallback. Anything the first two cannot resolve — a bot, an unusual device, a desktop visitor — needs a defined destination rather than an error.
The decision happens server-side before anything renders, so the visitor experiences it as a direct jump to the store rather than a visible detour.
Why two links lose installs
Three separate problems, and they compound.
It asks the visitor to do work. "iOS here, Android here" requires the reader to identify their own platform and pick correctly. Most will. Some won't bother. That gap is pure loss, and it is entirely avoidable.
Most surfaces only allow one link. A social bio. A QR code on a poster. An email signature. A podcast description read aloud. In every one of those, two links is not an option — you either pick a platform to favour or send everyone to a landing page and add a step.
It breaks measurement. Two links means two sets of numbers that have to be manually combined, and no single figure for "how many people clicked our install link this month." One link gives you one number.
The in-app browser problem
This is the part that trips up most home-grown implementations.
When someone taps a link inside Instagram, TikTok, or LinkedIn, it usually does not open in Safari or Chrome. It opens in an embedded browser controlled by that app. These have real constraints:
- Some block or ignore custom URL schemes such as
myapp:// - Some intercept navigation in ways that break automatic redirects
- Some strip or alter query parameters
- Behaviour differs between iOS and Android versions of the same app
A naive redirect that works perfectly in Safari can silently fail inside an in-app browser — and social traffic is exactly where install links get used most.
Handling it properly means detecting the in-app browser, preferring standard https store URLs over custom schemes, and showing a visible "Open in App Store" fallback button if the automatic redirect does not fire. Silent failure is the worst outcome, because you never learn it happened.
What to check before shipping
- Both stores configured, with a web fallback for desktop
- Tested from a real phone, not just a desktop browser with device emulation
- Tested from inside Instagram or TikTok, not only Safari and Chrome
- A fallback that makes sense — your homepage is better than an error, a
dedicated download page is better still
- Analytics on the link itself, so a drop in installs is diagnosable
Where install links pay off most
Social bios. One link, works for everyone, no platform bias.
QR codes. Printed material cannot branch. Physical signage, packaging, event badges, and table tents all need a single destination that adapts.
Email and newsletters. One CTA button instead of two competing ones.
Creator and influencer campaigns. Give every partner the same link and still attribute traffic separately by source.
Podcast and video. A URL that can be read aloud and typed from memory.
How Bridgly does it
Bridgly gives you one short link — bridgly.co/yourapp — with App Store, Google Play, and web destinations configured behind it. Device detection and routing are handled server-side.
Every link also comes with a QR code and an embeddable widget, so the same destination works in print and on the web. Clicks and scans are tracked by source and channel, and install attribution via store sync is available on paid plans.
The short version
- One link, routed server-side by device, beats two links everywhere.
- Most surfaces physically allow only one link.
- In-app browsers are the hard case — test there specifically.
- Always define a web fallback.
- Measure at the link, so you can see problems before they cost you a campaign.
Frequently asked questions
- What is a universal install link?
- A universal install link is a single short URL that detects the visitor's device and platform, then sends them to the correct destination — the App Store on iOS, Google Play on Android, and a web page on desktop or unsupported platforms. One link replaces the usual pattern of posting separate iOS and Android links.
- Why not just post both store links?
- Every extra choice costs conversions. Posting two links asks the visitor to identify their own platform before they can act, and on surfaces that allow only one link — most social bios, printed material, QR codes — it is not even possible. A single link removes the decision entirely.
- Do universal install links work in app browsers like Instagram?
- They can, but in-app browsers are the hardest case. Some intercept navigation or block store URL schemes. A well-built install link detects the in-app browser, routes to a normal https store URL rather than a custom scheme, and provides a visible fallback if the automatic redirect is blocked.
Read more
Fundamentals · 1 min read
Bitly vs Dub vs Bridgly: picking by job
Bitly shortens. Dub pays digital partners. Bridgly routes app installs and ties physical QR scans to attributed sales and commissions.
Fundamentals · 2 min read
Deferred deep linking, explained without the jargon
Deferred deep linking carries a destination across an app install, so a new user lands where they were headed instead of your home screen. Here is how the matching works, why it is never perfect, and when it is worth the setup.
Fundamentals · 1 min read
App Links vs Universal Links: what differs and what does not
Android App Links and iOS Universal Links solve the same problem with different plumbing. Here is what each verification file does, why you need both, and the mistakes that stop them verifying.