Do Firebase Dynamic Links still work?

No. Google shut the service down on August 25, 2025 and existing links stopped resolving. Anything still pointing at a page.link URL — in an email template, an app-store listing, a printed QR code — is broken today, not deprecated.

Is LinkSense a drop-in replacement for Firebase Dynamic Links?

No, and it is worth being precise about that. LinkSense covers the same core job: one link that opens your app when it is installed, routes to the App Store or Google Play when it is not, carries its own social preview tags, and records the click. It is a different product with a different data model, not a port of the Firebase API, so some things map one-for-one and some do not. The comparison table on this page lists both, including the places Firebase was better.

Do I need to add an SDK to my app?

Not for the core behaviour. LinkSense generates and serves the Apple App Site Association and Android assetlinks files on your subdomain, which is all iOS and Android need to hand a link to your app. You add your bundle ID and Team ID, associate the domain in Xcode or your manifest, and your links open the app. Firebase required its SDK to resolve the short link into the deep link it contained; here the OS delivers the full URL directly. The LinkSense SDKs exist only for deferred deep linking, which is a separate Pro feature in Beta.

Does LinkSense open a specific screen in my app?

LinkSense hands your app the full URL, with the path and query string intact, and your app routes from there using the navigation you already have. It does not store a per-link screen or route for you, so the routing decision stays in your code.

Can I import my Firebase links in bulk?

There is no bulk importer. Links are recreated one at a time, in the dashboard or through the REST API — which is available on every plan, including the free one, so a script can do the work. Firebase never exposed a bulk export of its own link definitions either, so in practice the source of truth is whatever created those links on your side.

What happened to deferred deep linking?

This is the clearest place where Firebase gave you more. Firebase Dynamic Links carried the original link through an app install on both platforms, first-party, at no cost. LinkSense has deferred deep linking as a Pro feature, still in Beta, and it requires one of our SDKs. If that behaviour is the reason you used Firebase Dynamic Links, test it before you migrate rather than after.

Will I get install and conversion numbers like Firebase Analytics gave me?

No, and the reason is structural rather than a missing feature. When a Universal Link fires and the app is installed, the operating system opens your app without ever contacting our server, so there is no request for us to record. LinkSense reports the clicks that do reach it — device, browser, OS, country, referrer — and does not publish install, open or conversion rates, because it has no way to observe them. Any product in this category quoting you such a rate is inferring it. Firebase could report first opens because it had an SDK inside the app doing the reporting; if you need that, you need an SDK-based attribution tool, and that is a different category.

What does this cost compared to Firebase?

Firebase Dynamic Links was free, so any paid alternative is a step backwards on price alone. The LinkSense free plan covers 1 project and 1,000 links in total, with unlimited clicks, REST API access, QR codes, social previews, a hosted landing page and 7 days of analytics history. Pro is $19.99 a month, flat: unlimited projects and links, custom domains, short links and analytics up to 90 days. There is no click metering, no monthly-active-user pricing and no per-seat charge.

Can my team share a LinkSense account?

Not yet. Firebase had project IAM with multiple members and scoped roles; LinkSense has a single owner per project, with no seats, roles or invitations. Every access rule in the database checks one user ID. If more than one person needs to manage links, they currently share a login.

Can I keep my old Firebase domain?

Not the page.link one — that namespace was Google-owned and went away with the service. If you were using a custom domain through Firebase Hosting, you can point it at LinkSense instead on the Pro plan; the app-side change is the same either way, one line in the Associated Domains entitlement and one attribute in the Android intent filter.

Firebase Dynamic Links is gone. Your links still have to open your app.

Google shut Firebase Dynamic Links down on August 25, 2025. LinkSense covers the part most apps actually used — one link that opens your app when it is installed and routes to the store when it is not. This is the honest version of the comparison: what maps across, what does not, and where Firebase was the better product.

What you lost, and what replaces it

Six things Firebase Dynamic Links did for you. These are the ones that map across.

The domain that owned your app

Firebase: Firebase hosted the Apple App Site Association and Digital Asset Links files behind your page.link subdomain. That, not the SDK, is what made a tap open your app.

LinkSense: LinkSense generates and serves both files on your project subdomain — and on your own domain on Pro. Free plan included, no SDK, no feature flag in front of it.

One link, three kinds of device

Firebase: iOS to the App Store, Android to Google Play, everything else to your web fallback, from a single URL.

LinkSense: Same precedence, same single URL: the app target wins on each platform, then the platform fallback, then the desktop URL.

Previews that unfurl

Firebase: The st, sd and si link parameters set the title, description and image a chat app showed when someone pasted the link.

LinkSense: Per-link Open Graph and Twitter Card fields, emitted on every HTML response the resolver returns — not only to crawlers it recognises.

Knowing a link was used

Firebase: Per-link click counts in the console, plus dynamic_link_first_open and dynamic_link_app_open events in Google Analytics.

LinkSense: Every click that reaches the resolver, with device, browser, OS, country and referrer. The Google Analytics half has no equivalent here — see the table.

Short links and custom paths

Firebase: Auto-generated or hand-picked short suffixes on your page.link domain.

LinkSense: Custom paths on every plan. Short aliases and your own domain are Pro.

Somewhere for a laptop to land

