Deep Link Not Received After App Installation

The problem

A store fallback opens and the app installs, but the first launch does not restore the screen or campaign payload from the original link.

A store redirect and a deferred match are different steps. WilderLinks can record a click token for later matching, but the newly installed app must receive that token through a supported platform or app-owned handoff and exchange it. The public tester reports stored configuration only; it does not create a click or test installation.

Before you start

• A saved WilderLinks link with the intended destination and deep-link payload.
• A test build with the appropriate SDK and a planned token handoff for its platform.
• A controlled device test where you can observe the click, install, first launch, and app logs.

Diagnose in order

1. 01WilderLinks

   Confirm the saved route before a device test

   Use the safe tester with the saved WilderLinks URL and selected platform. Confirm the link is active and that the expected route and deferred payload are configured. Do not paste the retired Firebase URL or expect this call to record a click.

   • The tester returns ACTIVE for the intended link.
   • The destination type and deferred-payload status match your saved configuration.
   • Your app profile and store fallback are configured for the relevant platform.
2. 02Your app

   Observe the token path on Android

   For Google Play installs, the native Android SDK can read Play Install Referrer. Flutter, React Native, and Unity need app-side native referrer integration or another supported token handoff; their SDKs do not automatically read the Play referrer. Check that the token is present before calling a match method.

   • The click used a configured Google Play fallback.
   • The install ran through the Play testing or release path being evaluated.
   • The app receives a dl_match_token and passes it to the matching method.
3. 03Your app

   Treat iOS as a separate integration

   The current Swift SDK does not automatically recover a token from the App Store. Clipboard fallback depends on platform behavior and user action, while an attribution provider can supply an explicit token for exchange. An iOS first-install test without a reliable token handoff cannot establish deferred matching.

   • Identify where the token comes from rather than assuming App Store recovery.
   • Check whether clipboard access or provider callback actually delivered it.
   • Only claim a recovered payload when the SDK match result reports matched.
4. 04Your app

   Separate the first launch from navigation

   After a successful match, use the returned destination or payload to navigate. A matched token does not by itself open a screen. If no token was delivered, debug the handoff before changing the link’s route.

   • Record the matched/error state in development logs without logging secrets.
   • Ensure the app does not discard the result during startup.
   • Verify the intended screen exists and can accept the recovered payload.