Skip to main content

Dashboard Setup

  1. Sign in to your Airbridge account.
  2. Click Add a new app.
  3. Add your app to Airbridge. Once you’re done, go to [Tracking Links]>[Deep Links] and submit the deep link information to Airbridge.

SDK Setup

Install the Airbridge SDK in your app and complete the essential setup.

SDK setup

To install the Airbridge Android SDK, declare the SDK repository in the build.gradle or settings.gradle file of your project that contains the repositories block. Then, add the SDK package to your application’s build.gradle file.Check the latest version at the link below and replace $HERE_LATEST_VERSION.Project build.gradle or settings.gradle file
Application build.gradle file

SDK initialization

Create the MainApplication class and add it to the AndroidManifest.xml. Then, initialize the SDK in the onCreate function within the class.The YOUR_APP_NAME and YOUR_APP_SDK_TOKEN can be found on the [Settings]>[Tokens] page in the Airbridge dashboard.
AndroidManifest.xml
AttentionStarting from Airbridge Android SDK 4.9.0, backup rule configuration is not required. Only refer to the backup rule configuration in the troubleshooting guide if you are using a version below 4.9.0.

Deep linking setup

Follow the instructions below and complete the setup for all the items below.Create an Activity class to handle deep links and add it to the AndroidManifest.xml. Then, add the 3 types of Airbridge Deep Links to the intent filter. When a tracking link is triggered, Airbridge will launch the app with the most appropriate type of Airbridge Deep Link depending on the browser and whether the app is installed on the user’s device.YOUR_SCHEME should be the URI scheme you submitted to the [Tracking Links]>[Deep Links] page in the Airbridge dashboard, without the ://.The YOUR_APP_NAME and YOUR_APP_SDK_TOKEN can be found on the [Settings]>[Tokens] page in the Airbridge dashboard.
AndroidManifest.xml
In the onResume function of the deep link handling Activity class, call the handleDeeplink function to convert the Airbridge Deep Link into the deep link set in the tracking link. Also, make sure the user is redirected to the intended in-app location using the converted scheme deep link.If the app is launched via an Airbridge Deep Link, isAirbridgeDeeplink returns true, and the configured deep link will be passed to the URI of the callback function.If the app is launched by a deep link that is not from Airbridge, isAirbridgeDeeplink returns false, and the callback function will not be called.

Redirect users through deferred deep linking

When a user who hasn’t installed the app clicks on a tracking link with a deep link set as the user destination, they can be redirected to the app store to prompt app install. After the user installs and launches the app, you can call the handleDeferredDeeplink function at the appropriate moment to obtain the deep link set in the tracking link. Ensure the user is redirected to the intended in-app location using the obtained deep link.The first time handleDeferredDeeplink is called after app installation, it returns true, and the deep link from the tracking link is passed as a parameter to the callback function.If handleDeferredDeeplink is called again after the initial call, it returns false, and the callback function will not be invoked.
AttentionWhen the app is opened via a deep link, Airbridge passes null to onSuccess regardless of whether a deferred deep link exists or not, ensuring that only the deep link is processed.

SDK setup

Install the Airbridge iOS SDK.
  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.

SDK initialization

Initialize the SDK by referring to the code below.
The YOUR_APP_NAME and YOUR_APP_SDK_TOKEN can be found on the [Settings]>[Tokens] page in the Airbridge dashboard.

ATT prompt setup

The SDK does not collect install events or trigger deferred deep linking until the user has responded to the ATT prompt.You can configure a timeout for the user response on the ATT prompt using the setAutoDetermineTrackingAuthorizationTimeout function. If the user does not respond within the specified timeout period, the install event will be collected, and deferred deep linking will be enabled regardless of the ATT prompt response. The default timeout value is 30 seconds.The Airbridge DeepLink Plan does not support attribution using identifiers. Therefore, to ensure that users who haven’t installed the app are directed to the intended destination through deferred deep linking without delay, set the setAutoDetermineTrackingAuthorizationTimeout value to 0 seconds.

Deep linking setup

