Deep Link SDKs & API Docs

Clone the SDK repository or add it as a Git submodule, then include the Android library module in your app build.

include(":wilderlinks")
project(":wilderlinks").projectDir = File(rootDir, "../path/to/wilderlinks-sdks/android/wilderlinks")

• minSdk >= 21
• A verified WilderLinks domain
• Android package name and SHA-256 fingerprint

• If you are migrating from an older URLynk integration, replace legacy package names, hosts, and app identifiers with your WilderLinks configuration before testing.
• Use the WilderLinks domain shown on this page and the app profile path prefix attached to your Android app.
• The path prefix here refers to the WilderLinks app profile namespace, not your Android applicationId.

Add Internet permission and place the intent filter inside your launcher activity. Use the exact path prefix configured for the app profile attached to this domain.

<uses-permission android:name="android.permission.INTERNET" />

<activity
    android:name=".MainActivity"
    android:launchMode="singleTop"
    android:exported="true">
    <intent-filter android:autoVerify="true">
  <action android:name="android.intent.action.VIEW" />
  <category android:name="android.intent.category.DEFAULT" />
  <category android:name="android.intent.category.BROWSABLE" />
  <data
    android:scheme="https"
    android:host="your-workspace.wilderlinks.space"
    android:pathPrefix="/x4I9/" />
    </intent-filter>
</activity>

• Create an app from the Apps page.
• Set the Android package name.
• Add SHA-256 fingerprints for debug, release, or Play signing.
• Attach the app profile to the branded domain.

• Initialize your app-side WilderLinks handling as early as possible so incoming links are not missed.
• Call `handleIncomingUri(uri, context)` for every App Link the OS delivers so the SDK sends visitor, device, timezone, OS, and language signals to the resolve API.
• Generate a real deep link from the dashboard, SDK, or API using the same domain and path prefix attached to the Android app profile.
• Open that generated link from adb, Chrome, Notes, or another source depending on the kind of test you are running.

Use this after a Play Store or Internal Testing install. WilderLinks app fallback URLs include `referrer=dl_match_token%3D<token>`, and the SDK exchanges that token for the original payload.

val result = Wilderlinks.checkInstallReferrer(context)
if (result.matched) {
  // result.deepLinkPayload
  // result.destinationUrl
}

The redirect page also attempts a gesture-gated clipboard write. Use this only as a fallback; Play Install Referrer is the primary Android deferred handoff.

val result = Wilderlinks.checkDeferredInstall(context)

Use this when the app is already installed and you want to confirm Android App Links or app-side routing is working.

adb shell am start -a android.intent.action.VIEW -d "https://your-workspace.wilderlinks.space/x4I9/test-link" YOUR_APPLICATION_ID

• Run the app on a physical Android device. Emulator behavior is not reliable for App Links and deferred flows.
• Generate a deep link from the app or dashboard.
• Open the generated link in the device browser. If the app is installed and App Links are verified, Android should open the app.
• If the app is not installed, WilderLinks sends the user to the Play Store with a `dl_match_token` in the install referrer.
• After Play Store installation, launch the app and call the SDK deferred check during startup.
• Confirm the app receives the payload you attached to the link, such as screen name, campaign data, or offer id.

• Publish a test build to a Play Console testing track such as Internal Testing.
• Add the Play App Signing SHA-256 fingerprint to the WilderLinks Android app profile, not just the local debug fingerprint.
• Path: Play Console -> Test and release -> App Integrity -> Play app signing -> Settings -> App Signing key certificate -> SHA-256 fingerprint.
• Wait at least 5 minutes so the Digital Asset Links file can propagate after signing or domain changes.
• Verify the deep link setup inside Play Console under Grow users -> Deep links.
• Use the same Google account on the device that has accepted the Play testing invitation.
• Uninstall any existing build of the app from the device before testing install-time deferred deep linking.
• Open a generated WilderLinks URL in the browser. It should send the user to the Play Store test listing when the app is not installed.
• Install the app from the Play Store test listing.
• Open the app after installation.
• Verify the SDK Play Install Referrer deferred check receives the original deferred payload after first launch.
• The browser page also attempts a gesture-gated clipboard fallback, but Play Install Referrer is the primary Android deferred handoff.
• For direct app opening checks during testing-track development, copy the deep link into a text editor or note-taking app on the device and tap it directly.

• After publishing your app to the Play Store, add the Play App Signing SHA-256 fingerprint from Play Console to the WilderLinks Android app profile.
• This fingerprint is required for reliable direct app opening from Android App Links.
• If browser taps still route to the Play Store during testing-track builds, verify the correct signing fingerprint, domain association, and path prefix before debugging app code.