Firebase: Firebase showed an app preview interstitial. It was a hand-off screen, not a page you would send a desktop visitor to.

LinkSense: One hosted landing page per project, generated from your store listing — icon, screenshots, description, store buttons. It catches links that have no desktop URL of their own.

Firebase Dynamic Links vs LinkSense

The Firebase column describes the service as it worked before the shutdown. Rows marked Firebase are ones where Firebase was the better product.

	Firebase Dynamic Links	LinkSense
Status	Shut down August 25, 2025. Links stopped resolving.	Active, and this is the whole product rather than a line item on a platform roadmap.
PriceFirebase	Free, at Google scale.	Free plan: 1 project, 1,000 links total, unlimited clicks. Pro is $19.99/month flat — no click metering, no MAU pricing, no per-seat charge.
Universal Links / App Links setup	Hosted for you on your page.link subdomain.	Generated and served on your subdomain, or your own domain on Pro. Every plan.
Getting the link into your app	The Firebase SDK resolved the short link and handed you the link= payload.	The OS hands your app the full URL and your app routes from there. No SDK in this path.
Device routing	iOS, Android, web fallback.	iOS, Android, desktop — app target first, then platform fallback, then desktop URL.
Social preview tags	st / sd / si parameters on the link.	Per-link Open Graph and Twitter Card title, description and image.
Desktop landing page	An app preview interstitial. Nothing you could point a laptop at.	One hosted landing page per project, built from your store listing, served to links with no desktop URL of their own.
Deferred deep linkingFirebase	Both platforms, free, first-party, no add-on tier.	Pro only, still in Beta, and it needs one of our SDKs. Firebase was better here.
AnalyticsFirebase	Console click counts plus first_open / app_open events in Google Analytics, joinable with the rest of your funnel.	Clicks by device, browser, OS, country and referrer. No install or app-open events — we do not have them to give.
Rest of the stackFirebase	The same console as Auth, Firestore, Crashlytics and Analytics, with shared project IAM.	A standalone product. Nothing to inherit, and nothing to be deprecated alongside.
Team accessFirebase	Firebase project IAM — multiple members, scoped roles.	One owner. No seats, roles or invites; every access rule in the database is a single-owner check.
REST API	Short-link creation over HTTP.	Links, projects and app registrations, on every plan — which is how you script a migration.
QR code per link	Not offered.	PNG or SVG, in the dashboard and over the API, ungated.
Link expiry, geo targeting, A/B variants	None of the three.	None of the three. Same gap, not an upgrade.

What LinkSense does not replace

Read this part before the pricing page. If one of these is why you are here, you will find out on day three otherwise.

The Google Analytics event stream

Firebase wrote dynamic_link_first_open and dynamic_link_app_open into your analytics property, so a link could be joined to the rest of your funnel. LinkSense emits nothing into Google Analytics, and there is a structural reason as well as a product one — see the question about install numbers below.

Free deferred deep linking on both platforms

Ours is a Pro feature, in Beta, and it requires the SDK. If carrying context through an install is the reason you used Firebase Dynamic Links, evaluate that specific feature before you commit rather than after.

Shared team access

There are no seats, roles or invitations. A project belongs to the account that created it. If two people need to edit links today, they share one login.

A bulk importer

There is no import path. Links are recreated one at a time, in the dashboard or through the REST API — which is on every plan, so a script can do it. How long that takes depends on how many links you have, which is why this page gives you steps and not an estimate.

Link expiry, geo targeting, A/B variants, a UTM builder, outbound webhooks, an analytics API, data export

None of these exist. Firebase did not have them either, so nothing is lost in the move — but several products in this category do ship them. If one is on your list, we are not the tool that has it.

Moving off page.link

Six steps. The migration guide covers the same ground with the concept mapping and the exact configuration changes.

Create a project and pick a subdomain

Your Firebase URL prefix becomes a LinkSense subdomain: yourapp.page.link becomes yourapp.linksense.net. On Pro you can point your own domain at it instead.

Register your iOS and Android apps

Same Bundle ID, Team ID, package name and SHA-256 fingerprints you had in Firebase. The Apple App Site Association and assetlinks.json files update as you add and remove apps.

Recreate the links

Routing rules, fallback URLs and social preview settings, matched to the Firebase links they replace. There is no bulk importer, so do it in the dashboard or script it against the REST API.

Repoint the app at the new host

One line in the Associated Domains entitlement on iOS, one attribute in the intent filter on Android.

applinks:yourapp.page.link  →  applinks:yourapp.linksense.net
android:host="yourapp.page.link"  →  android:host="yourapp.linksense.net"

Take the link-resolution SDK out of the path

Firebase needed its SDK to turn a short link back into your deep link. Here the OS delivers the full URL to your app and your existing router handles it. Add a LinkSense SDK only if you want deferred deep linking, which is Pro and in Beta.

Swap the references

Emails, marketing assets, hardcoded URLs, anything with page.link in it. Those stopped resolving in August 2025, so this step is repair work rather than a cutover.

Migration questions

Try it on one link first

Register one app, create one link, and see whether it opens on your own phone before you touch the other nine hundred. The free plan does app linking without an SDK or an upgrade.

Create a free account

Free plan · No credit card · Read the migration guide

LinkSense