Skip to content
Dashboard

Getting Started with Detour

This guide describes how to set up Detour for your app. You create an organization, configure an app in the dashboard, integrate the SDK, and test a deferred link on a real device.

Sign up at the Detour dashboard and confirm your email.

Detour is multi-tenant. An Organization groups apps, links, and users under one unique subdomain.

  • You choose that subdomain while creating the organization: yourorg.godetour.link.
  • Invited members manage apps and links according to their role: Owner, Admin, or Member.

In the dashboard, create a new app by providing an App Name. Detour then generates:

  • App ID — the unique app identifier used by the SDK configuration.
  • Publishable API Key — the active key used by the SDK configuration.
  • Base deferred linkhttps://<yourorg>.godetour.link/<app_hash>, or your custom domain if one is attached.

After you create an app, its details view opens automatically. You can also open it later from the Apps list. Complete the three tabs below.

  • Your app link is generated automatically and is read-only. You can copy it, open its QR code, and manage its metadata, but the base hash segment must stay unchanged.
  • Set the Redirect URL for web fallback.
  • Pick a query-forwarding strategy for that fallback URL: Don’t pass parameters, Pass all parameters, or Pass specific parameters.
  • Use Short links for campaign variants with their own path and query parameters.
  • Optionally tune Matching configuration. See Matching.

Configure iOS and Android separately.

FieldFormatWhere to find it
Bundle IDFor example com.example.appXcode: target settings → GeneralBundle Identifier
Team ID10 uppercase letters and digitsApple Developer account membership details, or Xcode signing settings
App Store IDNumericApp Store Connect, or your app’s App Store URL (.../id1234567890)
Enable copy link featureOptional
FieldFormatWhere to find it
Package nameFor example com.example.appapplicationId in build.gradle, or android.package in an Expo config
SHA-256 certificate fingerprintAt least oneFinding your Android SHA-256 fingerprint

The SHA-256 fingerprint must match the key that signed the build you install. Otherwise links open in the browser instead of the app. Which key that is depends on how you build.

On save, Detour generates the integration snippets for the app-side setup, filled in with your real host and path values.

  • Copy the Publishable API Key and App ID.
  • Generate new key rotates the key and revokes the previously active one.

After you install and initialize the SDK:

  1. Register the Detour host

    Add the snippets from App configuration. On iOS that is an Associated Domain, on Android an App Link intent filter. Without them, Detour links do not open your app when it is already installed. Deferred links work without them.

  2. Handle navigation

    Open the screen for the returned link, as described in the SDK usage guide.

Custom-scheme links need a separate registration. See Universal Links & App Links.

Which steps apply depends on whether your app is already in the store.

This is the usual case at this point, because the build that carries the SDK is not in a store yet. Only the install step changes, so a simulator or an emulator works here.

  1. Remove any earlier install from the device, simulator or emulator.
  2. Open a Detour link in a mobile browser there.
  3. Install your development build there and open it.

Detour records the click before the redirect runs, so the redirect ending on the web fallback or on a listing that does not exist yet does not affect the test.

This needs a real device.

  1. Remove any earlier install from the device.
  2. Open a Detour link in a mobile browser there.
  3. Follow the redirect into the App Store or Google Play, install the app from there, and open it.

In both cases the SDK returns the link you opened, on the first launch after the install. For the full steps, see Testing Deferred Links.