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.
We support two primary methods for implementing deep links: Universal Links and Custom URI Schemes.
What's the difference between Universal Links vs. Custom URI Schemes?
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 deep linking platform like Branch, Kochava or AppsFlyer. These platforms help ensure your deep link behaves correctly across devices and app installs.
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. We anticipate this functionality in a future update. If you wish to proceed with tracking, we can assist you in setting up server-to-server conversion tracking
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.