Firebase Dynamic Links (FDL) will be fully shut down on August 25, 2025. This guide explains what will break, how to audit your stack, and a fast migration plan so your links keep working.
What Will Break
- Existing FDL short links may stop resolving or stop passing parameters to your app.
- Deferred deep linking flows (first-install → open exact screen) will fail without replacement.
- Attribution and campaign parameters tied to FDL clicks will be lost.
If you rely on FDL for onboarding, promos, referrals, or personalized re-engagement — plan the switch now.
Quick Audit (15 minutes)
- Search codebases and configs for
page.link
or your FDL domain. - List all surfaces using FDL: emails, push templates, SMS, paid ads, QR, website banners.
- Open top 20 links on a fresh device → verify install → open app → screen.
- Document the parameters you pass today (campaign, promo code, user id).
Migration Plan (Step by Step)
- Create replacement links: use SDDL (Dashboard or API) to create short links for your key campaigns. Keep the same query params you used in FDL (promo, userId, etc.).
- Configure your apps:
- iOS: enable Associated Domains and add your link domain. Make sure your domain serves a valid
apple-app-site-association
. See: How to add an Associated Domain in Xcode. - Android: add App Links intent filters in the manifest and include your SHA-256 signing cert. Make sure your domain serves
/.well-known/assetlinks.json
. See: Find the SHA-256 fingerprint and Custom URL scheme on Android.
- iOS: enable Associated Domains and add your link domain. Make sure your domain serves a valid
- Implement deferred flow: on click, SDDL stores your params and issues a token; on first app launch, call the SDDL “defer” endpoint to fetch params and route the user to the target screen. Endpoint details are in API docs.
- Swap templates: update email/SMS/push/ad/QR templates to use the new short links.
- QA on fresh devices: click → store → install → open app → verify screen & parameters. For quick checks use the Deep Link Tester.
Why Teams Choose SDDL for Migration
- Deferred deep linking without heavy SDKs (API-first is possible).
- Universal Links & App Links with built-in validators and generators.
- Secure parameter storage and retrieval on first launch.
- Link analytics (clicks, platforms) and webhooks.
FAQ
Do I have to change my app binary?
You need to ensure universal/app links are configured. If you already support them, server-side migration can be swift.
Can I keep my parameters?
Yes. Pass the same campaign/user data through SDDL links and retrieve it on first launch.