Skip to content

Free tool

Can your links move?

If your deep links are on your own domain, moving them to DeepLinkNow is one DNS change, and every link you've already sent keeps opening your app. On a vendor's domain, you swap the domain in your links and keep the paths. Enter the domain to see which one applies.

Why one record is enough

A branded link domain like link.yourapp.com is a CNAME to the vendor. Your app trusts the domain, not the vendor: its Associated Domains on iOS and its intent filters on Android name link.yourapp.com. Point the CNAME at DeepLinkNow and the domain serves DeepLinkNow's verification files for the same app, so iOS and Android keep opening it.

DeepLinkNow treats every path on your domain as a deep link with no setup. link.yourapp.com/promo?code=X opens your app with /promo and code=X, whether the link was made last year on another vendor or a minute ago.

Domains the vendor owns, like yourapp.app.link or yourapp.onelink.me, aren't yours to repoint. For those, swap the domain in the links themselves: yourapp.app.link/summer-sale becomes yourapp.deeplinknow.com/summer-sale. The path carries over unchanged, so it's a find-and-replace, not a migration.

How the switch goes

  1. Create your app in DeepLinkNow with the same Team ID and bundle ID, and the same Android package and SHA-256 certificate, as the app your links open today. The result above lists them when the domain publishes them.
  2. Add the domain under Settings › Domain and add the TXT record it shows. That proves you own the domain while the CNAME still points at your current vendor.
  3. Change the CNAME to customers.deeplinknow.com. The domain goes active once the certificate is issued.
  4. Add the DeepLinkNow SDK in your next release for deferred deep links after an install.

Your old link data

Links that carry their data in the URL need nothing. A short code whose data lives with the old vendor reaches your app as the bare path, so you choose what to do with it: ignore it (the app opens on its home screen), map the codes you care about in your app, or import the old links so each code gets its data back.

Questions

Do I have to migrate my old links?
No. Every path on your domain works on DeepLinkNow with no setup, so an old link opens your app with the same path and query it always had. Your app gets that URL. A short code like /abc123 arrives as /abc123: if your app needs the data Branch or AppsFlyer stored for it, map the code in your app or on your own landing page, or import the old links.
Do I need to release a new version of my app?
Not for links to open the installed app: your app's Associated Domains and intent filters already list this domain. Deferred deep links (the app opening on the right screen after an install) need the DeepLinkNow SDK, so that comes with your next release.
What if my code reads links through Branch's SDK?
Branch's SDK only returns data for links Branch serves. Once the domain is on DeepLinkNow, read the URL the app was opened with, or use the DeepLinkNow SDK, which returns the path and query parameters.
Will links stop working during the switch?
DeepLinkNow's HTTPS certificate for the domain is issued after the CNAME points at it, so for a short time after the change the domain can fail in a browser. Make the change at a quiet time. Taps that open the installed app straight from iOS or Android aren't affected.
What does a custom domain cost?
Custom domains are on paid plans, from Startup at $49 a month with 3 domains. A team moving from Branch or AppsFlyer gets 3 months free on a yearly plan.

Move your links in an afternoon

Set up the app first, then change one record when you're ready. New workspaces get Startup, custom domains included, free for 14 days.

    Can your deep links move off Branch or AppsFlyer? | DeepLinkNow