Skip to main content
Mobile deep linking is in Public Beta. Complete the store-install tests in Testing and troubleshooting before production use.
This procedure creates one verified HTTPS link that can open your installed app and preserve attribution through a supported store install.

​
Before you begin

You need:
  • workspace owner access;
  • a custom domain with verified DNS and active HTTPS in Biqli;
  • the iOS bundle ID and ten-character Apple Team ID for iOS;
  • the Android package name and SHA-256 signing-certificate fingerprints for Android;
  • a public apps.apple.com URL for the Mobile App, an optional per-link TestFlight fallback for testing, and a Google Play URL for Android; and
  • an in-app route that your application can validate and handle.
You may register iOS, Android, or both. At least one complete platform configuration is required.

​
1. Register the Mobile App

Open Workspace settings → Mobile Apps, select New Mobile App, and enter: Save the app, then copy its biq_mapp_... app ID and biqli_mobile_pk_... mobile publishable key. The key is public and app-scoped, but you should still avoid posting it outside the application and documentation where it is needed.

​
2. Publish and inspect association files

Biqli can generate both files from the active Mobile Apps attached to the exact hostname:
Open the Mobile App detail page and use Preview association files, then Verify public files. Each URL must return the canonical JSON directly with HTTPS status 200, an application/json content type, and no redirect. Generated mode is recommended. Custom mode replaces the generated JSON completely; Biqli does not merge custom entries with registered apps. Every exact hostname needs its own association file.

​
3. Configure the native application

For iOS, add applinks:go.example.com to the target’s Associated Domains capability and forward NSUserActivityTypeBrowsingWeb URLs to Biqli. See the iOS SDK reference. For Android, add an HTTPS VIEW intent filter with DEFAULT, BROWSABLE, and android:autoVerify="true" for the domain. See the Android SDK reference. Do not place a secret biqli_... workspace API key in either app. Native apps use only the Mobile App ID and biqli_mobile_pk_... key. Create or edit a short link on the same custom domain and open Mobile Deep Linking & Deep View.
  1. Enable Mobile Deep Linking.
  2. Select the registered Mobile App.
  3. Enter the in-app route, such as /invite/accepted.
  4. Add an optional referral code and a safe metadata JSON object.
  5. List only the dynamic query keys you intend to forward.
  6. Optionally override the Mobile App’s platform store fallback URLs for this link.
  7. Enable iOS Deep View when you need exact iOS deferred attribution.
  8. Save the link.
The route must begin with /, contain no query or fragment, contain no double slash, and be no longer than 500 characters. Treat it as untrusted input in the app: map recognized routes to safe screens instead of executing arbitrary actions. Read Configure mobile deep linking for every dashboard field and limit.

​
5. Install and configure an SDK

Android:
iOS Swift Package Manager URL:
Select version 1.0.0 or later within the same major version. Configure the SDK once at application startup and pass incoming verified links through the platform lifecycle methods. Keep attribution non-blocking: an offline or transient failure can retry on a later cold launch.

​
6. Verify the result

Test the installed-app path first. A successful request returns matchedBy: exact_app_link, the configured route, and the link attribution. Then perform the real deferred-install tests through Google Play and TestFlight. Success means:
  • the operating system opens the installed app for the verified hostname;
  • a device without the app reaches the correct store;
  • the first launch can return the expected exact deferred match after the required handoff;
  • the app routes only recognized paths;
  • the backend verifies a signed attribution receipt before granting a reward; and
  • Mobile App analytics show the new resolution event.

​
External platform references