Firebase Dynamic Links was deprecated by Google on 25 August 2025. Since then, any app still relying on Firebase Dynamic Links for routing users into specific in-app screens has been operating with broken link chains, degraded deferred deep link performance, and attribution gaps that may not have surfaced clearly in dashboards yet.

This is not a planning document. Firebase Dynamic Links is already shut down. If your app has active campaigns, CRM sequences, push notifications, or QR codes pointing to Firebase Dynamic Links URLs, those links are currently misbehaving, and that misbehaviour is silently costing you installs, conversions, and attribution accuracy.

This guide covers exactly what breaks, what you need to audit, and how to execute a clean migration to a production-ready alternative.

Firebase Dynamic Links Is Gone: What This Actually Means for Your App

Google gave developers approximately one year of notice before shutting down Firebase Dynamic Links, but many teams assumed the deprecation meant the service would gradually degrade or that Google would keep basic routing alive. That assumption turned out to be incorrect.

What "shut down" means in practice:

• New dynamic links can no longer be created via the Firebase console or the Dynamic Links API

• Existing dynamic links that were previously working may now return errors, route to unexpected destinations, or fail to trigger deferred deep link resolution

• The SDK components related to Dynamic Links in the Firebase Android and iOS SDKs no longer receive updates and are producing integration errors in newer Xcode and Android Studio builds

• Firebase provides no migration path to a first-party replacement. Their recommendation is to build a custom solution or use a third-party deep linking platform

For teams that built deep linking infrastructure on Firebase Dynamic Links as a free, low-maintenance foundation, this is a forced migration with no graceful fallback.

What Breaks When Firebase Dynamic Links Stops Working

The failures are not always immediately obvious, particularly if your team does not have visibility into the full routing chain from click to in-app destination.

Campaign links in active paid media. Any Meta, Google, TikTok, or other paid ads with Firebase Dynamic Links destinations will be routing to a broken or fallback URL. Users may land on a web page instead of your app, or see a generic app store page with no in-app context after installing.

Deferred deep link chains are broken. One of the primary benefits of Firebase Dynamic Links was deferred routing: new users who tapped a link before installing would be taken to the correct in-app screen post-install. This mechanism is no longer functioning. New installs from any channel using Firebase Dynamic Links URLs will open to your app's default home screen, losing the campaign context entirely. The downstream effect on conversion funnels is significant. This is exactly the problem that reliable deferred deep linking was built to solve, and it is now broken for any team still on Firebase.

CRM and push notifications. Any deep links embedded in email campaigns, push notifications, or WhatsApp/SMS sequences that were created using Firebase Dynamic Links are affected. Users tapping those links may land on a browser page or receive an error depending on how the routing fails.

QR codes pointing to Firebase Dynamic Links domains. Physical QR codes on packaging, menus, events, or out-of-home advertising that encoded Firebase Dynamic Links URLs cannot be updated retroactively. This is the most painful failure mode because the fix requires printing new materials.

Attribution is now missing for those flows. Because Firebase Dynamic Links provided no real attribution data, teams using it may not immediately realise how much of their install volume was attributed through Firebase routing. Moving to a proper attribution-integrated deep linking platform will make those gaps visible for the first time.

Audit Checklist: Mapping Your Current Firebase Dynamic Links Usage

Before migrating, you need a complete picture of everywhere Firebase Dynamic Links appears in your product and marketing stack. Use this checklist to inventory the scope.

SDK references:

• Search your codebase for firebase.dynamicLinks or DynamicLinks imports

• Check your Podfile (iOS) and build.gradle (Android) for Firebase Dynamic Links dependencies

• Review your app delegate or MainActivity for Dynamic Links handling code

Domain inventory:

• List all page.link or custom Firebase Dynamic Links domains your app uses

• Identify any custom domains configured via Firebase that point to Dynamic Links routing

Campaign and marketing channels:

• Audit all active paid campaigns for Firebase Dynamic Links destination URLs

• Check email templates in your CRM platform for embedded Firebase links

• Review push notification templates for Firebase deep link strings

• Check WhatsApp/SMS templates

• Identify any QR codes in active physical materials

App store listings:

• Check if your App Store or Play Store listing description or preview links use Firebase Dynamic Links URLs

Organic and social channels:

• Review your app's bio links on Instagram, LinkedIn, or similar profiles

• Check any pinned posts or content with embedded Firebase links

This audit typically surfaces 3 to 5 distinct integration points beyond the obvious paid campaigns. The QR code and CRM channels are most commonly overlooked and carry the longest remediation timelines.

Evaluating Alternatives: What to Look for in a Firebase Dynamic Links Replacement

Firebase Dynamic Links was attractive primarily because of its zero cost and Google ecosystem integration. Any replacement should be evaluated on the criteria it was actually weak on, not just the price point.

Deferred deep linking reliability on iOS post-ATT. Firebase Dynamic Links used device fingerprinting for deferred resolution, which is restricted under Apple's ATT framework. A modern replacement should use deterministic attribution methods (click-through attribution with validated device IDs where consent is given) and handle the probabilistic fallback correctly.

Attribution integration. Firebase Dynamic Links provided essentially no attribution data beyond basic click counts. If you are replacing it, the opportunity exists to add proper campaign attribution at the same time, connecting link clicks to installs, events, and revenue. Running a deep linking tool that still provides no attribution means replacing one measurement gap with another.

Custom domain support. Firebase allowed custom domains, which many teams configured. Your replacement should support custom domains to avoid having to update all existing links to a new domain at the moment of migration.

