Moving off Firebase Dynamic Links: the fact sheet
Firebase Dynamic Links shut down on 25 August 2025. Quick facts on 404s, page.link, the APIs, the Takeout CSV export and what Google says replaces each feature.
Firebase Dynamic Links shut down on 25 August 2025. Links now return a 404, .page.link domains are gone and the APIs return errors. Google points to third-party providers for full parity, or App Links and Universal Links for installed-app deep links only.
What was Firebase Dynamic Links, and what happened to it?
Firebase Dynamic Links was Google's deep linking service for short links that opened the right content in an app, and Google's FAQ states that it shut down on 25 August 2025.
- Before shutdown: new and existing links kept working until 25 August 2025.
- Rollout of errors: error responses rolled out gradually from that date and reach 100% once the sunset date has passed.
- Metadata: domain and link metadata were marked for deletion on 25 August 2025, and URL prefix domains are deleted automatically after that date.
This page is a quick fact sheet. For a step-by-step plan, read the full guide to moving off Firebase Dynamic Links.
What happens to existing Firebase links now?
Every Firebase Dynamic Link clicked now returns an HTTP 404 status to the user, according to Google's Dynamic Links FAQ. Any link still printed on packaging, in old emails or in app store listings leads nowhere.
- APIs: requests to the Short Links API and the Link Stats API return a 400 or 403 HTTP status.
- page.link domains: once the service is shut down, .page.link domains are no longer available, so links on them cannot be repointed.
- Custom URL prefix domains: deleted automatically after the shutdown date. A domain you own can be pointed at a new host, which then serves its own association files.
Universal Links: Apple's way of opening an app from a normal https link on a domain you own, verified by an apple-app-site-association file. Android's equivalent is App Links, verified by assetlinks.json.
Can you still export your Firebase link data?
Google's export guide describes a Google Takeout export, but whether Takeout still works now that the 25 August 2025 deletion date has passed is not published. If you have not exported yet, try it and keep whatever comes back.
What Google's export guide says:
- Route: Google Takeout, not a REST API.
- Access: you must be signed in with a Google Account that has owner permissions on the Firebase project.
- Coverage: links created with the Firebase SDKs or REST API, not only console links, are included only if you choose them in Takeout's "Advanced" options.
- Format: CSV files, one per domain.
- Columns: short link, deep link, Android and iOS fallback and app identifiers, social meta tags, UTM parameters, link name and creation timestamp.
- Timing: an export can take up to a day.
- Analytics: the link analytics API is limited to about 5 queries per second, and the Google Analytics export covers only a subset of link analytics data.
The deep link column is the part to keep: Google's App Links and Universal Links guide suggests reusing your Dynamic Links' deep link paths on new links.
What Firebase did vs what replaces it
| Job | App Links and Universal Links (Google's guide) | Third-party deep linking provider |
|---|---|---|
| Short links | Not created | Check each provider's docs |
| Open the installed app | Yes, on a domain you own with assetlinks.json and apple-app-site-association under /.well-known | Check each provider's docs |
| Send users to the right app store | Not provided; Smart App Banners suggested on iOS | Check each provider's docs |
| Deferred deep linking after first install | Not provided | Check each provider's docs |
| Click analytics | Not provided | Check each provider's docs |
| Firebase Auth email links, password reset, email verification | Upgrade to the latest Firebase Authentication SDKs | Not applicable |
What are Google's options for replacing Firebase Dynamic Links?
Google's FAQ sets out three paths:
- Full feature parity: use a third-party deep linking provider. Google names Adjust, Airbridge, AppsFlyer, Bitly, Branch, Kochava and Singular, and notes they "have not been vetted by Google". Other providers exist outside that list.
- Installed-app deep links only: App Links on Android and Universal Links on iOS, on a domain you own (for example one served on Firebase Hosting).
- No replacement needed: review and export link metadata, delete URL prefixes in the Firebase console and remove the SDK.
Whichever path you take, the Firebase Authentication note applies to any app that used Dynamic Links for email sign-in links, password reset or email verification.
On Android 15 and later, assetlinks.json changes can take up to seven days to reach all devices, so publish the file on the new domain before you ship links that rely on it. The guide to migrating deep links safely covers the order of steps.
Planning a Firebase Dynamic Links move
Choose Firebase Dynamic Links in the planner on the home page, then work through the migration checklist. For a side-by-side of replacement options, see Firebase Dynamic Links replacements, and this Firebase Dynamic Links replacement guide covers rebuilding links step by step.
Questions
Do Firebase Dynamic Links still work?
No. Google's FAQ states the service shut down on 25 August 2025, and every link clicked now returns an HTTP 404 to the user.
Can I keep my page.link domain?
No. Google's FAQ states that .page.link domains are no longer available once the service is shut down, so links on them must be replaced with links on a domain you control.
Can I still export my Firebase Dynamic Links?
Google's export guide describes a Google Takeout export as CSV files, one per domain, run by a project owner. Whether it still works after the 25 August 2025 deletion date is not published, so try it and keep anything it returns.
Do App Links and Universal Links replace Firebase Dynamic Links fully?
No. Google's guide says they do not route users to the right app store, do not support deferred deep linking, do not provide click analytics and do not create short links.
How long does it take to switch MMP?
This site's planner pencils in about 7 to 12 weeks from contract check to retiring the old setup, most of it a 2 to 4 week parallel run. No vendor publishes a standard length; your release cycle, renewal notice and ad-network learning phases set the real pace.
Can I run two MMP SDKs at the same time?
Yes, for a while. AppsFlyer and Singular both publish guides for measuring with two MMPs, but SKAN postbacks go to only one MMP, TikTok supports one MMP at a time and X Ads does not support two.
Other vendors
Moving off AppsFlyerMoving off AppsFlyer? See what you can export and for how long, the 45-day renewal notice in its terms, where SKAN lives and which partners to turn off.
Moving off AdjustMoving off Adjust? See which raw data exports exist, the 45-day notice and 60-day deletion terms, how Meta pulls SKAN mappings and what to do with your links.
Moving off BranchMoving off Branch? See Branch's export windows, the 30-day renewal notice and 90-day data terms, how its SKAN endpoint works and what to plan for link domains.
Moving off SingularMoving off Singular? See its user-level retention windows, the 30-day renewal notice and data deletion terms, how SKAN models reach Meta and its dual-MMP guide.