Follow the instructions below and complete the setup for all the items below.Complete the scheme deep link app setup and universal link app setup by referring to the code below.When a tracking link is triggered, Airbridge will launch the app with the most appropriate type of Airbridge Deep Link depending on the browser and whether the app is installed on the user’s device.
Scheme deep link setup in the appIn Xcode, go to [YOUR_PROJECT]>[Info]>[URL Types]. Then, click “+” and enter YOUR_SCHEME.Universal Link setup in the appIn Xcode, go to [YOUR_PROJECT]>[Signing & Capabilities]. Then, click “+ Capability” and select “Associated Domains”. Lastly, add applinks:YOUR_APP_NAME.airbridge.io and applinks:YOUR_APP_NAME.abr.ge.
YOUR_SCHEME should be the URI scheme you submitted to the [Tracking Links]>[Deep Links] page in the Airbridge dashboard, without ://.The YOUR_APP_NAME and YOUR_APP_SDK_TOKEN can be found on the [Settings]>[Tokens] page in the Airbridge dashboard.When the app opens with a deep link, call the trackDeeplink function to collect the Deeplink Open event. Then call the handleDeeplink function to retrieve the deep link set in the tracking link. Also, make sure the user is redirected to the intended in-app location using the converted scheme deep link.If the app is launched via an Airbridge Deep Link, handleDeeplink returns true, and the configured deep link will be passed to the URI of the callback function.If the app is launched by a deep link that is not from Airbridge, handleDeeplink returns false, and the callback function will not be called.

Redirect users through deferred deep linking

When a user who hasn’t installed the app clicks on a tracking link with a deep link set as the user destination, they can be redirected to the app store to prompt app install. After the user installs and launches the app, you can call the handleDeferredDeeplink function at the appropriate moment to obtain the deep link set in the tracking link. Ensure the user is redirected to the intended in-app location using the obtained deep link.The first time handleDeferredDeeplink is called after app installation, it returns true, and the deep link from the tracking link is passed as a parameter to the callback function.If handleDeferredDeeplink is called again after the initial call, it returns false, and the callback function will not be invoked.
AttentionWhen the app is opened via a deep link, Airbridge passes null to onSuccess regardless of whether a deferred deep link exists or not, ensuring that only the deep link is processed.

SDK installation

Install the Airbridge React Native SDK.

SDK initialization

Initialize the SDK when the app is opened.The YOUR_APP_NAME and YOUR_APP_SDK_TOKEN can be found on the [Settings]>[Tokens] page in the Airbridge dashboard.ios/YOUR_PROJECT_NAME/AppDelegate.m file
android/app/src/main/java/.../MainApplication.kt file

SDK setup

Configure the SDK settings by following the steps below.
  1. Create an airbridge.json file at the top level of the React Native project folder, input the JSON as above, and configure the SDK settings.
  2. Don’t input values for keys that are not necessary for your service.
AttentionWhen issues arise due to Airbridge SDK backup rule merge conflicts, please refer to the backup rule configuration in the troubleshooting guide.

ATT prompt setup

The SDK does not collect install events or trigger deferred deep linking until the user has responded to the ATT prompt.You can configure the timeout for the user’s response to the ATT prompt using the autoDetermineTrackingAuthorizationTimeoutInSecond setting in airbridge.json.If the user does not respond within the specified timeout period, the install event will be collected, and deferred deep linking will be enabled regardless of the ATT prompt response. The default timeout value is 30 seconds.The Airbridge DeepLink Plan does not support attribution using identifiers. Therefore, to ensure that users who haven’t installed the app are directed to the intended destination through deferred deep linking without delay, set the autoDetermineTrackingAuthorizationTimeoutInSecond value to 0 seconds.

Deep linking setup

