Deep linking allows users to be directed into a specific location on a website or within a mobile app, whether that’s a product page, account view, or in-app content experience.
This article will show you exactly how Flowcode enables deep linking—breaking down the essential technology and guiding you through the steps to get your users to the right in-app content, every time.
Before we dive into the step-by-step setup, it is important to familiarize yourself with a few key concepts to ensure you’re choosing the best experience for your users:
1. Understanding Deep Linking: Standard vs. Deferred
There are two types of deep links we support. While both aim to get users into your app, they function differently depending on if your is app installed already.
Standard Deep Linking: Best for re-engaging existing users.
How it works: When a user scans, the link looks for the app on their device. If it’s there, it opens the app to a specific page.
The Catch: If the user does not have your app installed, the link will often break, showing an error message or a "dead end" browser page.
Deferred Deep Linking (Recommended): Best for new user acquisition. This is the most flexible option because it accounts for every user.
If they have the app: It works exactly like a standard deep link—opening the app immediately to the right content.
If they DON'T have the app: It sends the user to the app store first. Once they download and open the app, they are automatically routed to the specific content they originally scanned for.
Why we recommend Deferred Deep Linking: It provides a "no-fail" experience. You never have to worry about losing a customer just because they haven't downloaded your app yet.
2. Implementation Methods: Universal Links vs. Custom URI Schemes
We support two primary methods for implementing these links:
Feature | Universal Links | Custom URI Schemes |
Definition | A modern, secure, and verifiable method of deep linking that uses a standard HTTPS web URL. | A traditional method of deep linking that uses a custom, app-specific scheme (like an internal address for the app). |
Format Example |
| |
Fallback Behavior | Seamless Fallback: If the app is not installed, the link opens the equivalent web page or a designated fallback URL in the user's browser. | No Built-in Fallback: If the app is not installed, the link typically fails to open and presents an error.
⚠️ Use an app link provider to support a Fallback for custom URI schemes. |
Best Practice | Recommended: Generally more modern, secure, and reliable. | Supported, but Cautioned: Useful for older apps or specific contexts. |
Why We Recommend Universal Links
While Flowcode supports both methods, we typically recommend using Universal Links (on iOS) or their Android equivalent, App Links, as they offer a more modern and reliable experience.
Universal Links are essentially standard web links that your operating system (iOS or Android) recognizes as belonging to your app. If the app is installed, the link opens the app directly; if not, it simply loads the standard web URL, providing a seamless fallback.
If you must use a custom URI and need to have a fallback in place (to avoid errors for users that don’t already have your app installed), you should use a third-party app link platform. An app link from a third party can be used as the “website” destination URL in Flowcode.
Here’s how it works:
Step 1: Create Your Deep Link in a Dedicated Platform
Flowcode doesn’t generate deep links directly. To set one up, you’ll need to create your Universal Link or Custom URI in a platform like Branch, Kochava, or AppsFlyer.
💡 Tracking App Store Downloads (CT & PT Parameters)
If you are driving users to the Apple App Store, you should include CT (Campaign Token) and PT (Provider Token) parameters in your link.
PT: Your unique developer identifier found in App Store Connect.
CT: A custom name (e.g.,
Summer_Sale) you assign to the scan.
Including these ensures that when a user scans your Flowcode and downloads the app, the conversion is correctly attributed to your specific campaign within Apple App Analytics.
Read more about CT & PT Parameters.
Step 2: Create a Conversion Flow that drives to URL
In the Flowcode platform, click on the “Create” button to build a new Conversion Flow. Then, select the “Scan to URL” template where you’ll be prompted to name.
Step 3: Set up your Deep Link
Once you're in the Flow Editor, click on the External Destination object.
If you have a universal link or app link from a 3rd party, select "Website" from the Destination drop down, and paste the link into the designated Destination URL space:
If you have a Custom URI, select "App deep link" from the Destination drop down, and paste your Custom URI into the designated Destination URL space:
💡 Important Note: The Pixel doesn't support mobile apps yet, so there's no need to select or enable one now.
What You Can Do With This:
Route fans straight to in-app content, instead of stopping at a landing page.
Drive app downloads and re-engagement by linking into app stores or fallback web experiences (universal links only).
Track engagement and optimize with full attribution when integrated with your analytics tools.