Skip to main content
Mobile Apps and deferred mobile attribution are in Public Beta. Test the complete Google Play or TestFlight installation flow before using mobile attribution in production.
Workspace owners manage native applications from Workspace settings → Mobile Apps. A Mobile App connects one or more verified custom domains to an iOS app, an Android app, or both.

​
Before you create an app

Connect the custom domain first and wait until Biqli shows verified DNS and active HTTPS. New Mobile App remains unavailable until an eligible domain exists. Collect the platform identifiers:
  • iOS: Apple Team ID, bundle ID, and public apps.apple.com App Store URL;
  • Android: package name, Google Play destination, and the SHA-256 signing-certificate fingerprints for every build that must verify against the domain.

​
Register the app

  1. Open Workspace settings → Mobile Apps.
  2. Select New Mobile App.
  3. Enter an app name and choose from one to twenty available custom domains.
  4. Enter up to fifty allowed path rules per domain, one per line. A rule starts with one /, contains no query or fragment, is at most 500 characters, and may end in *. The default /* allows every path on that hostname.
  5. Complete at least one platform:
    • for iOS, enter the ten-character uppercase Apple Team ID, bundle ID, and App Store URL;
    • for Android, enter the package name, at least one uppercase colon-separated SHA-256 certificate fingerprint, and the matching Google Play URL.
  6. Choose the exact handoff lifetime from 15 minutes to seven days. The default is 24 hours.
  7. Leave Probabilistic iOS fallback off unless your privacy review and consent flow approve it.
  8. Save the app.
The detail page displays the public biq_mapp_... app ID and biqli_mobile_pk_... key used by the native SDK. This key cannot manage the workspace or read analytics; never substitute a browser biqli_pk_... key or secret biqli_... workspace key.

​
Publish association files

Use Preview association files to inspect the expected documents, then Verify public files to check what the domain currently serves:
Generated mode includes active apps attached to that exact hostname and is recommended. In Custom domains → your domain → Advanced settings, custom mode lets you replace either document with your own JSON. Custom JSON replaces the generated document completely; it is not merged with Mobile App entries. Enable Apple App Site Association for iOS and Android Asset Links for Android in those domain settings. A disabled document is not publicly served, even when the Mobile App contains the corresponding platform. The file must return HTTPS status 200 directly with application/json and no redirect. Each exact hostname needs its own file. Changes can remain cached by Apple or Android after Biqli verification succeeds. Each document may be at most 128 KB and contain at most 100 application entries. An Apple entry supports up to 20 app IDs. An Android entry supports up to 20 SHA-256 certificate fingerprints. Biqli rejects a save that would make a generated or custom document exceed these limits.

​
Configure Deep View

Open the custom domain’s advanced settings and enable Deep View when iOS users without the app should receive the exact deferred handoff experience. Configure the headline, description, button label, and light, dark, or system theme. The individual short link must also have iOS Deep View enabled. Both switches are required.

​
Rotate the mobile key

Rotate the key from the Mobile App detail page when you need a new active mobile publishable key.
  1. Select Rotate key.
  2. Copy the new biqli_mobile_pk_... value into the next app build.
  3. Confirm resolution works with the new build.
  4. Complete rollout before the previous key’s configured overlap period ends.
Rotation does not change the Mobile App ID, platform identifiers, domain, or analytics history. Do not rotate merely to hide a public key; rotate when you need to end use of an older distributed credential.

​
Disable or delete an app

Edit the Mobile App and turn off Active to stop new mobile resolutions while preserving its configuration. Re-enable it after correcting the configuration. Deleting the Mobile App is permanent. It revokes its mobile keys, prevents outstanding unresolved handoffs from resolving, and removes the app from Biqli-generated association files. Preview the affected hostname and coordinate the removal with every released app before confirming deletion. The current dashboard exposes key rotation and permanent app deletion, not a separate reversible Revoke all keys action. Disable the app for a temporary stop. Delete it only when you intend to revoke every key and remove its domain associations permanently.

​
Read attribution analytics

The detail page shows a rolling 30-day summary: Recent events show the resolution method, confidence, first-open state, SDK version, and date. A cached SDK result does not create another open. Mobile-open events are not delivered as webhooks.

​
Next steps