Use this article to get answers to any questions about deep linking.
Understand Deep Linking
Deep linking is a simple technique that directs users to a specific page or content within an app, rather than to a website or app store. In general, deep links work as follows:
- If the user has already installed the advertised app, deep link URLs direct them to the product page or specific page within the app.
- If the user has not installed the advertised app, the deep link falls back to the app store.
The deep link differs from a standard link in that the standard link typically directs users to a browser version of the app homepage or to the app store even even in cases when the user has already installed the advertised app.
Advantages of Deep Linking
From a Publisher point of view, deep linking provides a more personalized experience for a user by taking them to specific content within the app, thereby boosting conversions, installs, and user engagement.
From an Advertiser standpoint, deep linking makes the user's journey more seamless and streamlined, increasing user engagement.
Support
The Liftoff Monetize SDK supports deep linking in these SDKs:
- iOS: Liftoff Monetize SDK for iOS v.SDK 6.11 and higher
- Android: Liftoff Monetize SDK for Android v.SDK 6.11 and higher
How Deep Linking Works
Vungle Exchange Communicates to Buyers Whether Deep Linking Is Supported
By default, Vungle Exchange sends “deep link support” for all full screen videos to all DSP partners. Vungle communicates deep link support to buyers within the bid request using the flag deeplink.
$imp[ ].ext.deeplink=1indicates deep linking is supported.$imp[ ].ext.deeplink=0indicates deep linking is not supported.
Refer to the Imp Extension object in the Vungle Exchange OpenRTB 2.5 Integration Guide:
| Field | Type | Required | Description |
|---|---|---|---|
deeplink |
Boolean | no | Indicates whether deep linking is supported for this impression. ‘1’ = deep linking is supported ‘0’ = deep linking is not supported |
Buyers Pass the Deep Link
Buyers pass the deep linking URL in the bid response within the field
$seatbid[ ].bid[ ].ext.deeplink
For example:
ext": {"deeplink": "zalora://my//seg_s/m/”}
Refer to the Bid Extension object in the Vungle Exchange OpenRTB 2.5 Integration Guide:
| Field | Type | Required | Description |
|---|---|---|---|
deeplink |
string | no | Optional URL directing the user to specific content within the app if the app is already installed. If the app is not already installed and the deep link URL cannot be rendered, we default to the download URL. |
The SDK Identifies Deep Linking URLs
Deep linking URLs are passed to the SDK inside the ad markup with the key deeplinkUrl. For example:
"deeplinkUrl: “zalora://my//seg_s/m/”
In the absence of a deep link, the SDK points the user to the download URL (if it is provided and available), which takes the user to the app store.
Users Click the Deep Link
Liftoff Monetize and Vungle Exchange will not know whether the user has already installed the advertised app. DSPs send a deep link URL and a download URL.
- If a deep link is rendered successfully; it means the user has already installed the advertised app.
- If the deep link is not rendered successfully, it means that the user has not installed the app, and we fallback to download URL.
If the DSP sends only a deep link and no download URL, and:
- The user has already installed the advertised app, the user is directed to the specific page/content within the installed app
- The user has not installed the advertised app, the deep link fails without a fallback download URL provided by the buyer to take the user to the app store