Follow the instructions below and complete the setup for all the items below.Complete the scheme deep link app setup and universal link app setup for iOS, and the scheme deep link app setup and app link setup for Android by referring to the codes below.When a tracking link is triggered, Airbridge will launch the app with the most appropriate type of Airbridge Deep Link depending on the browser and whether the app is installed on the user’s device.ios/YOUR_PROJECT_NAME.xcodeproj file
Scheme deep link setup in the appIn Xcode, go to [YOUR_PROJECT]>[Info]>[URL Types]. Then, click “+” and enter YOUR_SCHEME.Universal Link setup in the appIn Xcode, go to [YOUR_PROJECT]>[Signing & Capabilities]. Then, click “+ Capability” and select “Associated Domains”. Lastly, add applinks:YOUR_APP_NAME.airbridge.io and applinks:YOUR_APP_NAME.abr.ge.
android/app/src/main/AndroidManifest.xml fileScheme deep link app setupAdd YOUR_SCHEME to the intent-filter.App link setupAdd YOUR_APP_NAME.airbridge.io and YOUR_APP_NAME.abr.ge to the intent-filter.
AndroidManifest.xml
YOUR_SCHEME should be the URI scheme you submitted to the [Tracking Links]>[Deep Links] page in the Airbridge dashboard, without the ://.The YOUR_APP_NAME and YOUR_APP_SDK_TOKEN can be found on the [Settings]>[Tokens] page in the Airbridge dashboard.Call the trackDeeplink function when the app is opened through a deep link, so the SDK can collect the deep link event.ios/YOUR_PROJECT_NAME/AppDelegate.m file
android/app/src/main/java/.../MainActivity.kt file
Call the setOnDeeplinkReceived function to retrieve the deep link set in the tracking link. Also, make sure the user is redirected to the intended in-app location using the converted scheme deep link.

Redirect users through deferred deep linking

No additional setup is required for deferred deep linking. When a user who hasn’t installed the app clicks a tracking link, they will be redirected to the app store, prompting them to install the app. After installation, when the user launches the app, the deep link set in the tracking link is automatically passed to the OnDeeplinkReceived function.

SDK installation

Install the Airbridge Flutter SDK.Add the following line to the dependencies block in your pubspec.yaml file. Check the link below for the latest version and replace $HERE_LATEST_VERSION accordingly.
  • SDK version list: link
From the root directory of your project, open the terminal and run the following command.Note that the Airbridge Flutter SDK only works with Flutter 1.20.0 or higher and Dart 2.12.0 or later.
Shell

SDK initialization

Initialize the SDK when the app is opened.The YOUR_APP_NAME and YOUR_APP_SDK_TOKEN can be found on the [Settings]>[Tokens] page in the Airbridge dashboard.ios/YOUR_PROJECT_NAME/AppDelegate.m 파일
android/app/src/main/java/.../MainApplication.kt 파일

SDK setup

Configure the SDK settings by following the steps below.
  1. Create an airbridge.json file at the top level of the project folder, input the JSON as above, and configure the SDK settings.
  2. Don’t input values for keys that are not necessary for your service.
AttentionWhen issues arise due to Airbridge SDK backup rule merge conflicts, please refer to the backup rule configuration in the troubleshooting guide.

ATT prompt setup

The SDK does not collect install events or trigger deferred deep linking until the user has responded to the ATT prompt.You can configure the timeout for the user’s response to the ATT prompt using the autoDetermineTrackingAuthorizationTimeoutInSecond setting in airbridge.json.If the user does not respond within the specified timeout period, the install event will be collected, and deferred deep linking will be enabled regardless of the ATT prompt response. The default timeout value is 30 seconds.The Airbridge DeepLink Plan does not support attribution using identifiers. Therefore, to ensure that users who haven’t installed the app are directed to the intended destination through deferred deep linking without delay, set the autoDetermineTrackingAuthorizationTimeoutInSecond value to 0 seconds.

Deep linking setup

