DeepLink Plan - iOS SDK (v4)

    Install the Airbridge iOS SDK and implement the necessary settings following the steps below.

    Install SDK

    The Airbridge iOS SDK can be installed using the method below. After installation, you can verify whether the SDK has been properly installed through the iOS SDK Test.

    1. Navigate to [File]>[Add Packages...] in Xcode.

    2. Enter the following address into the search bar and click Add Package.

    3. Click Add Package again.

    4. The Airbridge iOS SDK will be added to Package Dependencies.

    Install Restricted SDK

    Attention

    Install only one version of the SDK, either the general SDK or the restricted SDK.

    Depending on policies and environments, restrictions on collecting device IDs like GAID and IDFA may be required. When installing the Restricted SDK version, the device IDs are not collected.

    Install the Restricted SDK using the method below.

    1. Navigate to [File]>[Add Packages...] in Xcode.

    2. Enter the following address into the search bar and click Add Package.

    3. Click Add Package again.

    4. The Airbridge iOS SDK will be added to Package Dependencies.

    Initialize SDK

    SDK initialization methods vary depending on the system architecture. For SceneDelegate Lifecycle or AppDelegate Lifecycle, refer to the method for AppDelegate. For SwiftUI Lifecycle, refer to the method for SwiftUI.

    The YOUR_APP_NAME and YOUR_APP_SDK_TOKEN can be found on the [Settings]>[Tokens] page in the Airbridge dashboard.

    Call the Airbridge.initializeSDK function at the very top of AppDelegate's application(_:didFinishLaunchingWithOptions:) function.

    123456789101112131415
    import UIKit
    import Airbridge
    
    @main
    class AppDelegate: UIResponder, UIApplicationDelegate {
        func application(
            _ application: UIApplication,
            didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?
        ) -> Bool {
            let option = AirbridgeOptionBuilder(name: "YOUR_APP_NAME", token: "YOUR_APP_SDK_TOKEN")
                .build()
            Airbridge.initializeSDK(option: option)
            return true
        }
    }

    Configure ATT Prompt

    Note

    The functions necessary to ensure compliance with privacy policies should be reviewed with legal counsel.

    In the iOS environment, the IDFA can only be collected when users have allowed tracking of information through the AppTrackingTransparency (ATT) prompt.

    Event collection should be delayed until the user allows tracking. If the install event is collected before the user allows tracking on the ATT prompt, the install event data will lack an identifier, making performance measurement difficult. We recommend setting a sufficient delay time for event collection to collect identifiers.

    When using the DeepLink Plan, it is recommended to configure the setAutoDetermineTrackingAuthorizationTimeout parameter to 0 seconds when configuring the ATT prompt. The DeepLink Plan does not support attribution using identifiers. Therefore, to seamlessly redirect users who have already installed the app to the intended in-app location as configured in the deferred deep link, the setAutoDetermineTrackingAuthorizationTimeout parameter to 0 seconds.

    1. Prepare the text you will use in the ATT prompt.

    2. Enter the prepared text in the NSUserTrackingUsageDescription key of the Info.plist file.

    1. Navigate to [YOUR_PROJECT]>[Info]>[Custom iOS Target Properties] in Xcode.

    2. Hover your mouse over the key items, click + that appears, and enter Privacy - Tracking Usage Description.

    3. Enter the text for the ATT prompt as value.

    3. Set the time for displaying the ATT prompt.

    4. If the install event is not collected, the Airbridge iOS SDK delays collecting install events for 30 seconds until the user allows tracking each time the app is launched. If the user exits the app before deciding whether to allow tracking, the SDK will not collect the install event and will try again at the next app launch.

    When using the DeepLink Plan, it is recommended to configure the setAutoDetermineTrackingAuthorizationTimeout parameter to 0 seconds when configuring the ATT prompt. The DeepLink Plan does not support attribution using identifiers. Therefore, to seamlessly redirect users who have already installed the app to the intended in-app location as configured in the deferred deep link, the setAutoDetermineTrackingAuthorizationTimeout parameter to 0 seconds.

    The autoDetermineTrackingAuthorizationTimeout function can be used to set a longer delay for collecting install events. The default setting for the autoDetermineTrackingAuthorizationTimeout is 300 seconds. It can be set up to 3600 seconds (1 hour).

    1234567
    import Airbridge
    ...
    let option = AirbridgeOptionBuilder(name: "YOUR_APP_NAME",
                                        token: "YOUR_APP_SDK_TOKEN")
        .setAutoDetermineTrackingAuthorizationTimeout(second: 300)
        .build()
    Airbridge.initializeSDK(option: option)

    Attention

    Sufficient time must be configured to delay the collection of install events. If the delay time is up, the SDK will collect install events without identifiers before users can allow tracking on the ATT prompt.

    Deep Linking

    Deep linking allows you to redirect users from ads to specific locations within your app. The data collected from the tracking link enables you to monitor the performance of the deep link in Airbridge.

    When Airbridge generates a tracking link, it automatically selects and utilizes the optimal Airbridge deep link, depending on the environment. This link will be used for user redirection and is called the scheme deep link.

    Example)

    • Airbridge Deeplink: https://YOUR_APP_NAME.airbridge.io/~~~

    • Scheme Deeplink: YOUR_SCHEME://product/12345

    When the app is installed on a device and the user clicks the tracking link, the app opens through the Airbridge deep link. The Airbridge SDK converts the Airbridge deep link into a scheme deep link set on the tracking link. The converted scheme deep link is sent to the app.

    When the app is not installed on a device and the user clicks the tracking link, the Airbridge deep link is saved. After the user moves to the app store or website and the app is installed and launched, the Airbridge SDK converts the saved Airbridge deep link into a scheme deep link. The converted scheme deep link is sent to the app.

    Set up deep linking

    For the deep linking setup, the deep link information entered to the Airbridge dashboard and the in-app location address for user redirection is required.

    First, enter the deep link information into the Airbridge dashboard.

    After entering the deep link information into the Airbridge dashboard, refer to the information below for app setup. The instructions vary by the app system.

    Set up deferred deep linking

    When a user clicks on a tracking link with deferred deep linking capabilities and your app is not installed on the device, the Airbridge SDK retrieves the deep link as follows.

    The Airbridge.handleDeferredDeeplink function retrieves the saved Airbridge deep link and converts it into a scheme deep link to pass it to the app. Users are redirected to the intended destination using the converted scheme deep link.

    1234567891011
    import Airbridge
    ...
    let option = AirbridgeOptionBuilder(name: "YOUR_APP_NAME", token: "YOUR_APP_SDK_TOKEN")
        .build()
    Airbridge.initializeSDK(option: option)
    ...
    let isHandled = Airbridge.handleDeferredDeeplink() { url in
        if let url {
            // show proper content using url (YOUR_SCHEME://...)
        }
    }

    The Airbridge.handleDeferredDeeplink function returns true if the app is installed and called for the first time, waits for the Airbridge deep link acquisition, and converts it to a scheme deep link to pass it to onSuccess. You can use this scheme deeplink to send users to the set destination.

    If there is no stored Airbridge deep link, it will deliver nil to onSuccess. If the SDK is not initialized or if the Airbridge.handleDeferredDeeplink function has not been called for the first time, it will return false.

    The scheme deep link delivered is generally in the format of YOUR_SCHEME://... URL. If you use services like Meta Deferred App Links, it may be delivers in a different format.

    Testing

    The SDK functionality test and deep link test allow you to check whether the SDK and deep linking work as intended.

    Test SDK functionality

    Check whether the Airbridge iOS SDK is operating properly. The Install events are collected by the Android SDK regardless of whether the additional configurations have been completed or not.

    Check Install event collection

    Follow the steps below to check whether the Install events are being collected by the iOS SDK.

    1. Prepare a test device where the app is not installed, or if the app is already installed, delete it before testing.

    2. Set the SDK log level to Log_ALL.

    123
    let option = AirbridgeOptionBuilder(name: "YOUR_APP_NAME", token: "YOUR_APP_SDK_TOKEN")
        .build()
    Airbridge.initializeSDK(option: option)

    3. Install the app on the test device. After installing the app, launch it so that the Install event is collected.

    The first Open event collected by Airbridge is recorded as an Install event. Therefore, the Open may not be recorded when the app install event is collected.

    4. In the Xcode Console, check whether the event performed on the test device with a specific IDFA is logged properly. In the Console Filter, enter Library:Airbridge. If the Install events are being collected properly, you should see logs such as the following.

    • Send event packets to Airbridge: categories=9161

    • Send event packets to Airbridge: categories=9163

    For the Xcode Console messages and their meaning, refer to the following.

    5. If you can't see the logs in the Xcode Console even after a sufficient amount of time has passed, check whether the SDK has been initialized, the SDK configurations are completed as instructed, and the network status is stable.

    If the problem persists, contact your Airbridge CSM and share your SDK logs. If you don't have a designated Airbridge CSM, contact the Airbridge Help Center.

    Check whether the deep linking feature configured in the Airbridge iOS SDK works as intended.

    Preliminary check up

    Before testing the deep link, make sure the following items have been set up.

    #{"width":"120px"}

    Item

    #{"width":"240px"}

    Description

    #{"width":"140px"}

    Resources

    HTTP Deep Link (App links)

    Setup is required

    - Dashboard Settings

    - Set up deep link

    Scheme Deep Link

    Setup is required

    - Dashboard Settings

    - Set up deep link

    Deferred Deep Link

    The setup is completed automatically. No additional setup is required.

    - Set up deferred deep linking

    Custom Domain

    Setup is optional

    - Dashboard Settings

    App Install

    - If you don't need to test the deferred deep link, install the app on your test device in advance.

    - If you need to test the deferred deep link, the app should not be installed on the test device. If the app is installed, delete the app from the test device.

    Airbridge provides a website for testing deep links. If you want to test deferred deep links, you need to uninstall the app from your test device.

    1. Visit the deep link testing site from your test device. You can access the website directly by using the QR code below.

    2. Enter the App Name you registered with Airbridge. You can find it on the [Settings]>[Tokens] page in the Airbridge dashboard.

    If you want to test a specific deep link address, enter the scheme deep link into the Deeplink URL field. The scheme deep link format is {YOUR_SCHEME}://...

    If you're using a custom domain, make sure to enter your custom domain.

    3. Click one of the buttons listed below. Click the button depending on the deep link type you are testing.

    Note that you can only test deferred deep links if the app is not installed on your test device.

    #{"width":"120px"}

    Button

    #{"width":"240px"}

    Description

    #{"width":"140px"}

    Example

    Test HTTP Deeplink Type-1

    Test the HTTP deep link in the format of https://{your_app-name}.abr.ge.

    https://{your_app-name}.abr.ge/@{your_app-name}/test_sdk?...

    Test HTTP Deeplink Type-2

    Test the HTTP deep link in the format of https://abr.ge. The address format is different from Test HTTP Deeplink Type-1.

    https://abr.ge/@{your_app-name}/test_sdk?...

    Test Scheme Deeplink

    Test the scheme deep link.

    https://abr.ge/@{your_app-name}/test_sdk?...

    Test Deferred Deeplink

    Test the deferred deep link.

    https://abr.ge/@{your_app-name}/test_sdk?...

    Test Custom Domain Deeplink

    Test the custom domain. This button is only available when the custom domain is entered.

    https://{your_custom_domain}/@{your_app-name}/test_sdk?...

    4. Check whether the event performed on the test device with a specific IDFA is logged properly in the Xcode Console. Enter [Airbridge][Debug] in the Console filter. If the Install events are being collected properly, you should see logs as follows.

    • [Airbridge] [Debug] - success network to url: https://core.airbridge.io/api/v4/apps/{app_name}/events/mobile-app/9162

    • [Airbridge] [Debug] - success network to url : https://core.airbridge.io/api/v4/apps/{app_name}/events/mobile-app/9163

    • [Airbridge] [Debug] - success network to url : https://core.airbridge.io/api/v4/apps/{app_name}/events/mobile-app/9168

    If the SDK log level has been set to DEBUG in the Airbridge SDK initialization process, you can check the value sent through the network.

    5. The client request: method={...} message transmits the header and body values. Check the following items based on the button clicked on the deep link test site. If the deep link is working properly, all items should be confirmed.

    Troubleshooting

    Refer to the information below for troubleshooting regarding deep links.

    Problem

    Solution

    You clicked a deep link, but the app was not launched. Or the SDK logs show information that is not intended as per setting.

    Check whether the deep link is set up correctly. Refer to this article for the deep linking setup.

    You clicked a deep link, and the app was launched, but you didn't land on the intended app page.

    You need to write code that redirects the user to the deep link path that is passed by the onSuccessfunction. Refer to this article for the deep linking setup.

    このページは役に立ちましたか?

    ご質問やご提案はありますか?