Recover the links that still matter.
Start with links still present in campaigns, QR codes, email, packaging, referrals, and product flows.
Ferry replaces the jobs mobile teams relied on Firebase Dynamic Links to do: route users into the right app screen, preserve context through installation, and show which links lead to installs and revenue.
Google shut Firebase Dynamic Links down on August 25, 2025. Google says both custom-domain and page.link links stopped being served. Read the official FAQ
Ferry uses the mobile platform primitives your app already understands, then adds the deferred matching and attribution layer needed for real campaigns.
| What your app needs | How Ferry handles it |
|---|---|
| One link across mobile and web | Universal Links, App Links, store routing, and a web fallback from one hostname. |
| Context after installation | Deferred matching returns the original structured link payload with method and confidence. |
| A durable branded domain | Use a shared feryl.io hostname or connect a custom hostname you control. |
| Campaign measurement | Follow qualified opens through attributed installs, signups, purchases, and revenue. |
| A migration-friendly integration | Use the HTTP API or give the integration guide to your coding agent. |
Move the live journeys first. Historical links without users, distribution, or business value can wait.
Start with links still present in campaigns, QR codes, email, packaging, referrals, and product flows.
Create the project, choose a hostname, preserve important slugs, and map every destination to structured data.
Test installed-app routing and the first launch after install before changing DNS or publishing replacement URLs.
Start with one app, one hostname, and the links that still have users behind them.