Is Firebase Dynamic Links still available?
No. Google deprecated Firebase Dynamic Links in 2023 and shut it down on 25 August 2025. Existing FDL links no longer resolve.
A Firebase Dynamic Links alternative that stays simple
Google shut down Firebase Dynamic Links on 25 August 2025, and every link built on it now returns a 404. If you used FDL for its core job — one link that routes users to the store or into your app, keeps working across a fresh install, and tells you what got clicked — LinkTrace covers that job directly. Two HTTP calls, no SDK, and a free plan to migrate onto. If you used FDL as one piece of a wider Firebase setup, the limits section below says where LinkTrace is not the right replacement.
What FDL did, and what you actually need to replace
Most apps used FDL for three things.
| FDL feature | LinkTrace equivalent |
|---|---|
| Dynamic links that route to store or app | POST /api/v1/referral-links — short links with device detection and store fallback |
| Deferred deep linking (destination survives install) | customPayload on the link, plus POST /api/v1/attributions after install — see deferred deep linking |
| Link click analytics | Link-wise click counts on every plan; analytics dashboard from Growth |
Migrating from FDL to LinkTrace
- Get an API key. Sign up — the free plan needs no credit card — and copy your key from Settings › API Key in the dashboard.
- Replace link creation. Wherever your backend or app created FDL links, call
POST /api/v1/referral-linksinstead. Move any deep-link parameters intocustomPayload. - Replace link resolution. Swap FDL’s link-resolution callback for a single
POST /api/v1/attributionscall after install, and navigate from the returned payload. - Republish your links. Swap the dead
page.linkURLs in your campaigns, QR codes and share flows for the new LinkTrace links.
There is no client SDK to add and nothing Firebase-specific left in your app. Request and response shapes are in the API reference. If you are still evaluating, our FDL alternatives guide compares the wider field, and the Branch comparison covers the most common enterprise option.
Where LinkTrace is not the right replacement
LinkTrace does not replace the rest of Firebase. If your FDL usage was entangled with Firebase Analytics funnels, A/B tests through Remote Config, or Firebase Authentication email-link sign-in, you will need to re-home those separately — LinkTrace is deliberately just links, attribution and referrals.
It also does not do SKAdNetwork management, ad-network postbacks, fraud scoring and paid-media cost aggregation. If your deep links exist mainly for paid user-acquisition measurement, an MMP is the right tool — see our MMP alternative page for where that line falls.
Frequently asked questions
Does LinkTrace require Firebase?
No. LinkTrace is standalone: your server calls the API to create links, and your app makes one call after install. There is nothing to install or configure in Firebase.
How much work is the migration?
For the common case — create a link, resolve it after install — it is two API calls replacing two FDL calls. The link-creation and first-launch resolution points in your code are the only places that change, plus republishing links already used in campaigns.
Is there a free plan?
Yes. Deferred deep linking and referral tracking are included on the free Starter plan (a one-time allowance of 100 dynamic links and 1,000 attributed installs). No credit card required. See pricing.
Start tracing — free plan, no credit card
Two HTTP calls, no SDK, and deferred deep linking, install attribution and referral tracking on every plan.