Mobile deep linking

Mobile deep linking and deferred mobile attribution are in Public Beta. Verified links and local SDK tests are complete. Validate Android deferred installation through a Google Play test track and iOS deferred installation through TestFlight before relying on either path in production.

Biqli uses one HTTPS short link to open installed mobile apps, send people without the app to the correct store, and return the link’s in-app route and attribution data after installation. The Biqli Android SDK supports Android API 23 and later. The Biqli iOS SDK supports iOS 15 and later.

What you configure

Mobile linking connects four resources:

A verified custom domain that serves the platform association files.
A Biqli Mobile App containing the iOS and Android identities, path rules, and a public mobile publishable key.
A Biqli short link containing its route, referral data, safe metadata, permitted dynamic query keys, and store fallbacks.
The Biqli SDK in your app, which submits a mobile-open request and routes the returned result.

Read the quickstart to configure these resources in order.

Resolution behavior

Situation	Visitor experience	Resolver match
Installed iOS app and verified Universal Link	iOS opens the app directly	`exact_app_link`
Installed Android app and verified App Link	Android opens the app directly	`exact_app_link`
Android app not installed	Biqli adds an opaque handoff to the Google Play Install Referrer and redirects to Google Play	`exact_install_referrer` after installation
iOS app not installed, Deep View enabled on the domain and link	A Deep View asks the person to continue; after installation, the person uses the app’s explicit paste control	`exact_handoff`
iOS first open with explicit consent and probabilistic matching enabled	Biqli accepts one unambiguous recent candidate for the verified domain	`probabilistic`, or `none` if ambiguous
Desktop, crawler, bot, or unsupported device	The link follows its ordinary web redirect behavior	No mobile-open request
Mobile link disabled, inactive, expired, or unavailable	Biqli follows the applicable ordinary redirect, expired-link, or unavailable-link behavior	No mobile handoff is created

Deep View must be enabled in both the custom-domain settings and the individual link. If either switch is off, iOS uses the configured store fallback without an exact deferred handoff.

Match types and confidence

`matchedBy`	Confidence	Meaning
`exact_app_link`	`exact`	The installed app supplied the verified HTTPS link.
`exact_install_referrer`	`exact`	Android supplied the opaque handoff through Google Play Install Referrer.
`exact_handoff`	`exact`	iOS supplied the opaque handoff through an explicit user-initiated paste.
`probabilistic`	`probabilistic`	An opted-in iOS first open matched exactly one eligible recent candidate.
`none`	`none`	No eligible match was found. This is a successful resolution, not an error.

Exact matching takes priority over probabilistic matching. A request containing an exact handoff and an installed-app link that identify different links is rejected instead of choosing one.

Where results appear

The SDK and POST /v1/track/open return the resolution immediately. The Mobile App detail page shows aggregate 30-day analytics and recent resolution events. Biqli does not emit a mobile-open webhook. Use the SDK or resolver response for application behavior and Mobile App analytics for reporting. Do not invent a webhook dependency in your integration.

GETTING STARTED

BROWSER TRACKING