You need a full MMP.
If Dynamic Links was a small part of a larger measurement stack, Branch, AppsFlyer, or Adjust give you ad network attribution, SKAdNetwork support, and fraud tooling that Ferry does not have.
Google shut Dynamic Links down. Ferry does the same jobs on platform standards you control: route users into the right screen, keep context through install, and show which links produce revenue.
Ferry is a drop-in Firebase Dynamic Links replacement for iOS, Android, Flutter, and React Native apps. It covers deep links, deferred deep linking, custom domains, and link-level attribution on flat monthly pricing from $9. It is not a full mobile measurement platform; if you need ad network attribution and fraud tooling, an MMP is the better fit.
Firebase Dynamic Links covered a lot for free. This is an honest map from what it did to what Ferry does today.
| Capability | Firebase Dynamic Links | Ferry |
|---|---|---|
| Deep links | Shut down on August 25, 2025. Custom-domain and page.link links are no longer served. | Universal Links and App Links with store routing and a web fallback, served from one hostname. |
| Deferred deep links | Supported before the shutdown. No longer available. | Yes. Server-side matching returns the original link payload with a method and a confidence level on every match. |
| Attribution | Basic link analytics through the Firebase console. No longer available. | Link-level attribution: installs, signups, purchases, and revenue by link and campaign. Not a full MMP. |
| SDKs | iOS, Android, Flutter, React Native, and Unity SDKs, all deprecated. | Swift, Kotlin, Flutter, and React Native SDKs, plus a plain HTTP API for anything else. |
| Custom domains | Supported before the shutdown. Custom domains and page.link subdomains both stopped resolving. | One custom domain per project on Launch and above. Every plan includes a shared feryl.io subdomain. |
| Pricing model | Free while it existed. | Flat monthly tiers by link opens: $0 to $299 per month for 5,000 to 3,000,000 opens. 14-day trial, no free tier. |
| Self-serve signup | Yes, through the Firebase console, now removed. | Yes. Sign up, create a project, ship. No sales call at any tier. |
Google documents the shutdown in the official Dynamic Links FAQ at firebase.google.com/support/dynamic-links-faq.
FDL is gone, so the question is which replacement fits. Ferry is built for indie developers and small teams who need links, not a measurement platform.
If Dynamic Links was a small part of a larger measurement stack, Branch, AppsFlyer, or Adjust give you ad network attribution, SKAdNetwork support, and fraud tooling that Ferry does not have.
If nothing routes into an app, you do not need deep linking at all. A plain URL shortener or your own redirects are simpler and cheaper.
Ferry ships SDKs for Swift, Kotlin, Flutter, and React Native, and an HTTP API for the rest. If you need first-party Unity or desktop SDK support, the larger platforms cover more surface.
Move the journeys that still have users behind them first. The full step-by-step walkthrough covers link inventory, payload mapping, and SDK swap details.
Start with links still live in campaigns, QR codes, email, packaging, referrals, and product flows. Dead historical links with no users behind them can wait.
Create a Ferry project, choose a hostname, preserve the slugs worth preserving, and map every destination to a structured data payload.
Test installed-app routing and the first launch after install before publishing replacement URLs or changing DNS.
Yes. Google shut down Firebase Dynamic Links on August 25, 2025. Both page.link links and links on custom domains stopped being served, and the console tooling was removed.
It depends on what you used it for. If you need deep links, deferred deep linking, custom domains, and link-level attribution, Ferry covers those jobs with flat pricing from $9 per month. If you also need full mobile measurement with ad network integrations and fraud tooling, look at Branch, AppsFlyer, or Adjust.
No. Dynamic Links stopped resolving at the shutdown, so any link still printed in emails, QR codes, packaging, or app flows sends users nowhere. Each one needs a replacement URL on a domain you control.
Yes. After a user installs from a Ferry link, the SDK matches the first open back to the originating link and returns the original payload, along with the match method and a confidence level.
If the domain is yours, yes: connect it to a Ferry project as a custom domain and recreate the slugs you need. The page.link subdomains belonged to Google and cannot be moved.
The SDK integration is small, and the docs are written so a coding agent can do the wiring. Most of the real work is inventorying which old links still have users behind them and publishing replacements where those links live.
Start with one app, one hostname, and the links that still have users behind them.