In August 2025, Google officially shut down Firebase Dynamic Links, ending a free service that millions of mobile apps had quietly built their marketing operations on top of. For some teams, the migration was planned and smooth. For others, it meant waking up to broken campaign links, missing attribution, and users landing on app store pages instead of the content they clicked on.
If your company uses mobile apps in its digital marketing strategy, the Firebase sunset was not just a developer problem. It was a marketing operations problem. This guide covers what happened, what it means for your campaigns, and how to evaluate a replacement that actually fits your team.
1. What Firebase Dynamic Links actually did for marketing teams
Most marketers knew Firebase Dynamic Links as the thing that made app links work. But the mechanism underneath was more specific than that, and understanding it helps explain why replacing the service is non-trivial.
Standard deep links vs. deferred deep links
A standard deep link sends a user who already has your app installed directly to a specific screen inside the app. Tap a promotional email link for a sale, and instead of landing on the home screen, you arrive at the exact product page. That is standard deep linking.
Deferred deep linking goes a step further. If the user does not yet have the app installed, the link first routes them to the App Store or Google Play. After they install the app and open it for the first time, they are taken directly to the content they originally clicked on, rather than landing on a generic onboarding screen. Firebase Dynamic Links handled both scenarios in a single link.
Where marketing teams relied on this
The practical applications were everywhere across email marketing campaigns, SMS flows, social media promotions, referral programs, and QR codes. Any touchpoint where you wanted to move a user from a browser or messaging context into a specific part of your app was using some form of deep link.
Referral programs were especially dependent on dynamic links. A user sharing an invite link needed that link to carry context (their referral ID, the promotion being shared) through the install process and into the first app session. Firebase Dynamic Links made this straightforward without requiring a custom backend.
2. The timeline of the shutdown
Google announced the deprecation of Firebase Dynamic Links in August 2023, giving teams approximately two years to migrate. The official Firebase Dynamic Links FAQ and sunset notice outlined the timeline and confirmed that all existing links would stop functioning after August 25, 2025.
The notice was clear, but the impact was widely underestimated. Many teams only realized the depth of the problem when they began auditing exactly how many links, campaigns, and onboarding flows had Firebase Dynamic Links baked in. For companies that had been growing for several years, the answer was often: far more than expected.
Why many teams were caught off guard
Firebase Dynamic Links had been embedded in marketing stacks so seamlessly that engineers and marketers alike had stopped thinking about them as a managed service with an expiry date. The links were free, they required minimal maintenance, and they worked reliably. That invisibility became the problem when the shutdown notice arrived.
Teams also underestimated migration timelines. Moving deferred deep linking logic to a new provider requires coordination between mobile engineers, backend developers, and marketing operations teams. For companies with larger apps and complex attribution setups, six months was not always enough time.
3. How the shutdown affected specific marketing workflows
Email and SMS campaigns
Promotional emails and text messages that contained Firebase Dynamic Links began failing after the cutoff date. Users clicking those links encountered 404 errors or were routed to generic landing pages rather than the in-app content they expected. Reactivation campaigns were particularly affected, since archived link templates from previous campaigns still contained the old URLs.
Referral and sharing programs
Referral programs built on Firebase Dynamic Links lost the deferred deep linking functionality that makes them effective. When a new user installs the app through a referral link, the system needs to carry the referrer’s ID through the install process and attribute it correctly. Without that mechanism, referral credit breaks, users see no personalized onboarding, and lead generation funnels built around referral incentives stop converting.
Re-engagement and retargeting
Re-engagement campaigns rely on sending lapsed users a link that takes them back to a specific piece of content or an incomplete action inside the app. Without deep linking, those campaigns can only bring users to the app home screen, which dramatically reduces re-engagement rates. Teams that had been running Firebase-based retargeting had to rebuild those workflows from scratch before their next campaign cycle.
QR codes and physical marketing
QR codes in print materials, packaging, and physical signage that pointed to Firebase Dynamic Links became dead ends overnight. Replacing them required printing new materials or covering old QR codes, which represented a real cost for companies in retail, events, and consumer products.
4. What to look for in a replacement
Choosing a replacement is not just a technical decision. It involves marketing operations, analytics needs, budget, and how much engineering time you want to invest in the integration.
Core technical requirements
- Deferred deep linking: the link must carry context through an app install
- iOS Universal Links and Android App Links support
- Apple Universal Links compliance for iOS 14 and later (required to avoid falling back to Safari)
- Custom domain support so links match your brand
- Fallback URL control for web-only users
- Link analytics and click tracking
Marketing and operational requirements
- Link creation via dashboard, API, or bulk upload (not just code)
- UTM parameter pass-through for campaign attribution
- No-code or low-code options for the marketing team to create links independently
- QR code generation integrated into the link creation flow
- Predictable, flat-fee pricing that does not scale with monthly active users
That last point matters more than it appears. Several enterprise attribution platforms charge based on monthly active users (MAU), which means your marketing automation costs rise every time a campaign performs well. For growth-stage and mid-market companies, MAU-based pricing can become a significant constraint as the product scales.
5. Comparing your options in 2026
There are broadly three categories of solutions teams have moved to since the Firebase sunset. Each makes different tradeoffs between depth of integration, pricing, and the amount of engineering work required.
Enterprise attribution platforms (SDK-based)
Branch.io, AppsFlyer, and Adjust all require SDK integration into your iOS and Android apps. They are powerful for companies whose primary need is mobile attribution alongside deep linking, but SDK integration takes engineering sprints, and pricing scales with monthly active users or tracked events, which makes costs unpredictable as your app grows.
JotURL: SDK-free deep linking with flat-fee pricing
For marketing teams that need to move fast without heavy engineering involvement, JotURL is one of the most practical Firebasedynamic links alternative options available today. It handles deferred deep linking, Universal Links, and App Links without requiring any SDK integration in your app. Setup is done through a dashboard rather than code, which means the marketing team can create and manage links independently.
Native Universal Links and App Links (DIY)
For teams with dedicated mobile engineering resources, Android App Links and Apple Universal Links can be implemented without a third-party service. The limitation is that the native approach only handles standard deep linking (app already installed). Deferred deep linking requires additional custom backend logic, which adds ongoing maintenance that most marketing teams prefer to avoid.
6. Migration checklist for teams still on Firebase links
If you have not yet completed your migration from Firebase Dynamic Links (or if you inherited a codebase that still contains references to the old service), the following checklist covers the main steps.
- Audit all existing Firebase Dynamic Links across your codebase, email templates, SMS flows, and QR codes.
- Identify which links require deferred deep linking vs. standard linking only.
- Select a replacement tool based on your attribution needs, team structure, and pricing tolerance.
- Set up your AASA file (iOS) and assetlinks.json (Android) on your domain.
- Test deferred deep linking flows end-to-end on both platforms before going live.
- Replace old Firebase links in live email templates and active campaign assets.
- Update or reprint QR codes in any physical materials that still reference Firebase URLs.
- Archive old links and document the mapping from old Firebase URLs to new ones for internal reference.
Frequently Asked Questions
Did Firebase Dynamic Links fully stop working in August 2025?
Yes. Google confirmed that Firebase Dynamic Links stopped functioning after August 25, 2025. Any app or marketing workflow still relying on the old links will need to be migrated to a working replacement. There is no grace period extension available from Google.
Do I need an SDK to replace Firebase Dynamic Links?
No. SDK-based platforms like Branch.io and AppsFlyer require SDK integration into your iOS and Android apps, but tools like JotURL offer SDK-free deep linking. These platforms configure deep linking behavior through server-side setup and domain configuration rather than a device-level SDK, which reduces the engineering effort required significantly. For marketing teams that need fast campaign turnaround, SDK-free solutions often offer a better fit.
What is deferred deep linking and why does it matter for marketing?
Deferred deep linking allows a link to carry context (such as a referral ID, a promotion, or a specific product page) through the process of installing an app. When the user first opens the app after installing it, they are taken directly to the intended content rather than a generic home screen. This is important for referral programs, welcome campaigns, and any scenario where you want to personalize the first-time user experience based on what the user clicked before they had the app.
How long does it take to migrate from Firebase Dynamic Links to a new platform?
The timeline depends on the complexity of your app and how deeply Firebase Dynamic Links are embedded in your workflows. For teams with a focused use case (email campaigns and basic referral links), a migration can take one to three weeks, including testing. Teams with complex attribution setups, multiple apps, or legacy code using older Firebase SDK versions should budget four to eight weeks and include time for QA on both iOS and Android before launching any campaigns on the new system.
Can I keep using Firebase for other services even after Dynamic Links shuts down?
Yes. The shutdown of Firebase Dynamic Links does not affect other Firebase services such as Firestore, Firebase Authentication, Firebase Crashlytics, or Firebase Cloud Messaging. Only the Dynamic Links product was discontinued. You can continue using the rest of the Firebase ecosystem without interruption, and simply replace the deep linking component with a dedicated tool.
Are there free alternatives to Firebase Dynamic Links?
Implementing native Universal Links (iOS) and App Links (Android) without a third-party platform is technically free, but it requires development work and only covers the standard deep linking case. Deferred deep linking (context through a fresh install) requires additional custom backend logic if you want to avoid a paid service. For most marketing teams, the cost of developer time to build and maintain a DIY solution exceeds the cost of a paid tool within the first year.
What is the best way to handle QR codes that point to Firebase Dynamic Links?
QR codes are static images generated at a specific URL. Any QR code that points to a Firebase Dynamic Link URL will now produce an error. The practical options are: generate new QR codes pointing to your replacement deep link URLs, use a QR code redirect service that lets you update the destination URL without reprinting, or, for physical materials already in circulation, place a redirect at the old URL domain if you control it. Most deep link platforms include QR code generation as part of their link creation tools, which simplifies this for future campaigns.
Final Thoughts
The Firebase Dynamic Links shutdown was a significant disruption for any company that built mobile marketing workflows around a free platform. The good news is that the replacement ecosystem is mature. Whether your team needs full mobile attribution, a lightweight link generator, or a DIY implementation using platform-native APIs, there are well-tested options available in 2026.
The teams that handle this transition best are the ones that use the moment to audit their entire mobile linking setup, not just patch the immediate Firebase dependency. Understanding exactly where deep links appear in your campaigns, which flows require deferred linking, and what data you actually need from those links gives you a clearer picture of which replacement fits your real needs. For software companies running growth and engagement campaigns, getting this infrastructure right has a direct impact on campaign performance. Mobile users who click a link and land exactly where they expected to go convert at meaningfully higher rates than those who land on a home screen and have to navigate from there. That gap is what a good deep linking infrastructure protects.
