---
title: "Know which app a click came from, and route in-app browser visitors"
description: "Linkbreakers now recognizes the in-app browser of Instagram, TikTok, Facebook, Messenger, Threads, Snapchat, LinkedIn, Pinterest, X, WeChat, LINE and the Google app on every visit, records the app's version and details, and lets the Browser condition route those visitors. On every plan."
canonical: "https://linkbreakers.com/help/article/know-which-app-a-click-came-from-in-app-browsers"
last-updated: 2026-11-03
---

# Know which app a click came from, and route in-app browser visitors

> Linkbreakers now recognizes the in-app browser of Instagram, TikTok, Facebook, Messenger, Threads, Snapchat, LinkedIn, Pinterest, X, WeChat, LINE and the Google app on every visit, records the app's version and details, and lets the Browser condition route those visitors. On every plan.

## Short answer

When someone taps your link inside Instagram, TikTok or another app, it opens in that app's in-app browser, usually with no referrer. Linkbreakers now recognizes the in-app browser of 12 apps, records which app each click came from with its version and the details the app sends, shows it in your dashboard, exports and webhooks, and lets the **Browser condition** route those visitors. See [how to know which app a click came from and route in-app browser visitors](/help/article/how-to-detect-and-route-in-app-browser-visitors).

## What we shipped

A link in an Instagram bio, a TikTok profile, a story, a DM or an ad opens inside the app. The page you link to cannot tell where the visit came from, and some things do not work there: Apple Wallet passes, app store links, file downloads and some checkouts.

### Which app, on every visit

Linkbreakers reads the in-app browser from the user agent of every visit: Instagram, Facebook, Messenger, Threads, TikTok, Snapchat, LinkedIn, Pinterest, X, WeChat, LINE and the Google app. An Android webview that does not name its app is recorded as **Other in-app browser**.

Each visit's device records the in-app browser, the app version (every app except Pinterest, which sends none), and what the app writes about itself when it does: the app's language, the exact phone model, the manufacturer, the network type, the mobile carrier, the screen resolution and density, the region and the app build.

### Where it shows

- Visitor and device details, the activity timeline and the Live view
- The dashboard: a breakdown and widgets by in-app browser, and by app and major version (for example "Instagram 447")
- CSV exports and webhook payloads

Device details are stored when the data collection level is Basic or Advanced.

### Route in-app browser visitors

Each option of the **Browser condition** now switches between **Browser** and **In-app browser**. In-app browser options are **Any in-app browser**, each app on its own, and **Other in-app browser**. To send several apps to the same step, add one option per app pointing to it. A single app's option can also require a minimum app version.

A visit inside an in-app browser matches only in-app browser options, never a browser: an Instagram in-app browser on an iPhone is Instagram, not Safari. A visit in a regular browser matches only browser options. The activity timeline records which in-app browser and version the visit was in.

A common setup sends **Any in-app browser** to a message page that asks the visitor to open the link in Safari or Chrome, and everyone else straight to the destination.

### In the API, MCP and the Assistant

Devices carry `in_app_browser`, `in_app_browser_version` and `in_app_browser_details`. The Browser condition (`EVENT_ACTION_DEVICE_BROWSER_CONDITION`) takes the new `DEVICE_BROWSER_CONDITION_VALUE_*` values and an optional `min_app_version`, and analytics breakdowns take the `in_app_browser` and `in_app_browser_version` dimensions. The Assistant can build the routing for you.

### Instagram and Snapchat visits counted as people

People opening a link inside Instagram or Snapchat were counted as bots, because the bot list matched the app's name. They are counted as people now, past visits included. The apps' own crawlers, such as Snapchat's link preview service, stay bots.

## Limits and caveats

- Recognition relies on the user agent the app sends.
- Linkbreakers detects and routes; it does not force the link to open in Safari or Chrome.
- The Browser condition does not route on the app's language: use the Language condition for that.

## Frequently asked questions

### Which apps are recognized?

Instagram, Facebook, Messenger, Threads, TikTok, Snapchat, LinkedIn, Pinterest, X, WeChat, LINE and the Google app, plus Other in-app browser for unnamed Android webviews.

### Does an Instagram in-app browser match a Safari option?

No. It matches Instagram and Any in-app browser only.

### Do I need a paid plan?

No. It is available on every plan.

### Does it work at the None data collection level?

Routing does. Recording the in-app browser on the device needs Basic or Advanced.