Deep Linking

Firebase Dynamic Links Alternative: What to Use Now That It's Shut Down

Install₹499

Firebase Dynamic Links shut down on August 25, 2025. Every page.link and custom-domain Dynamic Link stopped working, and new ones can no longer be created. Google recommends Android App Links and iOS Universal Links if you only need to open an installed app, and a deep linking provider if you also need store routing, deferred deep links and click analytics. This guide compares the options feature by feature, shows where TrackerLink fits and where it doesn't yet, and walks through a migration for React Native and Flutter apps.

What happened to Firebase Dynamic Links

Google shut Firebase Dynamic Links down on August 25, 2025. According to Google's deprecation FAQ, links on both page.link subdomains and custom domains stopped working, link metadata was marked for deletion, and the SDK calls now return errors or empty data. The SDKs don't crash your app, but any code that waited for a dynamic link now gets nothing.

If your app still has a Dynamic Links package, or old page.link URLs sit in emails, QR codes or posts, those links are dead today.

What Dynamic Links did, and what you need to replace

Google's own FAQ lists six things Firebase Dynamic Links provided:

  1. Sending users to the right store for their device from one link, with a web page as fallback.
  2. Continuing the user's journey after they download and install the app (a deferred deep link).
  3. Opening the app at the right content when it is already installed.
  4. Analytics for link clicks.
  5. Short links.
  6. Metadata for link previews when the link is shared.

Before you pick a replacement, check which of these your app really used. Many apps only used the third one, and for that the free platform features are enough.

Your three options

1. App Links and Universal Links only

Android App Links and iOS Universal Links are built into the operating systems. A verified link on your domain opens your app directly when it's installed, and your website when it isn't. You host two small files on your domain, assetlinks.json and apple-app-site-association. The App Links and Universal Links generator creates both.

This is free and the most reliable way to open an installed app. What you don't get: store routing, anything that survives the install, and click analytics.

2. A full deep linking provider

For full feature parity, Google suggests providers such as Adjust, Airbridge, AppsFlyer, Bitly, Branch, Kochava and Singular, and notes that it hasn't vetted them. The mobile measurement platforms among them add fraud protection, SKAdNetwork support and ad network integrations. They are built for apps spending on paid acquisition.

3. TrackerLink in notifySphere

TrackerLink is the campaign link in notifySphere. One link sends each device to the right store or opens the installed app, records the click, and credits the install, signup and later events to the campaign. It sits next to push notifications, WhatsApp and Automation in the same dashboard, and notifySphere is free up to 1,000 monthly active users. Here is how it compares, honestly:

Dynamic Links featureApp Links + Universal LinksTrackerLink
Send each device to the right store from one link, with a web fallbackNo. They only open the app or your websiteYes. Store listing or a custom URL per platform, plus a desktop fallback
Open the installed app at the right contentYes. This is what they are forYes, through your app's URI scheme and the link's deep link value (on Android with a Play Store fallback)
Continue the journey after install (deferred deep link)NoAndroid: the campaign and click survive the install through the Play install referrer (exact). iOS: the install is matched to a recent click by IP address or device (less precise). The app gets the campaign, not the screen
Click analyticsNoYes: clicks by country, device and city, installs, signups, and your own events with revenue
Short linksNo. You use your own URLsYes, on notifySphere's domain (no custom domain yet)
Link previews for social sharingOnly what your web page providesYes: your store listing, or a custom title, description and image

When TrackerLink fits: your users are mostly on Android, you want to know which campaign, WhatsApp message or QR code brought each install, and you'd like to follow up with push or WhatsApp in the same tool. When it doesn't yet: you need exact install matching on iOS, new users landing on a specific screen straight after install, links on your own domain, or ad network integrations and fraud checks from a mobile measurement platform.

How the click survives the install on Android

When someone taps a TrackerLink and doesn't have the app, they go to the Play Store with a referrer parameter that carries the click ID (ns_click), the campaign code (cid) and any extra parameters you added to the link. After install, Google Play hands that referrer to the app through the Play Install Referrer API. The notifySphere SDK reads it on first launch and sends the click with the user's registration, so the install, the signup and later events are credited to the campaign. No guessing is involved. On iOS there is no install referrer, so notifySphere matches the first app open to a recent click from the same IP address or device within the attribution window (7 days by default). Deferred deep linking explained covers the mechanics on both platforms.

After a fresh install the SDK gives your app the campaign, not the screen. To send new users to specific content, open the screen based on the campaign or the user's tags in your own code.

Migration checklist

  1. List your old links. Find every page.link or custom-domain Dynamic Link in emails, QR codes, ads, posts and your app. They no longer work, so each one needs a new link.
  2. Remove the Dynamic Links package. Delete firebase_dynamic_links in Flutter or @react-native-firebase/dynamic-links in React Native, and the code that waited for a dynamic link.
  3. Handle links with the platform. Set up a URI scheme, and App Links and Universal Links on your domain, then route incoming URLs with React Native's Linking API or your Flutter router.
  4. Add the notifySphere SDK (React Native or Flutter 1.2+) so installs and events are attributed. Send conversions with postEvent.
  5. Create a TrackerLink for each old link in Engage → TrackerLink: campaign name, media source, deep link value, store fallbacks, web fallback and link preview. See the TrackerLink docs.
  6. Replace the links everywhere, including printed QR codes, and test: tap each link with the app installed and without it, on Android and iPhone.
  7. Watch the results in Attribution campaigns: clicks, installs, signups and revenue per link.

Notes for React Native and Flutter

  • React Native: the notifySphere SDK reads the Play install referrer on Android through react-native-install-referrer, which is a peer dependency. Opening screens from links stays in your navigation code.
  • Flutter: flutter_notify_sphere 1.2 and later reads the referrer when useReferral is true (the default) and adds the click to the user's tags at registration, so always pass a tags map to registerUser(). The Flutter push notifications guide shows the setup.

Frequently asked questions

When did Firebase Dynamic Links shut down?

On August 25, 2025. Google's FAQ says all links served by Firebase Dynamic Links, both on custom domains and on page.link subdomains, stopped working, and new links can no longer be created.

What does Google recommend instead of Firebase Dynamic Links?

For deep links into an app that is already installed, Google recommends Android App Links and iOS Universal Links. For full feature parity, including deferred deep links and analytics, it points to deep linking providers such as Adjust, Airbridge, AppsFlyer, Bitly, Branch, Kochava and Singular.

Do my old page.link links still work?

No. Since the shutdown they no longer open your app or redirect anywhere. Any page.link URL printed on a QR code, in an email or in an old post needs to be replaced with a new link.

Are App Links and Universal Links enough?

They are enough if you only need to open the app when it is already installed. They don't send users to the store, don't remember the link through an install, and don't give you click analytics. For those you need a link provider.

Is TrackerLink a full replacement for Firebase Dynamic Links?

On Android it covers the main jobs: store routing, opening the installed app, carrying the campaign through the install, analytics, short links and link previews. On iOS it opens the installed app, routes to the App Store, and matches installs to clicks by IP address or device, which is less precise than Android. Links use notifySphere's domain rather than your own.

What happens to firebase_dynamic_links and @react-native-firebase/dynamic-links?

They depended on the shut-down service, so they no longer return links. Remove them from your app and handle incoming links with your platform's own deep link handling, such as React Native's Linking API or a Flutter deep link package.

Next steps

Compare TrackerLink with a full provider in notifySphere vs Branch.io, or read the TrackerLink docs to create your first link.