Uncategorized

What is Deep Linking?

Table of Contents

Download The State of AI in Gaming Support Report

Deep linking is the practice of using a specific URL or URI to send a user directly to a defined destination inside a mobile app, bypassing the home screen. Three link types handle different scenarios: standard deep links (app installed), deferred deep links (app not installed), and contextual deep links (deferred links that also carry metadata through the install).

A studio sends a push notification: “Your support reply is ready.” For a player with the app installed, a standard deep link opens the exact support thread in one tap. For a player who uninstalled and reinstalled, a deferred deep link detects the missing app, redirects to the app store, and drops the player into the same thread on first launch.

Types of Deep Links

TypeRequires app installedHow it routes
StandardYesUses a custom URI scheme (myapp://) or an HTTPS-based scheme to open the registered in-app screen directly
DeferredNoRedirects to the app store, stores destination intent, and delivers the correct screen on first launch via Install Referrer API (Android) or device fingerprinting (iOS)
ContextualNoA deferred link that also carries metadata (campaign ID, referral source, promo code) through install, personalizing the first session

HTTPS-based schemes, iOS Universal Links and Android App Links, replaced custom URI schemes because any app could register the same URI string and intercept another app’s links. Server-side domain verification closes that security hole.

How Deep Linking Works

Two routing paths cover the full install spectrum.

Path A: App is installed

  1. User taps the link.
  2. The OS checks the app’s registered scheme or verifies the server-hosted configuration file.
  3. The OS routes the user to the correct in-app screen.

Path B: App is not installed

  1. The link detects the missing app and redirects to the app store.
  2. The user completes the install.
  3. On first launch, the app reads stored destination intent and routes the user to the intended screen.

Two platform files make HTTPS-based routing possible: the Apple App Site Association (AASA) file for iOS Universal Links and the Digital Asset Links JSON file for Android App Links. Both must be hosted at a verified domain and kept current.

Important: An expired or misconfigured AASA file causes iOS to silently fall back to Safari instead of the app, a common production bug that is difficult to detect without active link monitoring.

Deep Links vs. Universal Links

DimensionDeep Link (general)Universal Link (iOS) / App Link (Android)
ScopeBroad category covering all link typesPlatform-specific HTTPS implementation
Security modelCustom URI schemes are hijackable by any appServer-side file verification ties the link to one verified domain
Fallback behaviorCustom URI fails silently if app is absentFalls back to the associated web URL

Android App Links are the Android equivalent of iOS Universal Links. Both use HTTPS-based domain verification to prevent URI hijacking and provide a working fallback web destination when the app is absent.

Deep Linking in Player Support Workflows

Three support use cases where deep linking closes the gap between message and action:

  1. A push notification routes a player directly into their open support thread with agent context already loaded, skipping the home screen entirely.
  2. A QR code handoff for console players carries them into an active mobile support session without navigation steps. Helpshift’s console-to-mobile QR handoff uses this mechanism to preserve full player context across devices.
  3. A campaign message drops a player onto a reward claim screen rather than a main menu, removing friction between notification and conversion.

Contextual deep links add attribution value across all three flows. Campaign metadata passes through install, letting studios connect a specific notification or QR scan to downstream outcomes such as ticket resolution or event completion and tie those results back to campaign ROI.

Related Terms: Push Notifications, In-App Messaging, Player Context, Campaign Attribution

Resources

Ready to do this?