Build with LinkTrail
Everything you need to ship deferred deep links, smart routing, and privacy-first attribution across iOS, Android, and web.
Getting Started
Introduction
What LinkTrail does, and how a link flows from tap to the right in-app screen — through the store, a fresh install, and back to the campaign that earned it.
Quickstart
Integrate LinkTrail in about five minutes: register an app in the dashboard, add the SDK, and make the three calls that route links and attribute installs.
Dashboard
The web console at developer.linktrail.io — register apps, verify link domains, create and tag links, read attribution analytics, and manage settings.
SDKs
iOS SDK
Install and integrate the LinkTrail iOS SDK — module LinkTrailSDK, iOS 15+, via Swift Package Manager or CocoaPods — with configure, onLink and consent.
Android SDK
Install and integrate the LinkTrail Android SDK — package io.linktrail, minSdk 26, on Maven Central — with configure, onLink, consent and the Install Referrer.
React Native SDK
Install and integrate the LinkTrail React Native SDK — linktrail-react-native, a New Architecture TurboModule.
Flutter SDK
Install and integrate the LinkTrail Flutter SDK — package linktrail_flutter, one Dart API over the native SDKs.
Guides
Deep Linking
Direct, deferred, and contextual links — what each one carries, how the SDK delivers it after install, and when to reach for which.
Attribution
How LinkTrail matches an install to the link and campaign that earned it — deterministic first, probabilistic only when enabled, and what gets recorded.
Tracking Events
Attribute in-app behaviour and revenue back to the link that drove the install — which events to send, how to name them, and where they surface.
App Credentials
What the dashboard needs to register an app, and where to find each value — bundle IDs, Apple Team ID, App Store ID, package names and signing fingerprints.
Troubleshooting
When a link opens the browser or store instead of your app — domain verification, signing fingerprints, caches, consent, and the checks that find the cause.
Frequently asked questions
How do I integrate the LinkTrail SDK?
Three calls. Configure with your API key at launch, register an onLink handler to route incoming links, and forward OS links with handleDeepLink. After your consent prompt, call setConsent(true) so attribution can start. The Quickstart guide walks through both the dashboard setup and the app code in about five minutes.
Which SDKs does LinkTrail provide?
Four: iOS via Swift Package Manager or CocoaPods (iOS 15+), Android via Maven Central (minSdk 26), React Native as a New Architecture TurboModule, and Flutter as a pub.dev plugin. The React Native and Flutter packages wrap the same native SDKs, so behaviour is consistent across all of them.
Why do my deep links open the browser instead of my app?
Almost always domain verification rather than SDK code — a signing-fingerprint mismatch or a stale cache in the AASA or assetlinks.json file. Note that typing a URL in the address bar never opens an app on either platform by design; test by tapping a link from another app instead.
Do I need to obtain user consent before the SDK collects data?
Yes, and the SDK is built for it. Consent gating is on by default on iOS and Android: deep links still route so users reach the right screen, but no attribution is recorded until your app calls setConsent(true). As the controller, obtaining that consent is your responsibility.
Does the LinkTrail SDK collect the IDFA or Google Advertising ID?
No. The SDK never accesses the Apple IDFA, with or without App Tracking Transparency permission, and never reads the Google Advertising ID. It uses a vendor-scoped identifier — the iOS IDFV or Android App Set ID — which is scoped to you as the developer and not shared across companies.