Attention

The Airbridge dashboard offers a testing console to test whether the Airbridge SDK is working properly. Install the Airbridge SDK first before proceeding with the test.

• Testing the Airbridge SDK integration for Marketers

After completing the necessary settings for the Airbridge Android SDK setup, you can test whether it works properly using real-time logs, test sites, etc. Prepare the following information before testing the Android SDK.

GAID of the test device

Attention

Different Airbridge App modes must be selected on the Airbridge dashboard to separate the data of the app that you want to measure ad performance from the data of the app that you want to use for testing purposes.

For development apps, you must enter the package name into the Airbridge dashboard. Refer to the Airbridge user guide for more details.

Check whether the Airbridge Android SDK is operating properly.

Check whether the Install events are being collected by the Android SDK by following the steps below.

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 DEBUG.

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. Navigate to [Raw Data]>[App Real-Time Log] in the Airbridge dashboard and find the events with the test device's GAID in the real-time logs. If the Install event can be found in the real-time log, you can confirm that the SDK is working as intended. It may take up to 10 minutes to check the Install event in the [App Real-time Log].

5. If the Install event is not confirmed in the [App Real-time Log] even after sufficient time, check whether the Install event is in the SDK log. When the Install event is in the SDK log, uninstall the application on the test device and reinstall it.

If the Install event is not confirmed again, report this issue to your Airbridge CSM and provide the SDK log.

Airbridge initiates the attribution process when a Target Event occurs. The Install event is a typical Target Event. By checking the attribution result of the Install event, you can confirm whether the process from collection of the event to attribution is properly conducted.

1. Prepare a test device on which the app is not installed. Or please delete the app before testing.

2. Set the SDK log level to DEBUG.

val option = AirbridgeOptionBuilder("YOUR_APP_NAME", "YOUR_APP_SDK_TOKEN")
    .setLogLevel(AirbridgeLogLevel.DEBUG)
    .build()
Airbridge.initializeSDK(this, option)

3. Access the Attribution Integration Test site on your test device.

4. Enter the App Name and GAID, then click Submit. The App Name can be found on the [Settings]>[Tokens] page in the Airbridge dashboard.

5. Click Test Install Attribution to move to the Google Play Store. If the Airbridge Android SDK is not installed on the app that is available for download in the Google Play Store, use tools like Android Debug Bridge to install the app with the SDK.

6. Install the app on your test device. You must launch the app after install to collect the Install event.

The first Open event is recorded as an Install event in Airbridge. Therefore, the Open event may not be recorded if the Install event is collected.

7. Navigate to [Raw Data]>[App Real-Time Log] in the Airbridge dashboard and find the events with the test device's GAID in the real-time logs. If the Install event can be found in the real-time log, you can confirm that the SDK is working as intended. It may take up to 10 minutes to check the Install event in the [App Real-time Log].

8. Check whether the Install event data is collected as follows. The data must match the details below to confirm that the attribution process has been completed successfully.

• Event Category: Install

• gaid: GAID entered in the attribution test site

• attributionResult.channel: test_sdk

• attributionResult.attributedTouchpointOriginURL: https://abr.ge/@${YOUR_APP_NAME}/test_sdk?campaign=test_sdk_campaign&device_uuid=${YOUR_GAID}

9. If the Install event is not confirmed in the [App Real-time Log] even after sufficient time, check whether the Install event is in the SDK log. When the Install event is in the SDK log, uninstall the application on the test device and reinstall it.

If the Install event is not confirmed again, report this issue to your Airbridge CSM and provide the SDK log.

Check whether the event and user data are being collected as intended.

Check whether the events are being collected by the Airbridge Android SDK as defined in your Airbridge event taxonomy by following the steps below.

{
   ...
   "eventData": {
      ...
      "goal": {
         "category": "airbridge.ecommerce.order.completed",
         "semanticAttributes": {
            "value": 10000.0,
            "totalQuantity": 1000,
            "currency": "krw",
            "transactionID": "transaction_1",
            "products": [
               {
                  "quantity": 10,
                  "productID": "coca_1",
                  "price": 1.99,
                  "name": "Coca cola",
                  "currency": "usd",
                  "position": 1
               },
               {
                  "quantity": 5,
                  "productID": "fanta_1",
                  "price": 2.5,
                  "name": "Fanta Orange",
                  "currency": "usd",
                  "position": 2
               },
               {
                  "quantity": 1,
                  "productID": "terra_pack_1",
                  "price": 10.99,
                  "name": "Terra 12 Pack",
                  "currency": "usd",
                  "position": 3
               }
            ],
            "inAppPurchased": true
         }
      }
   },
   ...
}

Attention

If you haven't set up user data collection in the Airbridge Android SDK, the checkup process described below is not necessary.

Check whether the user data is collected as intended by the Android SDK.

{
    ...
    "eventData": {
        ...
    },
    "user": {
        "externalUserID": {User ID},
        "externalUserPhone": {User Phone},
        "alias": {
            "key": {value}
        },
        "attributes": {
            "key": {value}
        },
        "isClientSideHashed": true
    },
    ...
}

Check whether the deep linking feature configured in the Airbridge Android SDK is working properly.

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

Airbridge provides a deep link testing site. 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 site directly by using the QR code below.

2. Enter the App Name registered with Airbridge into the App Name field. You can check this on the [Settings]>[Tokens] page in the Airbridge dashboard.

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

Also, If you're using a custom domain, make sure to enter your custom domain in the Custom Domain field.

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.

4. When the Deep Link Open event is successfully collected, you can check this on the [Raw Data]>[App Real-time Log] page in the Airbridge dashboard.

Once you find the Deeplink Open event on the [Raw Data]>[App Real-time Log] page in the Airbridge dashboard, additional items must be confirmed, and the items vary depending on the button clicked. Refer to the information below. If the deep link operates properly, all the items can be found.

Refer to the information below for troubleshooting regarding deep links.