Lorixen.
EN

Deferred deep links: keep the offer through the app install

Short answer: A normal deep link opens a specific screen in your app, such as a product, a booking or a referral offer, but only if the app is already installed. A deferred deep link remembers where the person was going, sends them to the app store to install, and then opens that same screen on first launch instead of a generic welcome. On Android, the Google Play Install Referrer API can carry that context through the install. On iOS there is no direct equivalent, so businesses rely on a linking provider or a sign-in or code-based handover, and anyone still using Firebase Dynamic Links needs a replacement because that service has shut down.

Imagine a customer taps "Get 20% off your first order in our app" in an email. They do not have the app. They go to the store, install it, open it and land on a sign-up screen with no sign of the offer. Many will give up; others will email support asking where the discount went.

The same gap appears with referral links, shared product links, event tickets, QR codes on packaging and links in text messages. Whenever a link is meant for a specific place in the app, losing that context during installation costs conversions and goodwill.

Normal versus deferred

  • Deep link: a URL that opens a particular screen when the app is installed. On iOS this is usually a universal link and on Android an app link, both tied to your website domain.
  • Deferred deep link: the same intent, preserved across the install. The app checks on first launch whether the person arrived through a link and, if so, routes them to the right place.

You still need working normal deep links first. Deferred linking only handles the extra step when the app is missing.

Many apps relied on Firebase Dynamic Links for this. Google's FAQ states that on 25 August 2025, Firebase Dynamic Links shut down: all links it served, on custom domains and page.link subdomains, stop working and new links cannot be created. The FAQ lists the features it provided, including continuing the user's journey after downloading and installing the app via a deferred deep link.

If your app, emails or printed QR codes still use those links, they need replacing. Check old campaigns, packaging and signage as well as current emails.

Android: the Play Install Referrer

On Android, the Google Play Install Referrer API lets your app read information about how it was installed from the Play Store. If the store link included a referrer parameter, for example a campaign ID or a short token identifying the product, the app can retrieve it on first run. The library documentation describes calling getInstallReferrer() to obtain ReferrerDetails and reading the referrer from it.

Two practical points from the same documentation: the install referrer information is available for 90 days and does not change unless the app is reinstalled, and you should call the API only once, during the first run after install.

A simple pattern:

  1. Your web link, such as yourdomain.com/offer/SPRING20, checks whether the device is Android and the app is missing.
  2. It redirects to the Play Store with a referrer parameter containing a short token.
  3. On first launch, the app reads the referrer, looks up the token with your server and opens the offer screen.

iOS: no built-in equivalent

iOS has no install referrer API. Common approaches:

  • A linking or attribution provider that offers deferred deep linking as a service. Compare how each handles privacy, accuracy and pricing before choosing.
  • Account-based handover. If the user must sign in or create an account anyway, store the pending destination against their email or a code on the web, then retrieve it after sign-in.
  • A short code the user enters. For offers and referrals, showing "Your code: SPRING20" on the web page, and prompting for it in the app, is low-tech but reliable.

Avoid fingerprinting techniques that combine device characteristics to guess who someone is; they are unreliable and raise privacy concerns.

Designing the first-run experience

  • Show the context first. If someone came for a product, show it before asking for sign-up, or explain that the offer will be applied after sign-up.
  • Handle failure gracefully. If the link data cannot be retrieved, fall back to a sensible screen and offer a way to enter a code or search.
  • Expire tokens. Offer and referral tokens should be single-use or time-limited where that matters.
  • Measure. Track how many installs arrive with link data and how many reach the intended screen.

Testing

Test on real devices with the app uninstalled: tap the link, install, open, and confirm the destination. Repeat on Android and iOS, from email apps, messaging apps and a QR scanner, because in-app browsers sometimes handle links differently. Test what happens when the person opens the app days later.

A worked example

Picture a hypothetical Sydney meal-delivery business that printed QR codes on flyers offering a free dessert with a first app order. Many people scanned, installed and opened the app, but landed on a generic home screen, and the offer was rarely redeemed.

The team rebuilt the link flow. On Android, the QR link passes a token through the Play Store referrer, read once at first launch to open the offer. On iOS, the landing page shows a short code and the app's first screen asks, "Got a code?" Redemptions rose and support emails about missing offers dropped.

FAQ

Do I need a paid service?

Not necessarily. Android's referrer plus a code-based approach on iOS covers many business needs. A service is worth considering for heavy campaign use.

Will this work if the user installs from a different store?

The Play Install Referrer only covers installs from Google Play. Other stores need their own approach.

Are universal links and app links still needed?

Yes. They handle the common case where the app is already installed.

If customers lose offers or referrals somewhere between your link and your app, tell us where your links appear.

Sources

WhatsAppBook a call