You can configure additional deep link options to create a frictionless user experience. Currently, Airbridge offers one option: adding a Stopover Airpage for iOS users.
More deep link options are coming soon.
Usually, when a user who has installed the app clicks a deep link, they will be redirected to a specific page within the app. However, some of those users end up being redirected to the App Store page.
This happens to all iOS apps, except for the Safari browser, when the user clicks the deep link for the first time and every first time in every app.
For example, if an iOS user who has installed your app clicks a deep link for the first time in App X, they will be redirected to the App Store page instead of being redirected to the intended in-app page of your app. Not only this, if the user who has been redirected to the App Store page from App X clicks on a deep link for the first time in App Y, this user will also be directed to the App Store page.
Adding a Stopover Airpage can prevent such situations and make sure the deep links work as intended.
Navigate to [Tracking Link]>[Link Generation] and select [App (Deep Link)] as “Destination.” Then, check the checkbox in the Deep Link Option box to add the Stopover Airpage.
Once you add the Stopover Airpage, iOS users who installed your app and click the deep link in App X will see the Stopover Airpage, which includes the following notification.
If the user clicks “Open,” the user will be redirected to the specific in-app page as intended. If the user clicks “Cancel,” a second notification will appear like the following.
If the user clicks “Open,” the user will be redirected to the specific in-app page as intended. If the user clicks “Cancel,” the user remains on the current page of App X.
Regardless of whether the StopOver Airpage is added or not, if a user who has installed the app clicks the same deep link for the second time in App X, the deep link will work as intended.
Stopover Airpage |
User Action | User Journey |
---|---|---|
Added | Clicks “Open” in the first notification | 1. Clicks the deep link for the first time in App X. |
Added | Clicks “Open” in the second notification | 1. Clicks the deep link for the first time in App X. |
Not added | - | 1. Clicks the deep link for the first time in App X. |
Stopover Airpage | User Journey |
---|---|
Added | 1. Clicks the deep link. |
Not added | Redirected to App Store page. |
Regardless of whether the Stopover Airpage is added or not, if a user who has not installed the app clicks the deep link in App X, the user is sent to the App Store page.
However, when the Stopover Airpage is added, users who have not installed the app will see a notification like the following.
When creating a deep link for a UA campaign, it is advised NOT TO ADD a Stopover Airpage.
As UA campaigns should redirect users to the App Store page to drive installs, the Stopover Airpage is unnecessary and could undermine the user experience and overall campaign performance.
As re-engagement campaigns aim to re-engage users who installed the app some time ago, using the Stopover Airpage allows you to redirect those users smoothly to the intended in-app page in your app.
For example, if a user who has installed your app clicks a deep link in App X for the first time, the user will see the notification asking the user whether to open your app. If this user clicks “Cancel,” a second notification will appear. When clicking “Open,” the user will be redirected to the App Store page.
このページは役に立ちましたか?