Pricing predictability. The shift from a free tool to a paid one requires a clear usage-based pricing model. Seat-based enterprise pricing is difficult to justify for teams that were previously paying nothing.

Migration support. A credible platform should provide documentation and tooling for migrating from Firebase Dynamic Links specifically, not just generic onboarding.

For context on how the broader deep linking tool landscape looks in 2026, the guide on best deep linking tools for mobile apps covers eight platforms with a features and pricing comparison.

Option 1: Linkrunner (Unified Deep Linking + Attribution)

Linkrunner is the platform most directly positioned as a Firebase Dynamic Links replacement for growth-stage apps. It provides dynamic and deferred deep linking by default, unified with full campaign attribution in a single product.

The key advantage over Firebase Dynamic Links is not just that routing works, but that every link click is connected to an install, an in-app event, and a revenue outcome. The measurement gap that Firebase Dynamic Links always had is closed from day one.

Pricing starts with 25,000 one-time free attributed installs, then tiered usage-based billing from $0.012 to $0.007 per install depending on volume. There are no seat limits and no separate charges for deep linking. Custom domain setup, AASA and assetlinks.json hosting, and SSL are managed inside the platform.

For teams migrating from Firebase Dynamic Links, Linkrunner's SDK replaces the Firebase Dynamic Links SDK directly. The Firebase Dynamic Links-specific code (DynamicLinks handling, link resolution callbacks) is replaced with Linkrunner's equivalent, which is a straightforward substitution for most app architectures.

Linkrunner's own Firebase Dynamic Links migration page at linkrunner.io/firebase-dynamic-links covers the specific SDK swap steps.

Option 2: Branch (Deep Linking Focused)

Branch is the most established pure deep linking platform and a natural comparison for teams evaluating Firebase Dynamic Links replacements. It handles deferred deep linking reliably, has mature documentation, and supports complex link management scenarios.

The limitations: Branch does not provide campaign attribution by default. You get link performance data (clicks, opens, installs attributed to Branch links) but not the full funnel from click to revenue event and ROAS by campaign. Teams that want proper attribution alongside deep linking will need a separate MMP, which means paying for two platforms.

Branch's pricing is enterprise-focused with custom contracts. Cost predictability before signing is difficult, particularly for teams under Series A.

Option 3: AppsFlyer OneLink (Enterprise Attribution + Links)

AppsFlyer OneLink is the deep linking layer inside the AppsFlyer MMP. For teams that need enterprise-grade attribution depth across many channels and are willing to pay enterprise pricing, OneLink provides tight integration between link performance and campaign attribution data.

The cost is the primary constraint. AppsFlyer pricing typically amounts to ₹3 to 8 per install equivalent at scale, which is a significant shift from a free tool. Teams should run the total cost of attribution infrastructure analysis before committing.

For teams already on AppsFlyer for attribution who were using Firebase Dynamic Links as a supplement, migrating to OneLink is the simplest consolidation path.

Option 4: Custom Implementation (When DIY Makes Sense)

Some teams evaluate building a custom deep linking solution using Universal Links (iOS) and App Links (Android) directly, with a server-side redirect layer for deferred routing.

This is technically feasible but carries ongoing maintenance costs that are frequently underestimated at planning time. A reliable deferred deep link implementation requires a server that stores the original link context, resolves it post-install, handles edge cases across iOS and Android versions, and updates as Apple and Google change their routing specifications. Teams that have built this in-house consistently find the ongoing maintenance cost exceeds the cost of a commercial platform within 12 to 18 months.

DIY makes sense for teams with very specific routing requirements that no commercial platform supports, or for very large engineering organisations where platform independence is a strategic requirement. For the majority of growth-stage apps, a commercial platform delivers better reliability at lower total cost.

Frequently Asked Questions

Are my existing Firebase Dynamic Links completely broken?

Post-deprecation behaviour varies by link type. Some links may fall back to the App Store or Play Store without deep link context. Others may return errors. The deferred deep link resolution mechanism is no longer functioning. Treat existing Firebase Dynamic Links as broken until verified otherwise.

Can I extend the life of my Firebase Dynamic Links URLs?

There is no official way to extend Firebase Dynamic Links. Setting up redirect rules from Firebase domains to your new platform URLs is the most practical way to handle in-flight links that cannot be updated immediately.

How long does the migration take?

For most growth-stage apps, the technical migration (SDK swap, link recreation, CNAME update) takes 1 to 2 weeks of engineering time. The channel audit and template update work runs in parallel and typically takes another 1 to 2 weeks depending on how many channels are affected.

Do I lose historical analytics data from Firebase Dynamic Links?

Yes, Firebase Dynamic Links analytics data remains in the Firebase console but will not be importable into your new platform. Document any historical click and install data you need from Firebase before the console access is affected.

Does migrating to a paid platform affect my app's pricing significantly?

For teams under 25,000 monthly installs, Linkrunner's free tier covers the migration at no cost. For higher volumes, transparent usage-based pricing at $0.012 per install means a team driving 50,000 monthly installs pays approximately $600 per month, in exchange for proper attribution, deferred deep linking, fraud protection, and campaign intelligence that Firebase Dynamic Links never provided.

If you are mid-migration or starting the process now, request a demo from Linkrunner to walk through the Firebase-specific migration path. The setup is faster than most teams expect, and the attribution visibility you gain in the process is typically more valuable than the routing fix alone.