Skip to content

App links and deep linking

Enable app opening for supported ti-ny.link destinations. Check supported destinations, test iOS and Android journeys and verify the browser fallback.

How mobile app opening works

An app-aware dynamic link can open supported content in a compatible mobile app. The result depends on the destination URL, device, installed app and browser. Some visitors will reach the browser destination instead.

Use the app-aware sharing guide for campaign examples such as music, video, maps and messaging.

Enable app opening and test it

  1. Copy the destination URL from the service’s own sharing controls and open it to check the content.
  2. Create a short link to that destination.
  3. In the saved link’s settings, open App linking, enable Auto open app on mobile and choose Update. The panel lists supported apps and warns when the destination does not match.
  4. Open the public short link on iOS and Android, with and without the relevant app installed.
  5. Test from the browsers and social apps your audience uses, as well as desktop. Verify the browser destination too.

Mobile app opening is different from audience targeting. Country, device and language rules can route visitors to different URLs; configure and test those rules separately, including the default destination.

Apps listed in the platform

The apps below support recognised destination URLs on compatible iOS and Android devices. Your destination must match the service’s supported URL format.

ContentListed apps
Music and audioSpotify, Apple Music
Video and streamingYouTube, TikTok, Twitch, Netflix
Social and professionalReddit, X, Instagram, Snapchat, Facebook, LinkedIn, Pinterest
MessagingWhatsApp, Facebook Messenger, Telegram
DocumentsGoogle Sheets, Google Docs, Google Slides
Maps and travelGoogle Maps, Waze, Airbnb, TripAdvisor, Booking.com
ShoppingAliExpress, Amazon, StockX

Copy the destination using the app’s sharing controls. Paste it into Destination URL, check the App linking panel for a compatibility warning, save with Update and test the complete journey on the intended devices.

A recognised destination does not guarantee that every visitor opens the app. An installed app, supported browser and compatible destination are still needed.

When the URL does not match

The App linking panel warns when a destination does not match a supported app. Check the provider’s original shared URL and test the ordinary web destination. If the warning remains, use the browser destination or choose a supported URL.

If a supported app does not open, check that the URL identifies the content you intended, that the relevant app is installed, and that the link setting is enabled. Test a different browser and a direct open of the destination to help isolate the issue.

Connect a dynamic QR code to the configured short link. Scan the exported code before printing and repeat the app and browser checks above. Scanning a QR code does not remove device or browser compatibility limits.

Review link analytics for recorded activity. A visit does not confirm that the visitor opened the app or completed an action inside it.

For a destination that does not open as expected, work through the checks above with the exact URL, device and browser you are using. See the app-aware link workflow for a complete testing sequence.