At a glance
| Field | Detail |
|---|---|
| What | Replace Firebase Dynamic Links while preserving the intended app destination. |
| Who it matters to | App advertisers using legacy links and considering Branch. |
| Where | Google Ads and Meta campaigns, with different integration requirements. |
| When it applies | When auditing legacy destinations or implementing replacement links; this is an evergreen guide. |
| Action | Check domain ownership, installed-app routing, post-install routing and attribution separately. |
Branch deep links require more than replacing a URL in an ad. Google's deprecation FAQ set August 25, 2025 as the Firebase Dynamic Links shutdown date, including custom domains and page.link subdomains. For an app advertiser, the replacement decision starts with the journey that must survive: opening installed content, continuing after installation, or both.
Choose the replacement around the journey
Google's native-link migration guide supports opening an installed app and navigating to specific content. That migration does not itself provide device-specific store routing or continuation after downloading and installing the app. Our suggested check is to document those needs before choosing a native-link implementation alone.
Branch's migration guide distinguishes these domain options:
| Existing setup | Replacement option | Limitation | Suggested check |
|---|---|---|---|
| Owned custom domain | Reuse with Branch and preserve aliases | Downtime during the CNAME switch | Compare link paths. |
| Changing domains | Create replacement Branch links | Distributed links need replacement | Inventory affected placements. |
| Firebase page.link domain | Use a Branch or owned domain | page.link cannot transfer | Replace distributed URLs. |
Check prerequisites
| Requirement | Why it matters |
|---|---|
| Mobile developers and a legacy-link inventory | Branch identifies these as migration prerequisites. |
| Branch ad partner integration access | Availability varies by plan, according to its network setup guides. |
| Branch and advertising-account admin permissions | Needed for the Google Ads and Meta connections described by Branch. |
| Matching iOS domain and app configuration | Apple requires the website association file and app entitlement to agree. |
The network instructions below refer to the new Branch experience. They do not establish that every account has the same interface or plan access. See Branch's Google Ads setup and Meta setup for their respective requirements.
Configure the app and domain
Following Branch's migration guide, configure platform redirects and the link domain, integrate its SDK, and implement in-app routing. Review its parameter mapping before recreating Firebase links.
For iOS, Apple's associated-domain documentation requires an apple-app-site-association file and a matching Associated Domains entitlement. List the app identifiers under the applinks service, and host the file in the domain's .well-known directory over HTTPS with a valid certificate and no redirects.
Add the Associated Domains capability to the app target in Xcode. Domain entries should omit paths and query components. Apple also says that each participating subdomain needs its own entitlement entry and association file. Our suggested check is to inspect the exact hostname used by the replacement link, including any subdomain, before diagnosing an app-routing failure.
Match the campaign integration
Branch's Google Ads guide distinguishes App Campaigns for installs from engagement campaigns. Installs use its self-attributing network API-driven deferred deep linking; engagement supports Universal Links, App Links and URI schemes.
Create the Google Ads Link ID for each app and platform, connect the account in Branch, and save the appropriate Link IDs. Enable Branch's optional deferred-link feature where that is the chosen install journey. A successful domain migration does not establish that this campaign configuration is complete.
For Meta, connect the advertising account through Branch's Meta integration. Branch says most attribution flows through Meta APIs, with limited tracking-link support. It also states that Meta attribution data is not returned in the app's deep-link session initialization callback. Our interpretation: assess the content destination and the attribution record independently.
Verify destinations and measurement
Branch's migration checks cover opening the installed app, reaching specific content, and redirecting to the website or relevant store when appropriate. For acquisition campaigns, add a separate test of the intended first-open destination after installation.
For Meta event delivery, Branch recommends checking app events in Liveview and mapped events in Meta Events Manager. These checks establish different things from a successful content open.
| Common problem | Suggested investigation |
|---|---|
| Native replacement opens installed content but loses the post-install journey | Revisit Google's documented native-migration limits. |
| An iOS link does not open the app | Compare the hostname, association file and entitlement against Apple's requirements. |
| Meta campaign data is absent from the deep-link callback | Use attribution reporting separately; Branch documents that callback limitation. |
What to review
- Compare installed and newly installed journeys separately.
- Review campaign-specific deep-link support before replacing ad destinations.
- Check event receipt alongside destination behavior.
- Record unresolved eligibility questions; eligibility for every individual placement is not specified in the cited documentation.
Use the re-engagement setup review to connect destination checks with the intended return action.