Follow the instructions below and complete the setup for all the items below.Complete the scheme deep link app setup and universal link app setup for iOS, and the scheme deep link app setup and app link setup for Android by referring to the codes below.When a tracking link is triggered, Airbridge will launch the app with the most appropriate type of Airbridge Deep Link depending on the browser and whether the app is installed on the user’s device.ios/YOUR_PROJECT_NAME.xcodeproj file
Scheme deep link setup in the appIn Xcode, go to [YOUR_PROJECT]>[Info]>[URL Types]. Then, click “+” and enter YOUR_SCHEME.Universal Link setup in the appIn Xcode, go to [YOUR_PROJECT]>[Signing & Capabilities]. Then, click “+ Capability” and select “Associated Domains”. Lastly, add applinks:YOUR_APP_NAME.airbridge.io and applinks:YOUR_APP_NAME.abr.ge.
android/app/src/main/AndroidManifest.xml fileScheme deep link app setupAdd YOUR_SCHEME to the intent-filter.App link setupAdd YOUR_APP_NAME.airbridge.io and YOUR_APP_NAME.abr.ge to the intent-filter.
AndroidManifest.xml
YOUR_SCHEME should be the URI scheme you submitted to the [Tracking Links]>[Deep Links] page in the Airbridge dashboard, without ://.The YOUR_APP_NAME and YOUR_APP_SDK_TOKEN can be found on the [Settings]>[Tokens] page in the Airbridge dashboard.Call the trackDeeplink function when the app is opened through a deep link, so the SDK can collect the deep link event.ios/YOUR_PROJECT_NAME/AppDelegate.m file
android/app/src/main/java/.../MainActivity.kt file
Call the setOnDeeplinkReceived function to retrieve the deep link set in the tracking link. Also, make sure the user is redirected to the intended in-app location using the converted scheme deep link.

Redirect users through deferred deep linking

No additional setup is required for deferred deep linking. When a user who hasn’t installed the app clicks a tracking link, they will be redirected to the app store, prompting them to install the app. After installation, when the user launches the app, the deep link set in the tracking link is automatically passed to the OnDeeplinkReceived function.

SDK installation

Install the Airbridge Expo SDK.

SDK initialization

Initialize the SDK when the app is opened.The YOUR_APP_NAME and YOUR_APP_SDK_TOKEN can be found on the [Settings]>[Tokens] page in the Airbridge dashboard.
app.json

SDK setup

Configure the SDK settings by following the steps below.
  1. Create an airbridge.json file at the top level of the project folder, input the JSON as above, and configure the SDK settings.
  2. Don’t input values for keys that are not necessary for your service.

ATT prompt setup

The SDK does not collect install events or trigger deferred deep linking until the user has responded to the ATT prompt.You can configure the timeout for the user’s response to the ATT prompt using the autoDetermineTrackingAuthorizationTimeoutInSecond setting in airbridge.json.If the user does not respond within the specified timeout period, the install event will be collected, and deferred deep linking will be enabled regardless of the ATT prompt response. The default timeout value is 30 seconds.The Airbridge DeepLink Plan does not support attribution using identifiers. Therefore, to ensure that users who haven’t installed the app are directed to the intended destination through deferred deep linking without delay, set the autoDetermineTrackingAuthorizationTimeoutInSecond value to 0 seconds.

Deep linking setup

Follow the instructions below and complete the setup for all the items below.Complete the universal link app setup in the associatedDomains for iOS, and the app link setup in the associatedDomains for Android by referring to the code below.
app.json
YOUR_SCHEME should be the URI scheme you submitted to the [Tracking Links]>[Deep Links] page in the Airbridge dashboard, without ://.The YOUR_APP_NAME and YOUR_APP_SDK_TOKEN can be found on the [Settings]>[Tokens] page in the Airbridge dashboard.Call the setOnDeeplinkReceived function to retrieve the deep link set in the tracking link. Also, make sure the user is redirected to the intended in-app location using the converted scheme deep link.

Redirect users through deferred deep linking

No additional setup is required for deferred deep linking. When a user who hasn’t installed the app clicks a tracking link, they will be redirected to the app store, prompting them to install the app. After installation, when the user launches the app, the deep link set in the tracking link is automatically passed to the OnDeeplinkReceived function.

Testing

Follow the steps below to verify that the SDK has been successfully installed.

App install collection

  1. Navigate to [Settings]>[Testing Console]>[Attributed Installs].
  2. Enter the ADID of the test device, which is GAID or IDFA.
  3. Delete your app from the test device and scan the QR code.
  4. Check the results.
  5. If the test fails, revisit the SDK setup and SDK initialization steps and make sure the SDK is properly implemented.

Deep linking

  1. Navigate to [Settings]>[Testing Console]>[Deep Linking].
  2. Input the deep link of the app you want to test. It should be entered in the format of scheme://product/12345.
  3. Complete the Essential Test 1, 2, and 3 by following the instructions on the dashboard.
  4. Check the results.
  5. If the test fails, revisit the dashboard setup, SDK setup, and deep link setup steps and make sure the SDK is properly implemented.