BlogIn-app browsers

Why Instagram and WhatsApp links open the browser, not your app

· 8 min read · By the Strait team

Your App Links and Universal Links work from Messages, but the same link tapped in Instagram or WhatsApp opens a web page. Here is what in-app browsers do to a deep link, how to tell which one a tap came from, and how to get people into the app.

You set up Android App Links and iOS Universal Links. You test by sending yourself a link in Messages, tap it, and the app opens on the right screen. Then marketing puts the same link in an Instagram bio or a WhatsApp broadcast, and the reports come in: "it just opens a web page". Nothing is wrong with your verification. The link was opened by an in-app browser, and in-app browsers play by different rules.

This post explains what an in-app browser is, why a deep link often stops working inside one, how a server can tell which app a tap came from, and the practical fixes on Android and iPhone.

What an in-app browser is

When you tap a link inside Instagram, Facebook, TikTok, X, Snapchat or LinkedIn, the app usually doesn't hand the link to Chrome or Safari. It opens the page in its own browser: a web view embedded in the app, with the app's toolbar around it. Chat apps such as WhatsApp and Telegram can do the same on some phones and versions.

For the app that owns the web view, this keeps people inside the feed. For you, it changes how the link is opened.

App Links and Universal Links are decided by the operating system when a link is handed to the system to open:

  • On Android, a tapped link that leaves an app as a normal "view this URL" request goes through Android's link resolution. If your app is verified for that domain, Android opens your app. (Android: App Links)
  • On iPhone, iOS checks Universal Links when a link is opened from a user's tap in Safari or another app that passes the link to the system. (Apple: Supporting universal links in your app)

A web view embedded in another app usually loads the URL itself instead of handing it to the system. The operating system never sees a link to resolve, so it never gets the chance to open your app. The page loads inside Instagram, and that's the end of the road unless the page does something about it.

Two more habits of in-app browsers make it worse:

  1. They often block app-store and custom-scheme navigations that a normal browser would allow, or show a warning first.
  2. They're hard to test. You can't paste a link into Instagram's browser the way you paste into Chrome, so many teams only find out after a campaign launches.

This is also why "it works when I test it" is so common: most developers test from Messages, Slack or email, which hand links to the system. Tap from the channel your users actually use.

How a server knows where a tap came from

The good news: in-app browsers announce themselves. Each one adds its own token to the browser's user agent string, so the link's server can recognise it on the first request. The tokens we match in our engine:

In-app browser Token in the user agent
Instagram Instagram
Facebook FBAN, FBAV or FB_IAB
TikTok musical_ly, Bytedance or TikTok
X Twitter
Snapchat Snapchat
LinkedIn LinkedInApp
WhatsApp WhatsApp (after a normal Mozilla/5.0 browser prefix)
Telegram Telegram (same)

There is a trap with chat apps. When you paste a link into WhatsApp or Telegram, the app fetches the page itself to build the preview card. That request also says WhatsApp, but without the Mozilla/5.0 prefix a real browser sends. If you treat it as a person, you count a tap nobody made and may even send a robot to the Play Store. If you treat every WhatsApp request as a robot, you miss real people in WhatsApp's web view. We learned this one the hard way: an early version of our engine counted WhatsApp and Telegram web-view taps as preview bots until we split the two cases on that prefix.

Generic web views can be spotted too: Android web views include ; wv) in the user agent, and iOS web views leave out the Safari token that real Safari sends.

The fixes

1. Make direct taps work first

Before worrying about in-app browsers, make sure the normal path is solid: a verified App Links domain on Android and Universal Links on iPhone. That handles taps from Messages, Gmail, Slack and every app that hands links to the system. If those don't work yet, fix them first; our free App Links checker fetches both verification files from your domain and tells you what's wrong.

2. On Android: offer a one-tap hand-off

Android in-app browsers usually honour a link the person taps that uses Android's intent:// format, because a tapped intent link is passed to the system. So when the server sees an in-app browser on Android, the useful response is not a redirect. It's a small page with a big Open in app button whose link is an intent URL for your app, with a fallback to Google Play (keeping the link for after install) or your website.

That is what Strait does. The page leads with your app's name, icon and colour, and has a Continue anyway link to the web page for people who'd rather stay in the browser.

3. On iPhone: guide people to Safari

iOS gives a web page no reliable way to break out of another app's web view. The honest fix is a clear page: "You're in Instagram's in-app browser, which can't open apps", with the steps to open the link in Safari (the menu in the corner, then Open in browser or Open in Safari), plus a Get the app button for the App Store and a Continue anyway link. Once the link is in Safari, Universal Links work normally, and deferred deep linking works when you've turned on iPhone install matching (it's opt-in).

Some channels are friendlier than others. Where you control the format, prefer channels that usually hand links to the system, such as SMS and push notifications. Most email apps do too, but test the ones your users rely on. For Instagram, a link in a story sticker or bio will usually open in Instagram's browser, so plan for the escape page rather than hoping it won't happen.

5. Measure per channel

You can't fix what you can't see. Record which in-app browser each tap came from, so a report can say "Instagram taps: most went through the escape page; WhatsApp taps: most opened the app directly". In Strait, a tap's channel is the first of these that has a value: the tap URL's utm_source, the link destination's utm_source, the in-app browser it was tapped in (whatsapp, instagram…), then the referring site. Each tap also records where we sent it: directly to the app, the store, the website, or the in-app browser page.

Test it before your campaign does

You can see what a tap from a given app would do without a phone. Our API's simulate endpoint takes a link and a user agent preset (instagram-ios, instagram-android, facebook-android, whatsapp-android, and others) and returns the decision, where the visitor would be sent and a plain-English reason, without recording a tap or counting toward your plan:

Terminal
curl "https://strait.link/v1/simulate?url=https%3A%2F%2Fhilltop.strait.link%2Fsummer&ua=instagram-android" \
  -H "Authorization: Bearer $SECRET_KEY"

The decision comes back as redirect, interstitial, escape, preview, expired or blocked. Dashboard → Playground runs the same check. Then do the real thing: send the link to a test account in the app your users use, and tap it there.

On real hardware, our own test suite drives an Android phone over adb and checks where each tap lands: from Messages with the app closed, in the background and on screen; from Chrome, Samsung Internet, Edge and Firefox; and with the app not installed. Two browser details from those runs are worth knowing. Firefox and Edge ask "open in app?" before handing a link over. That's the browser's choice and can't be skipped, but once the person confirms, the app opens on the right screen and the tap is counted once. And Samsung Internet hands links to apps like Chrome does, as long as Settings → Useful features → Open links in other apps is on.

A checklist

  • App Links and Universal Links verified (check with the App Links checker)
  • Tested by tapping from the real channel, not from Messages only
  • In-app browsers detected on the server by user agent
  • Chat-app preview fetchers kept apart from real taps
  • Android: an Open in app page with an intent:// hand-off and a store fallback
  • iPhone: a page that explains how to open Safari, with Get the app
  • Taps reported per channel, with where each one was sent

More detail on each case is in our troubleshooting guide and the docs on how short links decide where to send a tap.

Sources and how we checked

  • Android Developers, Handling Android App Links, and Apple, Supporting universal links in your app: how each operating system decides to open an app from a link.
  • The in-app browser tokens are the patterns in Strait's own user-agent detection code, which our link engine and its test suite use.
  • Browser behaviour (Chrome, Samsung Internet, Edge, Firefox) and the direct-tap scenarios come from our real-phone test suites on an Android phone, run before each release; the WhatsApp and Telegram preview-bot fix is from our engine's change history (October 2026).
  • The simulate endpoint and the channel rule are documented in our REST API reference.